STATUS_CRC_ERROR error

NTDEV
1

Hi All,

I want to know which driver will return the NTSTATUS values mentioned in
ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
I/O) storage system or on a normal system.

I found many driver files in the device stack (mpio.sys, mpspfltr.sys,
mpdev.sys, partmgr.sys, etc) and could not find out which one returns this
error. I have written a filter driver for this purpose (targeting DiskDrive
classID) and it is lying on top of
"(lowest)mpspfltr->mpdev->partmgr->MyDriver(Higest) " stack. And found that
it should be partmgr.sys, that should return the (read/write related)errors.
Can any one help me in this regard.

Thanks and Regards
Ramesh

–

Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

2

It can even be a Disk class driver which mapped some SCSI sense info to
this status.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Ramesh K”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, January 05, 2005 7:35 PM
Subject: [ntdev] STATUS_CRC_ERROR error

Hi All,

I want to know which driver will return the NTSTATUS values mentioned in
ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
I/O) storage system or on a normal system.

I found many driver files in the device stack (mpio.sys, mpspfltr.sys,
mpdev.sys, partmgr.sys, etc) and could not find out which one returns this
error. I have written a filter driver for this purpose (targeting DiskDrive
classID) and it is lying on top of
"(lowest)mpspfltr->mpdev->partmgr->MyDriver(Higest) " stack. And found that
it should be partmgr.sys, that should return the (read/write related)errors.
Can any one help me in this regard.

Thanks and Regards
Ramesh

–
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Ramesh K wrote:

I want to know which driver will return the NTSTATUS values mentioned in
ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
I/O) storage system or on a normal system.

You do understand that any driver can return any status error it wants,
right? And that this is likely to change from release to release?

I know the floppy disk driver (and controller) return STATUS_CRC_ERROR.
There may be others… but I personally wouldn’t expect to get back a
CRC error from any of the mass storage drivers.

IS there something more specific that you’re looking for??

Peter
OSR

4

Hi Peter and Maxim,

Thanks for the replies.

Specifically I want to find whether the mpio will know about the different critical errors(CRC or PAGE_FAULT etc… ) or only the disk class drivers come to know about this errors.

Basically I am interested to know the mpio driver stack structure. Since mpio development kit also is not explaining much about this stack layer, I am not in a position to confirm who will handle such a situation? This knowledge will help me in developing the DSM (load balancing and etc).

Thanks and Regards
Ramesh

----- Original Message -----
From: “Peter Viscarola (OSR)”
To: “Windows System Software Devs Interest List”
Subject: Re:[ntdev] STATUS_CRC_ERROR error
Date: Wed, 05 Jan 2005 11:49:39 -0500

>
> Ramesh K wrote:
> >
> > I want to know which driver will return the NTSTATUS values mentioned in
> > ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
> > I/O) storage system or on a normal system.
> >
>
> You do understand that any driver can return any status error it
> wants, right? And that this is likely to change from release to
> release?
>
> I know the floppy disk driver (and controller) return
> STATUS_CRC_ERROR. There may be others… but I personally wouldn’t
> expect to get back a CRC error from any of the mass storage drivers.
>
> IS there something more specific that you’re looking for??
>
> Peter
> OSR
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@lycos.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

–
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

5

It can by ANY driver in the system that uses a cyclical redundancy check
algorhythm to verify day buffer contents. Or any driver that so desires to
use that status code, depending on how the developer wants to define CRC.
And next month he/she/it may decide to use another code or role his/hers/its
own.

“Ramesh K” wrote in message news:xxxxx@ntdev…
Hi All,

I want to know which driver will return the NTSTATUS values mentioned in
ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
I/O) storage system or on a normal system.

I found many driver files in the device stack (mpio.sys, mpspfltr.sys,
mpdev.sys, partmgr.sys, etc) and could not find out which one returns this
error. I have written a filter driver for this purpose (targeting DiskDrive
classID) and it is lying on top of
"(lowest)mpspfltr->mpdev->partmgr->MyDriver(Higest) " stack. And found that
it should be partmgr.sys, that should return the (read/write related)errors.
Can any one help me in this regard.

Thanks and Regards
Ramesh

–
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

6

Hi Peter and Maxim,

Thanks for the replies. I got a rejection mail since the content used a
restricted word. So execuse me for the repost.

Specifically I want to find whether the mpio will know about the different
critical errors(CRC or PAGE_FAULT etc… ) or only the disk class drivers
come to know about this errors.

Basically I am interested to know the mpio driver stack structure. Since
mpio development kit also is not explaining much about this driver stack, I
am not in a position to confirm who will handle such a situation? This
knowledge will help me in developing the DSM (load balancing and etc).
Experts please comment.

Thanks and Regards
Ramesh

----- Original Message -----
From: “Peter Viscarola (OSR)”
To: “Windows System Software Devs Interest List”
Subject: Re:[ntdev] STATUS_CRC_ERROR error
Date: Wed, 05 Jan 2005 11:49:39 -0500

>
> Ramesh K wrote:
> >
> > I want to know which driver will return the NTSTATUS values mentioned in
> > ntstatus.h (For example: STATUS_CRC_ERROR error) either on a mpio(Multi Path
> > I/O) storage system or on a normal system.
> >
>
> You do understand that any driver can return any status error it
> wants, right? And that this is likely to change from release to
> release?
>
> I know the floppy disk driver (and controller) return
> STATUS_CRC_ERROR. There may be others… but I personally wouldn’t
> expect to get back a CRC error from any of the mass storage drivers.
>
> IS there something more specific that you’re looking for??
>
> Peter
> OSR
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@lycos.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

–
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10