Event ID 11, please help me identify the HD involved

From: Leroy Casterline (spamfreeme_at_nospam.com)
Date: 08/26/04

  • Next message: Ross: "No drivers"
    Date: Thu, 26 Aug 2004 17:42:48 -0600
    
    

    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

    ---------- LDM File Versions ----------

                  2600.0.503.0 shp - C:\WINDOWS\System32\dmadmin.exe
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmconfig.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmdlgs.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmdskmgr.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmdskres.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmintf.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmremote.exe
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmserver.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmutil.dll
                  2600.0.503.0 shp - C:\WINDOWS\System32\dmview.ocx
                  2600.0.503.0 shp - C:\WINDOWS\System32\drivers\dmboot.sys
                  2600.0.503.0 shp - C:\WINDOWS\System32\drivers\dmio.sys
                  2600.0.503.0 shp - C:\WINDOWS\System32\drivers\dmload.sys

    ---------- Mount Points ----------

    ---------- Drive Letter Usage, Drive Type ----------

    A: = \Device\Floppy0 [Removable]
    C: = \Device\HarddiskVolume2 [Fixed]
    D: = \Device\HarddiskVolume3 [Fixed]
    E: = \Device\HarddiskVolume4 [Fixed]
    F: = \Device\HarddiskVolume5 [Fixed]
    G: = \Device\HarddiskVolume6 [Fixed]
    H: = \Device\HarddiskVolume7 [Fixed]
    I: = \Device\HarddiskVolume8 [Fixed]
    J: = \Device\HarddiskVolume1 [Fixed]
    K: = \Device\HarddiskVolume9 [Fixed]
    L: = \Device\HarddiskVolume10 [Fixed]
    Y: = \Device\CdRom1 [CDRom]
    Z: = \Device\CdRom0 [CDRom]

    ---------- 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

    ---------- \Device\Harddisk0 ----------

    \Device\Harddisk0\DP(1)0x7e00-0x4e22c6e00+3 (Device)
    \Device\Harddisk0\DP(2)0x4e22d6a00-0x27115f800+4 (Device)
    \Device\Harddisk0\DP(3)0x75343e000-0x3a9627200+5 (Device)
    \Device\Harddisk0\DP(4)0xafca6d000-0xc34f24e00+6 (Device)
    \Device\Harddisk0\DP(5)0x1731999c00-0x15f8cea400+7 (Device)
    \Device\Harddisk0\DP(6)0x2d2a68be00-0x32c5df400+8 (Device)
    \Device\Harddisk0\DP(7)0x3056c73000-0x78d9a5200+9 (Device)
    \Device\Harddisk0\DR0 (Device)
    \Device\Harddisk0\Partition0 (SymbolicLink) -> \Device\Harddisk0\DR0
    \Device\Harddisk0\Partition1 (SymbolicLink) ->
    \Device\HarddiskVolume2
    \Device\Harddisk0\Partition2 (SymbolicLink) ->
    \Device\HarddiskVolume3
    \Device\Harddisk0\Partition3 (SymbolicLink) ->
    \Device\HarddiskVolume4
    \Device\Harddisk0\Partition4 (SymbolicLink) ->
    \Device\HarddiskVolume5
    \Device\Harddisk0\Partition5 (SymbolicLink) ->
    \Device\HarddiskVolume6
    \Device\Harddisk0\Partition6 (SymbolicLink) ->
    \Device\HarddiskVolume7
    \Device\Harddisk0\Partition7 (SymbolicLink) ->
    \Device\HarddiskVolume8

    ---------- \Device\Harddisk1 ----------

    \Device\Harddisk1\DP(1)0x7e00-0x1beffb7a00+2 (Device)
    \Device\Harddisk1\DR1 (Device)
    \Device\Harddisk1\Partition0 (SymbolicLink) -> \Device\Harddisk1\DR1
    \Device\Harddisk1\Partition1 (SymbolicLink) ->
    \Device\HarddiskVolume1

    ---------- \Device\Harddisk2 ----------

    \Device\Harddisk2\DP(1)0x7e00-0x1c9f7f4600+c (Device)
    \Device\Harddisk2\DR10 (Device)
    \Device\Harddisk2\Partition0 (SymbolicLink) ->
    \Device\Harddisk2\DR10
    \Device\Harddisk2\Partition1 (SymbolicLink) ->
    \Device\HarddiskVolume9

    ---------- \Device\Harddisk3 ----------

    \Device\Harddisk3\DP(1)0x7e00-0x2543150400+d (Device)
    \Device\Harddisk3\DR11 (Device)
    \Device\Harddisk3\Partition0 (SymbolicLink) ->
    \Device\Harddisk3\DR11
    \Device\Harddisk3\Partition1 (SymbolicLink) ->
    \Device\HarddiskVolume10

    ---------- Partition Table Info Disk 0 ----------

              29,186 Cylinders
                 255 Tracks/Cylinder
                  63 Sectors/Track
                 512 Bytes/Sector
                  12 MediaType
         468,873,090 Sectors (total)
     240,063,022,080 Bytes (total)
         234,436,545 KB
             228,942 MB
               223.6 GB

                   0 StartingOffset
     240,067,805,184 PartitionLength
                   0 HiddenSectors
                   0 PartitionNumber
                   0 PartitionType
                   0 BootIndicator
                   0 RecognizedPartition
                   0 RewritePartition

                 MBR PartitionStyle
                  28 PartitionCount
            1d641d63 Signature

            Starting Partition Hidden Total Partition
    Partition Boot Recognized Rewrite
      Offset (bytes) Length (bytes) Sectors Sectors Number
    Type (HEX) Indicator Partition Partition

              32,256 20,974,431,744 63 40,965,687 0
    0x07 1 1 0
      20,974,464,000 219,080,332,800 40,965,750 427,891,275 1
    0x05 0 0 0
                   0 0 0 0 2
    0x00 0 0 0
                   0 0 0 0 3
    0x00 0 0 0
      20,974,496,256 10,487,199,744 63 20,482,812 4
    0x07 0 1 0
      31,461,696,000 15,726,735,360 20,482,875 30,716,280 5
    0x05 0 0 0
                   0 0 0 0 6
    0x00 0 0 0
                   0 0 0 0 7
    0x00 0 0 0
      31,461,728,256 15,726,703,104 63 30,716,217 8
    0x07 0 1 0
      47,188,431,360 52,427,934,720 51,199,155 102,398,310 9
    0x05 0 0 0
                   0 0 0 0 10
    0x00 0 0 0
                   0 0 0 0 11
    0x00 0 0 0
      47,188,463,616 52,427,902,464 63 102,398,247 12
    0x07 0 1 0
      99,616,366,080 94,368,637,440 153,597,465 184,313,745 13
    0x05 0 0 0
                   0 0 0 0 14
    0x00 0 0 0
                   0 0 0 0 15
    0x00 0 0 0
      99,616,398,336 94,368,605,184 63 184,313,682 16
    0x07 0 1 0
     193,985,003,520 13,629,288,960 337,911,210 26,619,705 17
    0x05 0 0 0
                   0 0 0 0 18
    0x00 0 0 0
                   0 0 0 0 19
    0x00 0 0 0
     193,985,035,776 13,629,256,704 63 26,619,642 20
    0x07 0 1 0
     207,614,292,480 32,440,504,320 364,530,915 63,360,360 21
    0x05 0 0 0
                   0 0 0 0 22
    0x00 0 0 0
                   0 0 0 0 23
    0x00 0 0 0
     207,614,324,736 32,440,472,064 63 63,360,297 24
    0x07 0 1 0
                   0 0 0 0 25
    0x00 0 0 0
                   0 0 0 0 26
    0x00 0 0 0
                   0 0 0 0 27
    0x00 0 0 0

     240,063,022,080 Bytes (468873090 sectors) Geometric size
     240,067,805,184 Bytes (468882432 sectors) True size (measured)
     240,067,805,184 Bytes (468882432 sectors) Reported size (Partition0)
                   0 Bytes ( 0 sectors) missing/wasted

    ---------- Partition Table Info Disk 1 ----------

              14,589 Cylinders
                 255 Tracks/Cylinder
                  63 Sectors/Track
                 512 Bytes/Sector
                  12 MediaType
         234,372,285 Sectors (total)
     119,998,609,920 Bytes (total)
         117,186,143 KB
             114,440 MB
               111.8 GB

                   0 StartingOffset
     120,000,000,000 PartitionLength
                   0 HiddenSectors
                   0 PartitionNumber
                   0 PartitionType
                   0 BootIndicator
                   0 RecognizedPartition
                   0 RewritePartition

                 MBR PartitionStyle
                   4 PartitionCount
            bdda2981 Signature

            Starting Partition Hidden Total Partition
    Partition Boot Recognized Rewrite
      Offset (bytes) Length (bytes) Sectors Sectors Number
    Type (HEX) Indicator Partition Partition

              32,256 119,990,352,384 63 234,356,157 0
    0x07 0 1 0
                   0 0 0 0 1
    0x00 0 0 0
                   0 0 0 0 2
    0x00 0 0 0
                   0 0 0 0 3
    0x00 0 0 0

     119,998,609,920 Bytes (234372285 sectors) Geometric size
     120,000,000,000 Bytes (234375000 sectors) True size (measured)
     120,000,000,000 Bytes (234375000 sectors) Reported size (Partition0)
                   0 Bytes ( 0 sectors) missing/wasted

    ---------- Partition Table Info Disk 2 ----------

              14,946 Cylinders
                 255 Tracks/Cylinder
                  63 Sectors/Track
                 512 Bytes/Sector
                  12 MediaType
         240,107,490 Sectors (total)
     122,935,034,880 Bytes (total)
         120,053,745 KB
             117,240 MB
               114.5 GB

                   0 StartingOffset
     122,942,324,736 PartitionLength
                   0 HiddenSectors
                   0 PartitionNumber
                   0 PartitionType
                   0 BootIndicator
                   0 RecognizedPartition
                   0 RewritePartition

                 MBR PartitionStyle
                   4 PartitionCount
            e4dae4da Signature

            Starting Partition Hidden Total Partition
    Partition Boot Recognized Rewrite
      Offset (bytes) Length (bytes) Sectors Sectors Number
    Type (HEX) Indicator Partition Partition

              32,256 122,935,002,624 63 240,107,427 0
    0x07 0 1 0
                   0 0 0 0 1
    0x00 0 0 0
                   0 0 0 0 2
    0x00 0 0 0
                   0 0 0 0 3
    0x00 0 0 0

     122,935,034,880 Bytes (240107490 sectors) Geometric size
     122,942,324,736 Bytes (240121728 sectors) True size (measured)
     122,942,324,736 Bytes (240121728 sectors) Reported size (Partition0)
                   0 Bytes ( 0 sectors) missing/wasted

    ---------- Partition Table Info Disk 3 ----------

              19,457 Cylinders
                 255 Tracks/Cylinder
                  63 Sectors/Track
                 512 Bytes/Sector
                  12 MediaType
         312,576,705 Sectors (total)
     160,039,272,960 Bytes (total)
         156,288,353 KB
             152,625 MB
               149.0 GB

                   0 StartingOffset
     160,041,885,696 PartitionLength
                   0 HiddenSectors
                   0 PartitionNumber
                   0 PartitionType
                   0 BootIndicator
                   0 RecognizedPartition
                   0 RewritePartition

                 MBR PartitionStyle
                   4 PartitionCount
            6aacc79b Signature

            Starting Partition Hidden Total Partition
    Partition Boot Recognized Rewrite
      Offset (bytes) Length (bytes) Sectors Sectors Number
    Type (HEX) Indicator Partition Partition

              32,256 160,039,240,704 63 312,576,642 0
    0x07 0 1 0
                   0 0 0 0 1
    0x00 0 0 0
                   0 0 0 0 2
    0x00 0 0 0
                   0 0 0 0 3
    0x00 0 0 0

     160,039,272,960 Bytes (312576705 sectors) Geometric size
     160,041,885,696 Bytes (312581808 sectors) True size (measured)
     160,041,885,696 Bytes (312581808 sectors) Reported size (Partition0)
                   0 Bytes ( 0 sectors) missing/wasted

    ---------- DMIO Kernel List ----------

    Basic-info: version=21 maxspecio=512 maxio=512 maxkio=2048
    Ktrans-state: dg=0.0 pendtid=0.0 state=UNKNOWN
    #
    # Kmem-regions:
    #
    #
    # Disks: (cnt: 0)
    #
    #
    # Devices: (cnt: 0)
    #
    #
    # Groups: (cnt: 1)
    #
    Group NULLDG: iid=0.0 id=
      diskset=00000000-0000-0000-0000-000000000000
      configtid=0.0 logsize=0
      kflag=()
      vflag=(created|notempdb|noautoreimport|secondary)
    # Group-Objects: (cnt: 0)
    # End-group: NULLDG

    ---------- LDM Disk Header Harddisk0 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Header Harddisk1 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Header Harddisk2 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Header Harddisk3 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Config Harddisk0 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Config Harddisk1 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Config Harddisk2 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk Config Harddisk3 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk KLOG Harddisk0 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk KLOG Harddisk1 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk KLOG Harddisk2 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- LDM Disk KLOG Harddisk3 ----------

    ERROR: scan operation failed:
            A format error was found in the private region of the disk

    ---------- DMAdmin Simple Query ----------

    ---------- DMAdmin Verbose Query ----------


  • Next message: Ross: "No drivers"

    Relevant Pages

    • XP Home HD Bkup/Rest?
      ... This is a laptop. ... this is the bad sectors & over-rode it. ... tape drives & is nebulous or confusing as to whether it will write to ... how to boot & restore the result to a new blank HD or partition ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Poor raid 1 performance?
      ... >> Or that the stripe size is lower than available free cache on the ... >> RAID controller ... Consider a single I/O command to read a number of sectors, ... The drives will return the sectors, in order, _at the same ...
      (comp.sys.ibm.pc.hardware.storage)
    • Re: File Encryption : how I tricked myself
      ... Sounds more like you don't know the difference between a logical and physical partition image. ... Acronis TrueImage Home reads through the file system so what it saves are logical images, plus TI Home does *not* support VSS so there are problems saving inuse or locked files. ... It had the feature that it could read through recognized file systems in that partition to see which sectors were not allocated and wouldn't bother to include those in the image file. ... Norton Ghost used to default to saving logical images unless you specified a switch to make it save physical images. ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Event ID 11 - please help
      ... a ton of drives. ... > two more SATA WD 120 GB drives connected to the Promise controller ... > Offset Length Sectors ... > Type Indicator Partition Partition ...
      (microsoft.public.windowsxp.hardware)
    • Re: How to play an old floppy disk.
      ... for all HD drives, if any. ... reference for the PC AT states that the High Capacity Diskette Drive ... side, 15 sectors per track. ... It is possible you have an issue with the controller rather than the ...
      (comp.sys.ibm.pc.hardware.storage)