More then 10 disks and disk error in event log KB923356

[Puppethead@gmail.com]

HI All,

This is a Windows 2003 Enterprise Server SP2 and it is connected to
our SAN. It can see over 30 disks.

The event log shows:

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 7/6/2007
Time: 4:40:44 PM
User: N/A
Computer: DATASERVER
Description:
The driver detected a controller error on \Device\Harddisk2.

According to KB 923356 the drive number is truncated at the first
number. So \Device\Harddisk2. could be 2 or 20-29. We get this error
over and over but cannot tell which disk it is because of the
truncation. If we could find out what disk is making the errors we
might be able to continue trouble shooting the problem.

Does anyone know of a way to make the error return the whole disk #?

Thanks,

Allen

 

[John Toner [MVP]]

There's currently no way. This is supposed to be fixed in Longhorn

Only way to figure out which disk is triggering this would be to use LUN
masking and try removing disks one at a time.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

wrote in message
news:1184007479.629269.46690@m37g2000prh.googlegroups.com...
> HI All,
>
> This is a Windows 2003 Enterprise Server SP2 and it is connected to
> our SAN. It can see over 30 disks.
>
> The event log shows:
>
> Event Type: Error
> Event Source: Disk
> Event Category: None
> Event ID: 11
> Date: 7/6/2007
> Time: 4:40:44 PM
> User: N/A
> Computer: DATASERVER
> Description:
> The driver detected a controller error on \Device\Harddisk2.
>
> According to KB 923356 the drive number is truncated at the first
> number. So \Device\Harddisk2. could be 2 or 20-29. We get this error
> over and over but cannot tell which disk it is because of the
> truncation. If we could find out what disk is making the errors we
> might be able to continue trouble shooting the problem.
>
> Does anyone know of a way to make the error return the whole disk #?
>
> Thanks,
>
> Allen
>

 

[Puppethead@gmail.com]

On Jul 10, 11:23 am, "John Toner [MVP]" <jto...@DIE.SPAM.DIE.mvps.org>
wrote:
> There's currently no way. This is supposed to be fixed in Longhorn
>
> Only way to figure out which disk is triggering this would be to use LUN
> masking and try removingdisksone at a time.
>
> Regards,
> John
>
> Visit my blog:http://msmvps.com/blogs/jtoner
>
> wrote in message
>
> news:1184007479.629269.46690@m37g2000prh.googlegroups.com...
>
>
>
> > HI All,
>
> > This is a Windows 2003 Enterprise Server SP2 and it is connected to
> > our SAN. It can see over 30disks.
>
> > The event log shows:
>
> > Event Type: Error
> > Event Source: Disk
> > Event Category: None
> > Event ID: 11
> > Date: 7/6/2007
> > Time: 4:40:44 PM
> > User: N/A
> > Computer: DATASERVER
> > Description:
> > The driver detected a controller error on \Device\Harddisk2.
>
> > According to KB 923356 the drive number is truncated at the first
> > number. So \Device\Harddisk2. could be 2 or 20-29. We get this error
> > over and over but cannot tell which disk it is because of the
> > truncation. If we could find out what disk is making the errors we
> > might be able to continue trouble shooting the problem.
>
> > Does anyone know of a way to make the error return the whole disk #?
>
> > Thanks,
>
> > Allen- Hide quoted text -
>
> - Show quoted text -

Thanks input.
-Allen