How to look up error codes without the FSDK?

NTFSD
1

I sometimes see disk errors in our installled base that aren’t documented in
the DDK as far as I see, and I’d like to be able to look up such error
codes. I’m not a file system developer and thus don’t have the development
kit.

For example, today I saw FTDISK event ID 6 “The device \Device\Harddisk0\Ft1
that is part of a fault tolerance set has failed and will no longer be
used.” with the data
0000: 00 00 00 00 01 00 56 00 …V.
0008: 00 00 00 00 06 00 05 c0 …?
0010: 00 00 00 00 00 00 00 00 …
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
Which indicates that the ErrorCode was 0xC0050006, but I can’t find that
code anywhere, not even with a Google search.

Note that I’m not debugging any file system driver – I’m just hoping that
the error code will give me a clue as to what is wrong with the drive /
system / etc.

Any suggestions as to how I should tackle such things in the future? If
there’s no way short of owning the file system development kit, could
someone do me a favor and send me the relevant header file and/or just look
up that one error for me?

Thanks!

2

No header file would give you any more information than that:-(

–
Kind regards, Dejan M. MVP for DDK
http://www.alfasp.com E-mail: xxxxx@alfasp.com
Alfa Transparent File Encryptor - Transparent file encryption services.
Alfa File Protector - File protection and hiding library for Win32
developers.
Alfa File Monitor - File monitoring library for Win32 developers.

3

How to look up error codes without the FSDK?Seems to be plain English. It’s
broke and isn’t going to be used. Look in the other event logs and see if
the disk driver logged any errors. Why are you trying to run a fault
tolerant system without the Resource Kit? Also, use plaintext and no HTML
in newsgroups. I need more viruses like another hole in my head and the
summaries don’t work well with HTML.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd…
I sometimes see disk errors in our installled base that aren’t documented in
the DDK as far as I see, and I’d like to be able to look up such error
codes. I’m not a file system developer and thus don’t have the development
kit.
For example, today I saw FTDISK event ID 6 “The device \Device\Harddisk0\Ft1
that is part of a fault tolerance set has failed and will no longer be
used.” with the data
0000: 00 00 00 00 01 00 56 00 …V.
0008: 00 00 00 00 06 00 05 c0 …À
0010: 00 00 00 00 00 00 00 00 …
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
Which indicates that the ErrorCode was 0xC0050006, but I can’t find that
code anywhere, not even with a Google search.
Note that I’m not debugging any file system driver – I’m just hoping that
the error code will give me a clue as to what is wrong with the drive /
system / etc.
Any suggestions as to how I should tackle such things in the future? If
there’s no way short of owning the file system development kit, could
someone do me a favor and send me the relevant header file and/or just look
up that one error for me?
Thanks!

4

I guess I wasn’t clear. My question is NOT about the Event Log message
(which I understand); I just put that there for some context.

My question is about the error code 0xC0050006 which is embedded inside the
Event Log message, which is seemingly the error code returned from the SCSI
miniport driver, in this case, ATAPI.SYS.

In this case, the error code is 0xC0050006. In other cases, I’ve seen
0xC0040009 (which I did find in NTIOSTAT.H or somesuch), which is
IO_ERR_TIMEOUT. Apparently, multiple error codes can lead to the same event
log message.

So, given error code 0xC0050006, how do I find out what that error means?

Look in the other event logs and see if the disk driver logged any errors.

Amazingly, there are no other errors – the mirror is just suddenly broken.
I know that one would expect to see timeouts, controller errors, or
somesuch, but in this case (and a few others), there is nothing. Hence, my
particular interest in what the error code really means.

Why are you trying to run a fault tolerant system without the Resource
Kit?

We do have the NT Resource Kit, and I don’t see how that helps in this
situation since it doesn’t contain the header files. The DDK does contain
most of header files, but seemingly not those for some of the file system.

[Sorry about the non-plain-text; that drives me nuts on NTDEV as well. I
just subscribed to NTFSD, and forgot to set that…]

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Monday, 27 October, 2003 5:59 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Re: How to look up error codes without the FSDK?

How to look up error codes without the FSDK?Seems to be plain English. It’s
broke and isn’t going to be used. Look in the other event logs and see if
the disk driver logged any errors. Why are you trying to run a fault
tolerant system without the Resource Kit? Also, use plaintext and no HTML
in newsgroups. I need more viruses like another hole in my head and the
summaries don’t work well with HTML.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd…
I sometimes see disk errors in our installled base that aren’t documented in
the DDK as far as I see, and I’d like to be able to look up such error
codes. I’m not a file system developer and thus don’t have the development
kit.
For example, today I saw FTDISK event ID 6 “The device \Device\Harddisk0\Ft1
that is part of a fault tolerance set has failed and will no longer be
used.” with the data
0000: 00 00 00 00 01 00 56 00 …V.
0008: 00 00 00 00 06 00 05 c0 …?
0010: 00 00 00 00 00 00 00 00 …
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
Which indicates that the ErrorCode was 0xC0050006, but I can’t find that
code anywhere, not even with a Google search.
Note that I’m not debugging any file system driver – I’m just hoping that
the error code will give me a clue as to what is wrong with the drive /
system / etc.
Any suggestions as to how I should tackle such things in the future? If
there’s no way short of owning the file system development kit, could
someone do me a favor and send me the relevant header file and/or just look
up that one error for me?
Thanks!

—
You are currently subscribed to ntfsd as: xxxxx@vertical.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

The 0006 part is given in MSDN and an event ID for ftdisk. The only other
way I can find is the source code to NT. It appears from some of your
comments that this is NT and not W2K or 2003. Maybe Microsoft still offers
some support for NT, but I thought it was going to be dropped. If you look
up the 0006 in MSDN you get the same text given in your message.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd…

I guess I wasn’t clear. My question is NOT about the Event Log message
(which I understand); I just put that there for some context.

My question is about the error code 0xC0050006 which is embedded inside the
Event Log message, which is seemingly the error code returned from the SCSI
miniport driver, in this case, ATAPI.SYS.

In this case, the error code is 0xC0050006. In other cases, I’ve seen
0xC0040009 (which I did find in NTIOSTAT.H or somesuch), which is
IO_ERR_TIMEOUT. Apparently, multiple error codes can lead to the same event
log message.

So, given error code 0xC0050006, how do I find out what that error means?

> Look in the other event logs and see if the disk driver logged any errors.

Amazingly, there are no other errors – the mirror is just suddenly broken.
I know that one would expect to see timeouts, controller errors, or
somesuch, but in this case (and a few others), there is nothing. Hence, my
particular interest in what the error code really means.

> Why are you trying to run a fault tolerant system without the Resource
Kit?

We do have the NT Resource Kit, and I don’t see how that helps in this
situation since it doesn’t contain the header files. The DDK does contain
most of header files, but seemingly not those for some of the file system.

[Sorry about the non-plain-text; that drives me nuts on NTDEV as well. I
just subscribed to NTFSD, and forgot to set that…]

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Monday, 27 October, 2003 5:59 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Re: How to look up error codes without the FSDK?

How to look up error codes without the FSDK?Seems to be plain English. It’s
broke and isn’t going to be used. Look in the other event logs and see if
the disk driver logged any errors. Why are you trying to run a fault
tolerant system without the Resource Kit? Also, use plaintext and no HTML
in newsgroups. I need more viruses like another hole in my head and the
summaries don’t work well with HTML.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd…
I sometimes see disk errors in our installled base that aren’t documented in
the DDK as far as I see, and I’d like to be able to look up such error
codes. I’m not a file system developer and thus don’t have the development
kit.
For example, today I saw FTDISK event ID 6 “The device \Device\Harddisk0\Ft1
that is part of a fault tolerance set has failed and will no longer be
used.” with the data
0000: 00 00 00 00 01 00 56 00 …V.
0008: 00 00 00 00 06 00 05 c0 …À
0010: 00 00 00 00 00 00 00 00 …
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
Which indicates that the ErrorCode was 0xC0050006, but I can’t find that
code anywhere, not even with a Google search.
Note that I’m not debugging any file system driver – I’m just hoping that
the error code will give me a clue as to what is wrong with the drive /
system / etc.
Any suggestions as to how I should tackle such things in the future? If
there’s no way short of owning the file system development kit, could
someone do me a favor and send me the relevant header file and/or just look
up that one error for me?
Thanks!

—
You are currently subscribed to ntfsd as: xxxxx@vertical.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

6

Could this be a custom error code? Bits 16-27 form a facility code (5 in this case), which is not defined in my copy of ntstatus.h. The top 2 bits are a severity code (3 in this case means “Error”). Even if you had the fsdk, it wouldn’t help. I don’t find this error code in my copy.

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Tuesday, October 28, 2003 11:04 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Re: How to look up error codes without the FSDK?

The 0006 part is given in MSDN and an event ID for ftdisk. The only other way I can find is the source code to NT. It appears from some of your comments that this is NT and not W2K or 2003. Maybe Microsoft still offers some support for NT, but I thought it was going to be dropped. If you look up the 0006 in MSDN you get the same text given in your message.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd…

I guess I wasn’t clear. My question is NOT about the Event Log message (which I understand); I just put that there for some context.

My question is about the error code 0xC0050006 which is embedded inside the Event Log message, which is seemingly the error code returned from the SCSI miniport driver, in this case, ATAPI.SYS.

In this case, the error code is 0xC0050006. In other cases, I’ve seen 0xC0040009 (which I did find in NTIOSTAT.H or somesuch), which is IO_ERR_TIMEOUT. Apparently, multiple error codes can lead to the same event log message.

So, given error code 0xC0050006, how do I find out what that error means?

> Look in the other event logs and see if the disk driver logged any
> errors.

Amazingly, there are no other errors – the mirror is just suddenly broken. I know that one would expect to see timeouts, controller errors, or somesuch, but in this case (and a few others), there is nothing. Hence, my particular interest in what the error code really means.

> Why are you trying to run a fault tolerant system without the Resource
Kit?

We do have the NT Resource Kit, and I don’t see how that helps in this situation since it doesn’t contain the header files. The DDK does contain most of header files, but seemingly not those for some of the file system.

[Sorry about the non-plain-text; that drives me nuts on NTDEV as well. I just subscribed to NTFSD, and forgot to set that…]

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Monday, 27 October, 2003 5:59 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Re: How to look up error codes without the FSDK?

How to look up error codes without the FSDK?Seems to be plain English. It’s broke and isn’t going to be used. Look in the other event logs and see if the disk driver logged any errors. Why are you trying to run a fault tolerant system without the Resource Kit? Also, use plaintext and no HTML in newsgroups. I need more viruses like another hole in my head and the summaries don’t work well with HTML.

“Taed Wynnell” wrote in message news:xxxxx@ntfsd… I sometimes see disk errors in our installled base that aren’t documented in the DDK as far as I see, and I’d like to be able to look up such error codes. I’m not a file system developer and thus don’t have the development kit. For example, today I saw FTDISK event ID 6 “The device \Device\Harddisk0\Ft1 that is part of a fault tolerance set has failed and will no longer be used.” with the data
0000: 00 00 00 00 01 00 56 00 …V.
0008: 00 00 00 00 06 00 05 c0 …?
0010: 00 00 00 00 00 00 00 00 …
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
Which indicates that the ErrorCode was 0xC0050006, but I can’t find that code anywhere, not even with a Google search. Note that I’m not debugging any file system driver – I’m just hoping that the error code will give me a clue as to what is wrong with the drive / system / etc. Any suggestions as to how I should tackle such things in the future? If there’s no way short of owning the file system development kit, could someone do me a favor and send me the relevant header file and/or just look up that one error for me? Thanks!

—
You are currently subscribed to ntfsd as: xxxxx@vertical.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@avid.com To unsubscribe send a blank email to xxxxx@lists.osr.com