SBS Server 2003 Hangs When Disk Is Full

[Guest James B]

Hi,

Our SBS 2003 Server ‘hung’ while writing to a drive that didn’t have

enough space for all the files being copied. A similar situation happened

last week when a removable drive went bad and data was transferred to it. The

server was completely unresponsive and had to be powered down.

 

I would assume that the copy/write process should fail in the even of a

full drive but not lock up the system.

 

When this happened, the Application Event Log had 8001, 8017 & 8019 errors

and the System Event Log had a 7011 error and 98 & 7036 information entries.

No other events were logged between 12:49 am and when I rebooted the server

at 5:33 am.

 

Any ideas about how to avoid this type of system hang would be greatly

appreciated.

 

 

Thanks,

James

 

Dell PowerEdge 2900 III, 2 Quad Core Xeons, 4GB RAM

SBS 2003 Server Premium R2 (all service packs & updates)

 

Application Log:

 

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8001

Date: 4/15/2008

Time: 12:40:39 AM

User: N/A

Computer: SERVER-NAME

Description:

End Backup of 'E:' 'Warnings or errors were encountered.'

 

Verify: Off

Mode: Replace

Type: Normal

 

Consult the backup report for more details.

 

----------

 

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8017

Date: 4/15/2008

Time: 12:40:39 AM

User: N/A

Computer: SERVER-NAME

Description:

NTBackup error: 'An inconsistency was encountered in the requested backup

file.'

 

----------

 

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8019

Date: 4/15/2008

Time: 12:40:40 AM

User: N/A

Computer: SERVER-NAME

Description:

End Operation: Warnings or errors were encountered.

Consult the backup report for more details.

 

----------

 

Event Type: Error

Event Source: NTBackup

Event Category: None

Event ID: 8019

Date: 4/15/2008

Time: 12:43:05 AM

User: N/A

Computer: SERVER-NAME

Description:

End Operation: Warnings or errors were encountered.

Consult the backup report for more details.

 

----------

 

System Log:

 

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7011

Date: 4/15/2008

Time: 12:44:24 AM

User: N/A

Computer: SERVER-NAME

Description:

Timeout (30000 milliseconds) waiting for a transaction response from the

NtFrs service.

 

----------

 

Event Type: Information

Event Source: Removable Storage Service

Event Category: None

Event ID: 98

Date: 4/15/2008

Time: 12:44:30 AM

User: N/A

Computer: SERVER-NAME

Description:

RSM was stopped.

 

----------

 

Event Type: Information

Event Source: Service Control Manager

Event Category: None

Event ID: 7036

Date: 4/15/2008

Time: 12:44:31 AM

User: N/A

Computer: SERVER-NAME

Description:

The Removable Storage service entered the stopped state.

 

----------

 

Event Type: Information

Event Source: Service Control Manager

Event Category: None

Event ID: 7036

Date: 4/15/2008

Time: 12:46:05 AM

User: N/A

Computer: SERVER-NAME

Description:

The Volume Shadow Copy service entered the stopped state.

 

----------

 

Event Type: Information

Event Source: Service Control Manager

Event Category: None

Event ID: 7036

Date: 4/15/2008

Time: 12:49:05 AM

User: N/A

Computer: SERVER-NAME

Description:

The Microsoft Software Shadow Copy Provider service entered the stopped state.

[Guest Pegasus \(MVP\)]

Re: SBS Server 2003 Hangs When Disk Is Full

 

 

"James B" <JamesB@discussions.microsoft.com> wrote in message

news:5ABFFA86-0984-42BF-9A46-2B2E922AF447@microsoft.com...

> Hi,

> Our SBS 2003 Server 'hung' while writing to a drive that didn't have

> enough space for all the files being copied. A similar situation happened

> last week when a removable drive went bad and data was transferred to it.

> The

> server was completely unresponsive and had to be powered down.

>

> I would assume that the copy/write process should fail in the even of a

> full drive but not lock up the system.

>

> When this happened, the Application Event Log had 8001, 8017 & 8019

> errors

> and the System Event Log had a 7011 error and 98 & 7036 information

> entries.

> No other events were logged between 12:49 am and when I rebooted the

> server

> at 5:33 am.

>

> Any ideas about how to avoid this type of system hang would be greatly

> appreciated.

>

>

> Thanks,

> James

 

In an ideal world, Windows would continue to run with all volumes

filled to the hilt. In a practical world this does not necessarily

happen, which means that you have to get up at 5am to fix things.

 

The obvious answer would seem to be: Never allow your server

disks to become full. Good server maintenance means (among

other things) that each partition must at all times have no less than

20% spare capacity. An easy way to monitor this is to get the

Task Scheduler to send a status report once a week to the

server administrator.

[Guest James B]

Re: SBS Server 2003 Hangs When Disk Is Full

 

Pegasus,

The drive filling up was due to an error in a script and is not a normal

occurrence. I'm just very surprised that a full secondary disk (not the boot

disk) or a bad block would hang the server. Even XP or Win2K Server generates

an error and goes on with its business rather than stopping the system.

 

 

Thanks,

James

 

"Pegasus (MVP)" wrote:

>

> "James B" <JamesB@discussions.microsoft.com> wrote in message

> news:5ABFFA86-0984-42BF-9A46-2B2E922AF447@microsoft.com...

> > Hi,

> > Our SBS 2003 Server 'hung' while writing to a drive that didn't have

> > enough space for all the files being copied. A similar situation happened

> > last week when a removable drive went bad and data was transferred to it.

> > The

> > server was completely unresponsive and had to be powered down.

> >

> > I would assume that the copy/write process should fail in the even of a

> > full drive but not lock up the system.

> >

> > When this happened, the Application Event Log had 8001, 8017 & 8019

> > errors

> > and the System Event Log had a 7011 error and 98 & 7036 information

> > entries.

> > No other events were logged between 12:49 am and when I rebooted the

> > server

> > at 5:33 am.

> >

> > Any ideas about how to avoid this type of system hang would be greatly

> > appreciated.

> >

> >

> > Thanks,

> > James

>

> In an ideal world, Windows would continue to run with all volumes

> filled to the hilt. In a practical world this does not necessarily

> happen, which means that you have to get up at 5am to fix things.

>

> The obvious answer would seem to be: Never allow your server

> disks to become full. Good server maintenance means (among

> other things) that each partition must at all times have no less than

> 20% spare capacity. An easy way to monitor this is to get the

> Task Scheduler to send a status report once a week to the

> server administrator.

>

>

>

[Guest zeiss]

Re: SBS Server 2003 Hangs When Disk Is Full

 

check Removable Storage Service. Set it to Manual

 

"James B" wrote:

> Pegasus,

> The drive filling up was due to an error in a script and is not a normal

> occurrence. I'm just very surprised that a full secondary disk (not the boot

> disk) or a bad block would hang the server. Even XP or Win2K Server generates

> an error and goes on with its business rather than stopping the system.

>

>

> Thanks,

> James

>

> "Pegasus (MVP)" wrote:

>

> >

> > "James B" <JamesB@discussions.microsoft.com> wrote in message

> > news:5ABFFA86-0984-42BF-9A46-2B2E922AF447@microsoft.com...

> > > Hi,

> > > Our SBS 2003 Server 'hung' while writing to a drive that didn't have

> > > enough space for all the files being copied. A similar situation happened

> > > last week when a removable drive went bad and data was transferred to it.

> > > The

> > > server was completely unresponsive and had to be powered down.

> > >

> > > I would assume that the copy/write process should fail in the even of a

> > > full drive but not lock up the system.

> > >

> > > When this happened, the Application Event Log had 8001, 8017 & 8019

> > > errors

> > > and the System Event Log had a 7011 error and 98 & 7036 information

> > > entries.

> > > No other events were logged between 12:49 am and when I rebooted the

> > > server

> > > at 5:33 am.

> > >

> > > Any ideas about how to avoid this type of system hang would be greatly

> > > appreciated.

> > >

> > >

> > > Thanks,

> > > James

> >

> > In an ideal world, Windows would continue to run with all volumes

> > filled to the hilt. In a practical world this does not necessarily

> > happen, which means that you have to get up at 5am to fix things.

> >

> > The obvious answer would seem to be: Never allow your server

> > disks to become full. Good server maintenance means (among

> > other things) that each partition must at all times have no less than

> > 20% spare capacity. An easy way to monitor this is to get the

> > Task Scheduler to send a status report once a week to the

> > server administrator.

> >

> >

> >

[Guest James B]

Re: SBS Server 2003 Hangs When Disk Is Full

 

Zeiss,

The Removable Storage service is set to manual and is not running. I'll

check the logs to see if it was turned on by something. Thanks for the tip.

 

 

James B

 

 

"zeiss" wrote:

> check Removable Storage Service. Set it to Manual

>

> "James B" wrote:

>

> > Pegasus,

> > The drive filling up was due to an error in a script and is not a normal

> > occurrence. I'm just very surprised that a full secondary disk (not the boot

> > disk) or a bad block would hang the server. Even XP or Win2K Server generates

> > an error and goes on with its business rather than stopping the system.

> >

> >

> > Thanks,

> > James

> >

> > "Pegasus (MVP)" wrote:

> >

> > >

> > > "James B" <JamesB@discussions.microsoft.com> wrote in message

> > > news:5ABFFA86-0984-42BF-9A46-2B2E922AF447@microsoft.com...

> > > > Hi,

> > > > Our SBS 2003 Server 'hung' while writing to a drive that didn't have

> > > > enough space for all the files being copied. A similar situation happened

> > > > last week when a removable drive went bad and data was transferred to it.

> > > > The

> > > > server was completely unresponsive and had to be powered down.

> > > >

> > > > I would assume that the copy/write process should fail in the even of a

> > > > full drive but not lock up the system.

> > > >

> > > > When this happened, the Application Event Log had 8001, 8017 & 8019

> > > > errors

> > > > and the System Event Log had a 7011 error and 98 & 7036 information

> > > > entries.

> > > > No other events were logged between 12:49 am and when I rebooted the

> > > > server

> > > > at 5:33 am.

> > > >

> > > > Any ideas about how to avoid this type of system hang would be greatly

> > > > appreciated.

> > > >

> > > >

> > > > Thanks,

> > > > James

> > >

> > > In an ideal world, Windows would continue to run with all volumes

> > > filled to the hilt. In a practical world this does not necessarily

> > > happen, which means that you have to get up at 5am to fix things.

> > >

> > > The obvious answer would seem to be: Never allow your server

> > > disks to become full. Good server maintenance means (among

> > > other things) that each partition must at all times have no less than

> > > 20% spare capacity. An easy way to monitor this is to get the

> > > Task Scheduler to send a status report once a week to the

> > > server administrator.

> > >

> > >

> > >