Archived from groups: microsoft.public.windowsxp.device_driver.dev (More info?)
Hi,
I'm asking this here because, while I was helped, I was unable to
resolve this problem in the WinXP/Hardware forum. I expect that driver
writers will know how to fix this...
WinXP SP1A, patches up to date.
I've got an Asus P4C800-E Deluxe motherboard, which has built-in Intel
and Promise RAID controllers. I have two SATA WD 120GB hard drives
connected to the Intel controller configured as RAID-0 (striped), and
two more SATA WD 120 GB drives connected to the Promise controller
configured as RAID-1 (mirrored). The RAID-0 array consists of drives C:
-> I: and the RAID-1 array is drive J:. I also have two USB drives used
to hold off-line backups, drives K: and L:.
I am using the latest (non-beta) version of the P4C800 BIOS (1017),
which includes the latest Intel RAID firmware (I was running an older
BIOS version when these problems surfaced, so I updated to see if this
would solve the problem). I am using the Intel Application Accelerator
RAID version.
The Event ID 11 message I get is "The driver detected a controller error
on \Device\Harddisk4\D". I've also had reports of this nature for
Harddisk5, Harddisk6, Harddisk7, Harddisk8, Hardisk9 and Harddisk10. The
latest version of the WD diagnostics report no errors.
The KB says that the most likely cause of these errors is a bad cable.
In checking my cables, I noticed that the plastic SATA connector on the
motherboard for one of the Intel RAID connections had come loose.
Thinking that this was my problem, I swapped out the motherboard but the
problems persist. I also swapped the cables on the Intel controller with
those on the Promise controller. Since the problem did not move with the
cables, I assume the cables are not the problem (I don't have spares but
I've got some on order now).
This leads me to believe that the problem must be on a drive rather than
in the controller or cable, but I'm not sure which drive is having
problems (or even which controller the problem drive is connected to).
Does this sound reasonable?
I've found several articles in the KB and in these newsgroups that
advise looking at key HKLM\HARDWARE\DEVICEMAP in the registry to find
this information. However, since my drives are on RAID controllers, I
have no IDE keys and the SCSI keys refer only to the RAID controllers.
For example, "HKLM\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target
Id 0\Logical Unit Id 0" reports an Identifier "RAID 0 Volume" and a Type
"DiskPeripheral".
Further research lead to me the dmdiag utility included in the Support
Tools. Running this utility with the -v (verbose) option yields the
results I've pasted at the end of this message. Nothing in these results
exactly matches the " \Device\Harddisk4\D" reported in the error. The
closest I see is "E: = \Device\HarddiskVolume4 [Fixed]", but since the
drive designation is different I don't want to assume they are the same.
Also, I have no idea what the "\D" in the error message means.
Also, as I mentioned above, I've had these errors on Harddisk9 and
Harddisk10 (but only once - Harddisk4 turns up in every error event -
when 9 and 10 were reported, it was in series of error events with 4, 5,
6, 7, and 8). Since Harddisk9 and Harddisk10 appear to be my USB drives,
I can't see how they can be involved in this issue at all. Since I have
not seen them in an error event since I swapped in the new motherboard,
perhaps it as an issue with the USB controller on the old MB.
Could someone please confirm that " \Device\Harddisk4\D" and
"\Device\HarddiskVolume4" refer to the same drive volume?
I'd also like to know why the volumes are reported differently in the
error event and in the dmdiag report (assuming they are indeed the same
volume), and what the "/D" in the error event means.
Thanks!
P.S. Am I correct in assuming that I can ignore the "LDM" errors below
as I don't have dynamic drive volumes?
---------- Computer Name and OS Version ----------
Computer name: LEROYWORK
NT build: 2600
CPU Type: x86
DMDIAG Version: 5.1.2600.0 shp
---------- Consolidated LDM Configuration Data ----------
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
ERROR: scan operation failed:
A format error was found in the private region of the disk
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.