Counter settings: disk

Showing posts with label disk. Show all posts

Saturday, February 25, 2012

Could not create tempdb - SQL Server 2005 with SP1

I am receiving the following message within the Application Event Log on one
of my servers.
Could not create tempdb. You may not have enough disk space available. Free
additional disk space by deleting other files on the tempdb drive and then
restart SQL Server. Check for additional errors in the event log that may
indicate why the tempdb files could not be initialized.
I am also receiving this error:
The database 'model' is marked RESTORING and is in a state that does not
allow recovery to be run.
The strange thing about this message is that the server was working
correctly yesterday. The only thing that changed: The server was shut down
and moved to a new data center. Connectivity is in place because I can
connect to the box via Remote Desktop from work and from home.
This error is ONLYhappening on the default instance. There are two other
instances on the server (all three SQL Server installs are running under the
same network account).
There is enough free space on the volumes.
OS: 24GB free
internal array: 650 GB free
external array (MSA 500 G2): 900GB free
I even tried starting that instance in single user mode from the command
prompt via:
sqlservr -smssqlserver -c -f -m -T3608
This worked and I tried moving tempdb to the different volumes that are
available on the box. When I try to start SQL Server I receive the same
errors about model and tempdb and this instance fails to start.
I appreciate any assistance you can provide!
--
Keith KratochvilKeith Kratochvil wrote:
> I am receiving the following message within the Application Event Log on one
> of my servers.
> Could not create tempdb. You may not have enough disk space available. Free
> additional disk space by deleting other files on the tempdb drive and then
> restart SQL Server. Check for additional errors in the event log that may
> indicate why the tempdb files could not be initialized.
> I am also receiving this error:
> The database 'model' is marked RESTORING and is in a state that does not
> allow recovery to be run.
> The strange thing about this message is that the server was working
> correctly yesterday. The only thing that changed: The server was shut down
> and moved to a new data center. Connectivity is in place because I can
> connect to the box via Remote Desktop from work and from home.
>
> This error is ONLYhappening on the default instance. There are two other
> instances on the server (all three SQL Server installs are running under the
> same network account).
>
> There is enough free space on the volumes.
> OS: 24GB free
> internal array: 650 GB free
> external array (MSA 500 G2): 900GB free
> I even tried starting that instance in single user mode from the command
> prompt via:
> sqlservr -smssqlserver -c -f -m -T3608
> This worked and I tried moving tempdb to the different volumes that are
> available on the box. When I try to start SQL Server I receive the same
> errors about model and tempdb and this instance fails to start.
>
> I appreciate any assistance you can provide!
>
Hi
Check your logs(ldf) file size
regards
SW|||In addition to the errors that I mentioned (recorded within the Application
log), this error is within the System log:
The SQL Server (MSSQLSERVER) service terminated with service-specific error
1814 (0x716).
The error is written right after the entry that states:
The SQL Server (MSSQLSERVER) service entered the stopped state.
I tried starting SQL Server normally after telling it where to create tempdb
(via ALTER DATABASE ... MODIFY FILE...).
It would not start -- the same errors on model and tempdb are written to the
log.
Then I started SQL Server via the command line again
(sqlservr -smssqlserver -c -f -m -T3608).
It started (as before).
SQL crashes if I execute these commands:
sp_helpdb tempdb
select * From tempdb..sysfiles
I can execute these commands, however:
select * From master..sysdatabases where name = 'tempdb'
select * From master..sysaltfiles where name like 'temp%'
Here are the results:
name dbid sid mode status status2 crdate reserved category cmptlevel
filename version
tempdb 2 0x01 0 8 1090520064 2006-10-26 09:26:35.027 1900-01-01 00:00:00.000
0 90 E:\mssql\data\tempdb.mdf NULL
fileid groupid size maxsize growth status perf dbid name filename
1 1 1024 -1 10 1048578 0 2 tempdev E:\mssql\data\tempdb.mdf
2 0 64 -1 10 1048642 0 2 templog E:\mssql\data\templog.ldf
However tempdb's data and log files are are not on the disk. I searched for
them using Agent Ransack (as well as Windows Explorer).
--
Keith Kratochvil
"Sebastian" <sebastian@.waksmundzcy.com.pl> wrote in message
news:%23Bnb$FJGHHA.2456@.TK2MSFTNGP06.phx.gbl...
> Keith Kratochvil wrote:
>> I am receiving the following message within the Application Event Log on
>> one of my servers.
>> Could not create tempdb. You may not have enough disk space available.
>> Free additional disk space by deleting other files on the tempdb drive
>> and then restart SQL Server. Check for additional errors in the event log
>> that may indicate why the tempdb files could not be initialized.
>> I am also receiving this error:
>> The database 'model' is marked RESTORING and is in a state that does not
>> allow recovery to be run.
>> The strange thing about this message is that the server was working
>> correctly yesterday. The only thing that changed: The server was shut
>> down and moved to a new data center. Connectivity is in place because I
>> can connect to the box via Remote Desktop from work and from home.
>>
>> This error is ONLYhappening on the default instance. There are two other
>> instances on the server (all three SQL Server installs are running under
>> the same network account).
>>
>> There is enough free space on the volumes.
>> OS: 24GB free
>> internal array: 650 GB free
>> external array (MSA 500 G2): 900GB free
>> I even tried starting that instance in single user mode from the command
>> prompt via:
>> sqlservr -smssqlserver -c -f -m -T3608
>> This worked and I tried moving tempdb to the different volumes that are
>> available on the box. When I try to start SQL Server I receive the same
>> errors about model and tempdb and this instance fails to start.
>>
>> I appreciate any assistance you can provide!
> Hi
> Check your logs(ldf) file size
> regards
> SW|||Does that directory structure exist on the E Drive? Does the E: Drive
even exist'
What other databases were supposed to be on your E Drive?
Keith Kratochvil wrote:
> In addition to the errors that I mentioned (recorded within the Application
> log), this error is within the System log:
> The SQL Server (MSSQLSERVER) service terminated with service-specific error
> 1814 (0x716).
> The error is written right after the entry that states:
> The SQL Server (MSSQLSERVER) service entered the stopped state.
>
> I tried starting SQL Server normally after telling it where to create tempdb
> (via ALTER DATABASE ... MODIFY FILE...).
> It would not start -- the same errors on model and tempdb are written to the
> log.
> Then I started SQL Server via the command line again
> (sqlservr -smssqlserver -c -f -m -T3608).
> It started (as before).
> SQL crashes if I execute these commands:
> sp_helpdb tempdb
> select * From tempdb..sysfiles
>
> I can execute these commands, however:
> select * From master..sysdatabases where name = 'tempdb'
> select * From master..sysaltfiles where name like 'temp%'
> Here are the results:
> name dbid sid mode status status2 crdate reserved category cmptlevel
> filename version
> tempdb 2 0x01 0 8 1090520064 2006-10-26 09:26:35.027 1900-01-01 00:00:00.000
> 0 90 E:\mssql\data\tempdb.mdf NULL
>
> fileid groupid size maxsize growth status perf dbid name filename
> 1 1 1024 -1 10 1048578 0 2 tempdev E:\mssql\data\tempdb.mdf
> 2 0 64 -1 10 1048642 0 2 templog E:\mssql\data\templog.ldf
>
> However tempdb's data and log files are are not on the disk. I searched for
> them using Agent Ransack (as well as Windows Explorer).
> --
> Keith Kratochvil
>
> "Sebastian" <sebastian@.waksmundzcy.com.pl> wrote in message
> news:%23Bnb$FJGHHA.2456@.TK2MSFTNGP06.phx.gbl...
> > Keith Kratochvil wrote:
> >> I am receiving the following message within the Application Event Log on
> >> one of my servers.
> >> Could not create tempdb. You may not have enough disk space available.
> >> Free additional disk space by deleting other files on the tempdb drive
> >> and then restart SQL Server. Check for additional errors in the event log
> >> that may indicate why the tempdb files could not be initialized.
> >>
> >> I am also receiving this error:
> >> The database 'model' is marked RESTORING and is in a state that does not
> >> allow recovery to be run.
> >>
> >> The strange thing about this message is that the server was working
> >> correctly yesterday. The only thing that changed: The server was shut
> >> down and moved to a new data center. Connectivity is in place because I
> >> can connect to the box via Remote Desktop from work and from home.
> >>
> >>
> >>
> >> This error is ONLYhappening on the default instance. There are two other
> >> instances on the server (all three SQL Server installs are running under
> >> the same network account).
> >>
> >>
> >> There is enough free space on the volumes.
> >> OS: 24GB free
> >> internal array: 650 GB free
> >> external array (MSA 500 G2): 900GB free
> >>
> >> I even tried starting that instance in single user mode from the command
> >> prompt via:
> >> sqlservr -smssqlserver -c -f -m -T3608
> >> This worked and I tried moving tempdb to the different volumes that are
> >> available on the box. When I try to start SQL Server I receive the same
> >> errors about model and tempdb and this instance fails to start.
> >>
> >>
> >> I appreciate any assistance you can provide!
> >>
> >
> > Hi
> >
> > Check your logs(ldf) file size
> >
> > regards
> > SW

Could not create tempdb - SQL Server 2005 with SP1

Friday, February 17, 2012

Could anyone help? backup error

Database: SQL2000
OS: Windows 2000 SP4
Backup device: local hard disk (E Drive)

When I backup the database I got this error: BackupMedium::ReportIoError: write failure on backup device 'E:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\5WavesDB'. Operating system error 112(There is not enough space on the disk.).

My backup file only needs 4G and my E Drive has 13G free. My log files has been set to "growth automatically". Does anyone help to give some advise on this. Thank you for any help.you'd get this error if your data and log device sizes exceed 13g. try to shrink your log device(-s). if this operation does not result in a smaller log device size check for open trans in your database.|||Have you ran chkdsk on this disk? If you really have 13g free it shouldn't be an issue.
Just as an fyi, if you are not doing transaction log backups you need to set your recovery mode to Simple on your databases. Otherwise, your transaction logs will get huge.

Corrupting database

Hello:
I am using SQL 2005 on a W2K3 Standard server. The database is being
installed to a external HP disk cage called an MSA 30. After the database
installs it become corrupt almost right away. Does anyone have any
experience with SQL databases on external disk cages.
Harrison MidkiffHarrison,
There is no logical difference between an internal disk and an external disk
array as far as SQL Server is concerned. I would bet your problem is caused
by some hardware anomaly. I copied this from my prior post on another group:
I've seen similar things happen with intermittent h/w failures. In one
specific case it was a newer Perc card that was supposed to be backward
compatible with an older disk array. It wasn't, and would cause the server
to shut down intermittently. It did leave bread crumbs in the Event Log, so
we were able to work our way through it. You might want to check the Event
Log.
Check the SQL Server Log and the Windows Event Log. I bet there is a
reference to some sort of I/O or other hardware error. Possibly, you have a
version compatibility issue with your SCSI controller or drivers as I did.
Or, you may have some sort of fatal hardware issue with the array itself. If
there is no error there, I would suspect faulty write cacheing on the array
side. Turn off write cacheing if it is on.
-- Bill
"Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
> Hello:
> I am using SQL 2005 on a W2K3 Standard server. The database is being
> installed to a external HP disk cage called an MSA 30. After the database
> installs it become corrupt almost right away. Does anyone have any
> experience with SQL databases on external disk cages.
> Harrison Midkiff
>|||Hi
Use SQLIOSim, available from http://support.microsoft.com/kb/231619 to test
your disk subsystem.
It sounds like you have an IO system that is not performing correctly.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"AlterEgo" <alterego55@.dslextreme.com> wrote in message
news:OWK%238o%23SHHA.4252@.TK2MSFTNGP05.phx.gbl...
> Harrison,
> There is no logical difference between an internal disk and an external
> disk array as far as SQL Server is concerned. I would bet your problem is
> caused by some hardware anomaly. I copied this from my prior post on
> another group:
> I've seen similar things happen with intermittent h/w failures. In one
> specific case it was a newer Perc card that was supposed to be backward
> compatible with an older disk array. It wasn't, and would cause the server
> to shut down intermittently. It did leave bread crumbs in the Event Log,
> so
> we were able to work our way through it. You might want to check the Event
> Log.
> Check the SQL Server Log and the Windows Event Log. I bet there is a
> reference to some sort of I/O or other hardware error. Possibly, you have
> a version compatibility issue with your SCSI controller or drivers as I
> did. Or, you may have some sort of fatal hardware issue with the array
> itself. If there is no error there, I would suspect faulty write cacheing
> on the array side. Turn off write cacheing if it is on.
> -- Bill
>
> "Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
> news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
>

Corrupting database

Hello:
I am using SQL 2005 on a W2K3 Standard server. The database is being
installed to a external HP disk cage called an MSA 30. After the database
installs it become corrupt almost right away. Does anyone have any
experience with SQL databases on external disk cages.
Harrison MidkiffHarrison,
There is no logical difference between an internal disk and an external disk
array as far as SQL Server is concerned. I would bet your problem is caused
by some hardware anomaly. I copied this from my prior post on another group:
I've seen similar things happen with intermittent h/w failures. In one
specific case it was a newer Perc card that was supposed to be backward
compatible with an older disk array. It wasn't, and would cause the server
to shut down intermittently. It did leave bread crumbs in the Event Log, so
we were able to work our way through it. You might want to check the Event
Log.
Check the SQL Server Log and the Windows Event Log. I bet there is a
reference to some sort of I/O or other hardware error. Possibly, you have a
version compatibility issue with your SCSI controller or drivers as I did.
Or, you may have some sort of fatal hardware issue with the array itself. If
there is no error there, I would suspect faulty write cacheing on the array
side. Turn off write cacheing if it is on.
-- Bill
"Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
> Hello:
> I am using SQL 2005 on a W2K3 Standard server. The database is being
> installed to a external HP disk cage called an MSA 30. After the database
> installs it become corrupt almost right away. Does anyone have any
> experience with SQL databases on external disk cages.
> Harrison Midkiff
>|||Hi
Use SQLIOSim, available from http://support.microsoft.com/kb/231619 to test
your disk subsystem.
It sounds like you have an IO system that is not performing correctly.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"AlterEgo" <alterego55@.dslextreme.com> wrote in message
news:OWK%238o%23SHHA.4252@.TK2MSFTNGP05.phx.gbl...
> Harrison,
> There is no logical difference between an internal disk and an external
> disk array as far as SQL Server is concerned. I would bet your problem is
> caused by some hardware anomaly. I copied this from my prior post on
> another group:
> I've seen similar things happen with intermittent h/w failures. In one
> specific case it was a newer Perc card that was supposed to be backward
> compatible with an older disk array. It wasn't, and would cause the server
> to shut down intermittently. It did leave bread crumbs in the Event Log,
> so
> we were able to work our way through it. You might want to check the Event
> Log.
> Check the SQL Server Log and the Windows Event Log. I bet there is a
> reference to some sort of I/O or other hardware error. Possibly, you have
> a version compatibility issue with your SCSI controller or drivers as I
> did. Or, you may have some sort of fatal hardware issue with the array
> itself. If there is no error there, I would suspect faulty write cacheing
> on the array side. Turn off write cacheing if it is on.
> -- Bill
>
> "Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
> news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
>> Hello:
>> I am using SQL 2005 on a W2K3 Standard server. The database is being
>> installed to a external HP disk cage called an MSA 30. After the
>> database installs it become corrupt almost right away. Does anyone have
>> any experience with SQL databases on external disk cages.
>> Harrison Midkiff
>

Saturday, February 25, 2012

Could not create tempdb - SQL Server 2005 with SP1

Could not create tempdb - SQL Server 2005 with SP1

Could not create tempdb - SQL Server 2005 with SP1

Friday, February 17, 2012

Could anyone help? backup error

Corrupting database

Corrupting database

Counter settings

Blog Archive

About Me