none
How to find out which hdd is \Device\Harddisk#\DR# ?

    Question

  • I have few similar (same model) usb external hdds, one of them apparently isn't stable and I see that in event viewer,

    How can I found how which hdd is it?

    Many thanks!

    Wednesday, March 14, 2012 6:23 PM

Answers

All replies

  • See that: http://support.microsoft.com/kb/159865



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by Matthias S. _ Monday, August 25, 2014 7:53 AM
    • Unproposed as answer by Matthias S. _ Monday, August 25, 2014 8:01 AM
    Wednesday, March 14, 2012 6:33 PM
  • Hello,


    In Disk Management console, the disks are labeled as Disk 0, Disk 1 and Disk 2. If you want to determine which physical USB hard disk is the one in question, you will have to unplug all USB disks and test one by one.


    Thanks
    ZHANG

    Thursday, March 15, 2012 5:44 AM
    Moderator
  • That document is for Server 2000, last updated in 2007.  Does anyone know if it applies to newer versions?  If so, would be nice if MS would update.

    Article ID: 159865 - Last Review: February 26, 2007 - Revision: 3.5

    APPLIES TO
    • Microsoft Windows 2000 Server
    • Microsoft Windows 2000 Advanced Server
    • Microsoft Windows 2000 Professional Edition
    • Microsoft Windows 2000 Datacenter Server
    • Microsoft Windows NT Advanced Server 3.1
    • Microsoft Windows NT Server 3.5
    • Microsoft Windows NT Server 3.51
    • Microsoft Windows NT Server 4.0 Standard Edition
    • Microsoft Windows NT Workstation 3.1
    • Microsoft Windows NT Workstation 3.5
    • Microsoft Windows NT Workstation 3.51
    • Microsoft Windows NT Workstation 4.0 Developer Edition
    • Microsoft Windows NT Advanced Server 3.1
    Keywords:              
    KB159865
    Wednesday, September 12, 2012 3:04 PM
  • That would be nice, yes. A cannot seem to find the same for Windows 7, and I cannot find the "drive mapping" in my registry according to the link for 2000 Server.

    I not sure if I should start a new thread, but it would be with the same title - and it's not that old :)

    I have the same problems, but have a rather heavy disk setup.

    I get messages for different disks (so it seems like a controller malfunction?).
    All of these is from mid-october until today november 1st.

    • Level: Error, Source: Disk:
    • The driver detected a controller error on \Device\Harddisk4\DR12.
    • The driver detected a controller error on \Device\Harddisk5\DR10.
    • The driver detected a controller error on \Device\Harddisk4\DR11.
    • The driver detected a controller error on \Device\Harddisk4\DR9.
    • The driver detected a controller error on \Device\Harddisk5\DR5.
    • The device, \Device\Harddisk4\DR4, is not ready for access yet.
    • The driver detected a controller error on \Device\Ide\IdePort5.
    • The driver detected a controller error on \Device\Harddisk5\DR5.
    • The driver detected a controller error on \Device\Ide\IdePort1.
    • Level: Warning, Source: Disk:
    • An error was detected on device \Device\Harddisk4\DR4 during a paging operation.
    • The system failed to flush data to the transaction log. Corruption may occur.

    The DR# does not match anything. I may have a lot of disks, but not 12!! :)

    I have these Disks in Disk Management:

    • Disk 0: WDC WD2500JD-00HBB0 ATA Device, 232 GB, 1 partition (E:)
    • Disk 1: ST380011A ATA Device, 74 GB, 2 partitions (System Reserved, C:)
    • Disk 2: WDC WD5000AAKS-65YGA0 ATA Device, 465 GB, 1 partition
    • Disk 3: SAMSUNG HD103SJ ATA Device, 931 GB, 1 partition
    • Disk 4: ST3200822AS ATA Device, 186 GB, 1 partition
    • Disk 5: Seagate FreeAgent Go USB Device, 465 GB, 1 partition
    • CD-ROM 0: LITE-ON DVDRW SHM-165P6S ATA Device

    In the Properties of the disk (in Disk Manager) in the Details tab, I choose the property Physical Device Object name and get something that can look like the thing I/we need. And in the General tab, there is the Location property.

    • Disk 0: Location 0 (Channel 0, Target 0, Lun 0), \Device\Ide\IdeDeviceP4T0L0-4
    • Disk 1: Location 0 (Channel 1, Target 0, Lun 0), \Device\Ide\IdeDeviceP1T0L0-1
    • Disk 2: Location 0 (Channel 1, Target 0, Lun 0), \Device\Ide\IdeDeviceP3T0L0-3
    • Disk 3: Location 0 (Channel 0, Target 0, Lun 0), \Device\Ide\IdeDeviceP2T0L0-2
    • Disk 4: Location 0 (Channel 1, Target 0, Lun 0), \Device\Ide\IdeDeviceP5T0L0-6
    • Disk 5: on USB Mass Storage Device, \Device\0000006b
    • CD-ROM 0: Location 1 (Channel 1, Target 1, Lun 0), \Device\Ide\IdeDeviceP1T1L0-7

    But it's nothing like \Device\Harddisk4\DR12? It seems like the last part after '-' could be the disk#+1, except that the USB-drive has been put as number 5 (4+1), which should be the ST3200822AS disk.

    I dont get it... Can someone help?

    I have this pc:

    Mobo: Asus P5KC 
    CPU: Core2 Duo E8400 3GHz
    Socket LGA775 45nm
    6MB L2 Cache
    1333MHz FSB, 45nm
    64 bit architecture
    RAM: Corsair 2x 2GB DDR2 800MHz 5-5-5-18 1,80V CM2X2048-6400C5DHX ver4.1
    Graphics
    Zotac GeForce 8800GT Amp! Edition 512MB DDR3 HDCP OC SPDIF D/D/TV

    Best regards, Svend

    Thursday, November 01, 2012 7:43 AM
  • Oh, I think I found the error and the disk.

    One of my disks - Disk 4 in the above - has disappeared from Disk Management and the drive has disappeared from Computer.

    It comes back after reboot, but after some time, or heavy usage, it hangs the computer for a minute, and then disappears.

    I guess it's bye bye for that disk...

    But it still doesn't resolve... Why did I get errors from a variety of disks, and what disks are they?

    Thursday, November 01, 2012 10:38 PM
  • Just adding to the thread in case it helps any one.

    I have a storage pool drive that tells me it is healthy and fine. However, the system was hanging up.

    I found Event ID: 153, Source: Disk - The IO operation at logical block address 35575ee8 for Disk 3 was retried.

    Details show \Device\Harddisk3\DR3

    I have a simple virtual disk that I am using for backup. The system has 4 drives. A boot disk and 3 drives to create the virtual disk in the storage pool. So the disks are 0 through 3. I am going to replace disk 3 and hope that this fixes the error. It would be nice if there error in the event log talked to File and Storage Services because it thinks all is well. The virtual disk is healthy and when I check the properties of each disk they all report healthy. It would also be nice if \Device\Harddisk3\DR3 actually was referenced in the File and Storage Services system. Or if the event log referenced the Name or something from the Storage pool information. Not a great start to storage services for me, I am worried when I put this into production and I really need to know which drive is bad.


    Victor Camacho Your-IT-Group

    Friday, November 09, 2012 10:11 PM
  • More I read threads about this topic, and less I find an answer. I always have customers with these kinds of errors on the registry event and what I just need to understand is which disk has problems and find a solution.

    -----

    http://support.microsoft.com/kb/159865

    That link is more than 10 years old, why today we still have to see that as main technical answer (on other threads too) when a question like this is posted, especially when the poster doesn't specify the OS? if in new OSs things are not changed from that post, so why 90% of times I even can't find these registry keys?

    -----

    "... DR is simply an abbreviation for Drive and should match the Harddisk# entry in the path before it..." (Microsoft Enterprise support, from another thread)

    Just now I have a harddisk2 / DR4 error in front of me. And take a look at mr. Svendko post

    -----

    In the end... can we have a simple answer with the rules applied on how drives are numbered, in every part (harddisk xxx / DR yyy etc.), every relationship with sata,scsi, ide, usb, every EVERY rule, so that we can identify the problem? a simple link to some technical page is good, since I still have not found it. And if it's not possible for who knows which reason, is it possible to have an answer like "do not care about these kinds of errors in event log, they really don't mean you have a problem on one of your harddisks, they are random junk written to scare people. And if tomorrow one of hd fails,  believe me it's not because of that" ?

    • Proposed as answer by KarlHenselin Thursday, July 11, 2013 2:14 PM
    Thursday, March 28, 2013 11:02 AM
  • I have 1 memory stick which does not respond. Please advise.
    Saturday, August 17, 2013 6:20 PM
  • I guess we can't have a straightforward answer.  All I find is aforementioned ten year old article referencing Windows NT.
    Thursday, June 12, 2014 11:05 PM
  • The number in the DRx part at the end really does not have any special meaning. It is just a sequence number which starts at 0 and increases ever since. That means it matches the preceding HarddiskX part after boot, but if you plug or unplug some drives, the number keeps increasing and naturally gets out of sync.

    As for pinpointing the exact disk from a path like \Device\Harddisk1\DR3, this works for me:

    1. Download WinObj from Sysinternals
    2. Run it as administrator
    3. Go to \Device\HarddiskX
    4. You will see individual PartitionY symbolic links (to \Device\HarddiskVolumeZ), note these down
    5. Go to \GLOBAL??, sort by the 3rd column "SymLink"
    6. Find the \Device\HarddiskVolumeZ value you noted down in the 3rd column
    7. You will see various names of that volume in the first column, including HarddiskXPartitionY, Volume{GUID} and (what's probably most useful for most people) the DOS-style letter like C:
    • Proposed as answer by QuiqueSein Tuesday, March 10, 2015 3:28 PM
    Tuesday, March 03, 2015 1:54 AM
  • Finally a simple and clear method to identify disks, thanks!!!
    Tuesday, March 10, 2015 3:31 PM
  • Thanks, really a simple and clear method to identify disks

    That's what I looked for.

    Saturday, October 17, 2015 12:46 AM
  • Yes, that old KB http://support.microsoft.com/kb/159865 still applies to current versions.  Not sure about Windows 10 / 2016 but I expect the principle is the same.
    Friday, November 20, 2015 2:50 AM
  • Forgive me for being dense, but I see everything EXCEPT the letter C:
    Thursday, January 07, 2016 5:23 PM
  • For me I had a disk in a MSFT Storage Pool, and none of the graphic tools did a great job of identifying which disk was what. Running it in Core anyways, so it's nice to be able to run this remotely if needed.

    Get-PhysicalDisk | select deviceid,friendlyname,serialnumber,size | sort -Property deviceid
    Monday, May 08, 2017 2:00 AM
  • you can pipe Get-PhysicalDisk to gm to see all the good stuff you can grab. throw physicallocation in your selection and it will tell you exactly which port it's plugged into on your board/raid controller.

    Get-PhysicalDisk | select deviceid,friendlyname,serialnumber,size,physicallocation | sort -Property deviceid
    Monday, May 08, 2017 2:07 AM