Обнаружена ошибка на устройстве device harddisk2 dr2

Posted by derektom 2013-02-19T14:39:22Z

• click start, right click computer and select manage. Expand storage on the left and select disk management. That should tell you.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Thanks for your reply. That’s the first place I looked but I’m unsure how to correlate Harddisk2\DR2 to any of those drives. Is «DR2» = «Disk 2»? Attached is a screenshot for reference. Thanks again.

  attach_file
  Attachment
  
  drives.jpg
  304 KB
  
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Rockn

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  mace

  Does diskpart give you more detailed info?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Do you have any Management software installed for the RAID?  That would have it’s own logging and hopefully diagnostics too.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

• 

  Thanks for the feedback, Rockn, LarryG., and Fishsauce.

  diskpart didn’t give me any helpful info beyond what the Disk Management console had already provided.

  I have HP RAID management software but it didn’t really help either since I have so many other hard drives (USB, iSCSI) that are not on the internal RAID.

  Following a link off of the link Fishsauce provided (below), it does seem to validate that the disk in question is «Disk 2» that in Disk Management shows is an external 2TB USB Seagate GoFlex drive.

  http://support.microsoft.com/kb/159865 Opens a new window

  NOTE: Disk Management is enhanced in Windows 2000 and later operating systems. You can use Disk Management to view this information without using Registry Editor. To view where a particular hard disk is located in your system, use the following procedure:

  1. Start Disk Management console (diskmgmt.msc).

  2. View the graphical view of your disks. Right-click the gray portion of the basic or dynamic disk whose disk number matches the "Harddisk#" in the error message.

  3. Click Properties. The Properties will contain "Device Type" information that will tell you if the disk is IDE or SCSI, and it will also display the "Hardware Vendor" name of the physical device and the "Adapter Name" it is attached to.

  I’ll swap out that drive and see if the error goes away.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Any update on this? I am curios as I am having the same event log error generated.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Ha!.. Sorry for not following up on this…

  YES, I swapped out the «Disk 2» drive (an external Seagate GoFlex) as indicated in the Disk Management console and the errors went away.

  So the disk numbers shown in the Disk Management console (Disk 1, Disk 2, Disk 3, etc) correspond to the \Device\Harddisk# in those Event Log errors. For instance, in the following error, the matching disk to look for in Disk Management is «Disk 5».

  The driver detected a controller error on \Device\Harddisk5\DR6

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Note that I made a correction in the above post.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• I hadn’t realized that your post was from May, but here is some info in case other run into this:

  I would take a look at «WinObj» from the Sysinternals, it’s a free download:

  http:/ Opens a new window/technet.microsoft.com/en-us/sysinternals/bb896657.aspx

  Fire that up and expand the «Device» tree node. Under there you will have several nodes for «Harddisk0» … that should help.

  I was under the impression that «DR» stands for «disk removable», but I honestly wasn’t able to find any references to that so I could be wrong. But in my experience this error is almost always logged for USB drives (and we see a lot of events since we do event log monitoring).

  One thing to note however, is that «DR» is being incremented as you insert new (e.g. USB) drives. So, if you insert a memory stick for the first time, it could be logged as

  Harddisk1\DR1

  but when you eject it and put it back in, it will be

  Harddisk1\DR2

  So you definitely can’t go by the DR unless you use Winobj. The «Harddisk5» should refer to «Disk 5» in Disk Management however.

  Hope this helps.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hi Ingmar, much thanks for that additional info. Good stuff!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  As far as I remember, DR represents the Raw physical drive and DP represents Disk Partition.

  Every disk will have a device controlling the Raw Physical drive (DR identifier) and a device per each partition, controlling the partition (DP instance)

  For example: Harddisk1\DR2 and Harddisk1\DP3

  Unlike in the case of Harddisk#, the numbers after DR and DP are not counters. These are just unique random numbers.

  I assume that the DR number is somehow linked to drive signatures. Same drive inserted multiple times into the same port will have same DR. Another drive inserted to the same port will have a different DR. But this is just an assumption. Maybe DR changes with each insertion/removal even if the drive is the same. I haven’t tried this.

  I use DISKPART:

  CMD >

  DISKPART

  list disk

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I just read all of the answers, even trying WinObj, but I still do not know what physical drive is associated with the error message in the event viewer. 

  Device\Harddisk1

  Why doesn’t MS have a clear answer for this?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Slacka…when you are in Disk Management and you are looking at the the graphical view of the disks, right click on the first drive and select Properties.  From there select the Volumes tab and next the word Disk, which should be the first line item, you will see which actual disk that is.  Let me know if this helps.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I am having this occur regularly on six disk (3 out of 4 disks in 2 different mediasonic hf2-su3s2 proboxs) I am using StableBit Scanner to monitor the disk and it isn’t reporting any issues. The computer is running Windows Server 2012 R2 Essentials and the two externals enclosures are connected by USB 3.0 (which has been its own headache with the disks constantly dropping out all the time but I finally fixed that issue with a Anker USB 3.0 hub (no clue why that fixed it but glad that it did) It usually occurs six instances in a row disk 6 disk 7 disk 8 disk 8 disk 7 disk 6 and then same thing with 10, 11, 12, 12, 11, 10. Could this be an issue with the enclosures and not the drives maybe a problem with the port multiplier and that is why it is only 3 out of the four disks. Neither of the first disk in the enclosure get the error (disk 5, or 9)

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Well what about..

  An error was detected on device \Device\Harddisk1\DR25 

  When I go to Disk management..all I have is «Disk 0» 

  So does harddisk1 = disk 0 

  and harddisk2 = disk 1

  ??????

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  josephboombox — do you have a DVD/CD drive? If you have only one drive and it’s showing as Disk 0 in Disk Management, but you also have a CD-ROM 0 next to it, the CD-ROM may be detected as Disk 1. That is my experience with Windows and this message. For example, I have the following configuration in Disk Management: Disk 0 (RAID — C), Disk 1 (RAID- D), Disk 2 (USB — E), CD-ROM 0 (CD-ROM): , however, in DISKPART is shows this: Volume 0 — DVD-ROM, Volume 1 — C:, Volume 2 — D, Volume 3 — E. In other words, Windows moved DVD-ROM in front of the other drives and shifted the numbers by 1. Hope that makes sense. And the numbers that are shown in DISKPART seem to be corresponding to the ones in the error message. Thank you Microsoft for not making our job easy.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hola, estoy leyendolos y a mi me aparece este error No hay disco en la unidad. Inserte un disco en la unidad /device/Harddisk5/DRS, ALGUNO DE UDS SABRIA DARME UNA ORIENTACION A KE SE DEBE Y COMO RESOLVERLO,? PORK YO NI IDEA !!!!!!  MUCHAS GRACIAS.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  God damn it I am fed up with this!  I have had this question myself for YEARS! Here is another question Why the god damn bloody hell does MS make this information so F’ing hard to correlate to a physical drive?

  Why not have an app where you can simply see each \device id that corresponds to each bloody disk!!!!!!  Disk 1 -> \device\harddisk#\DR# or something?

  It’s crap like this that makes me truly hate windows!  It’s like they go out of their way to make stuff totally incomprehensible!  What are they trying to force everyone to take the MCSE course to learn the SECRET HANDSHAKE?

  I mean what if my car speedometer gave me my speed in furlongs per fortnight then converted that to a secret guid so my speedometer reads your speed is …  {000f-2343-aff1-0034……}?  

  Or better yet replace everything on my dashboard with a single red light and when it comes on SOMETHING is broke!  Don’t give me a clue or way to find out what is broke just tell me something is broke or even worse give me this tantalizing string that looks like it can be simply decoded to point to a specific thing when in fact it cannot be and there might be one guy in the universe that knows how to decode it!

  WHY ENCODE IT IN THE FIRST PLACE????  

  I mean seriously google «what drive is \device\harddisk1\DR1» and you will get a bazillion responses just like this one with 400 responses — none of which answer the question!  It’s a simple god damn question and the answer should be like one line.  Run xxx and it will translate every physical drive you can see to a \device id.  Or run xxx and enter the \device string and it will spit out the physical drive in a human readable format!  

  No instead we get things like look at the hex dump from the event message and take the entry at 0001 03 now convert that number and divide it by your weight in grams then if it’s a Monday or any month with an A in the name mulriply that by your mother birth date converted to gregian date converted to the integer number of days since the epoc raised to the log of 3……ARGH!!!!!! 

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  Thank you rm9 for your eloquent and educated reply.

  The most prominent omission from your valuable contribution is the Microsoft troubleshooter. I would be grateful to know if ANYONE has ever had any joy from running the Microsoft Troubleshooter or from the «Search online for a solution to this problem» option?

  I’d really also be interested to know if Microsoft ever actually does anything with the billions of error reports that are automatically sent to them.

  Otherwise I can only second and applaud your comments….

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  here is the problem with the Microsoft paradigm. they have a group of really really bright folks working on part of this whole disk drive management issue. and, they also have another group of really really bright folks working on another aspect of the disk drive management issue.

  here is the kicker: neither one of these groups communicates with the other. so we have this elaborate schema describing the disk structures, and we also have a second similarly elaborate schema describing the SAME structure. however, there is no common description and there is no map or description of the correlation between these two schema.

  my perception is that this has been a long term failure in the management of the Microsoft development process, or to phrase it another way, nobody has a clue WTF is going on overall. nobody grasps the big picture concept. maintenance efforts suffer while troops in the field try to decipher this hodgepodge of disparately presented information about the same subject. recollect the elephant? very much like a tree, or wait, like a snake… no it’s a wall!

  luls. yeah, i’m here because i have the same problem. just WHICH darn drive is the dud?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  i had same trouble,shown device/harddisc2/dr2
  after i instaling an application.it sucks.
  i was re instaling windows,still shown.
  how to fix it?

  
  0 of 1 found this helpful
  thumb_up
  thumb_down
  

• 

  This link might help.

  http://support.microsoft.com/kb/159865 Opens a new window

  How to Distinguish a Physical Disk Device from an Event Message Opens a new window

  start button,
  right click on my computer >
  select manage
  select storage from the left tree menu
  this will list all the attached drives.
  all HDD will be number as DISK 0, DISK 1, DISK2 etc.

  from the error message ‘device/Harddisc2/DR2’ the Harddisc2 corresponds to DISK2 attached to your computer/server
  however, DR2 in the error message, i think it corresponds to the desk sector number 2 or partition number 2.

  
  1 of 2 found this helpful
  thumb_up
  thumb_down
  

• 

  mr9: I feel your pain. But I think you forgot to divide by pi. Or maybe multiply by pi. And then go have a pint.

  So far, for me, Hardisk3, or whatever number, has matched up with the graphical display of the Disk # in Disk Management. And it’s usually been the external USB backup disks. But one time it was one of the 4 disks in a RAID 10. Boy was that fun!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I managed to find the device using WinObj as guided in http://wp.me/p1KeqG-6F Opens a new window%uFEFF

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  CirruSafe is an IT service provider.

  pimiento

  I have Intel® Server System R2308SC2SHFN with embedded RAID controller. Two RAID arrays.  No removable drives.  Drive Group 0 and Drive Group 1 are RAID 5.  Intel RAID Web Console says both arrays are healthy.

  Windows Management console — Disk Management says RAID drive group 0 is Disk  0 and RAID drive group 1 is Disk 1.

  Windows Event viewer says errors are occurring on \Device\Harddisk2\DR76 and \Device\Harddisk3\DR77.

  So, at least in this case, the disk number in the logs (Harddisk2 and Harddisk3) and the disk number in Disk Management (0 and1) have nothing to do with each other.

  RAID group 0 has three partitions (System Reserved, C:, and E:) and RAID group 1 gas one partition (F:).

  So maybe each partition corresponds to a «Harddisk» number?

  Anyone have any experienewith Intel’s embedded RAID controller?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Desktop-Host wrote:

  Anyone have any experienewith Intel’s embedded RAID controller?

  Please create a new thread with your questions.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  CirruSafe is an IT service provider.

  pimiento

  Done on Windows Server

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Don’t think so.  The disks are enumerated starting at zero.  So Disk 2 is really the third disk.  Yes what you say would make sense, but when I get a message that identifies \Device\Harddisk4\DR6 when I don’t have a Disk 4 and I certainly don’t have 6 partitions.  I suspect that your answer is probably not correct.  Do I have a better one?  No.  Wish I did, because I’d really like to know which disk to swap out before it goes completely under.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I laughed so hard I think I hurt a stomach muscle now. I couldn’t agree more with rm9 and pdoff!

  
  Was this post helpful?
  thumb_up
  thumb_down