Re: Windows Disk Drive Device Names

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

That KB article was exactly what I was looking for. Thank you. Searching
the KB for "device names", "Physical device event message" and many other
keyword attempts wasn't producing results.

I did an Advanced Search for: Device\Harddisk1
@
http://support.microsoft.com/search/?adv=1

With: The exact phrase entered selected.

Which resulted in...
http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&1033comm=1&spid=global&query=Device%5CHarddisk1&pwt=false&title=false&kt=PHRASE&mdt=0&res=20&ast=1&ast=2&ast=3&ast=4&mode=a&adv=1

How to Distinguish a Physical Disk Device from an Event Message was the
fifth one down and looked the most promising.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:D2D76C5D-E5D4-4558-97BF-EBDCB9BDA60A@xxxxxxxxxxxxx,
abeach <abeach@xxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
That KB article was exactly what I was looking for. Thank you. Searching
the KB for "device names", "Physical device event message" and many other
keyword attempts wasn't producing results.

So according to http://support.microsoft.com/kb/159865

SCSI and atapi device are listed under
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\

Device D would be the 4th SCSI device registy entry, identifed by
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 2\Logical Unit Id 0]

To complete the information in this thread, the computer has a motherboard
integrated Adaptec 39320 RAID controller and a IDE DVDROM drive. There
are 3 drives attached to the 39320 controller, 1 drive is the main
windows boot drive, SCSI ID 0. The other 2 drives, SCSI IDS 2 and 3 are
configured as a striped volume by the SCSI controller. Disk Managment
identifes the striped volume as a single disk, Disk 1.

Here's my HKLM\Hardware\Devicemap\SCSI\ keys.

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0]
"DMAEnabled"=dword:00000001
"Driver"="atapi"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus
0\Initiator Id 255]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target
Id 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target
Id 0\Logical Unit Id 0]
"Identifier"="HL-DT-ST DVD+-RW GWA4164B"
"Type"="CdRomPeripheral"
"DeviceName"="CdRom0"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1]
"Interrupt"=dword:00000018
"IOAddress"=dword:0000d800
"Driver"="a320raid"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus
0\Initiator Id 7]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 0]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 0\Logical Unit Id 0]
"Identifier"="FUJITSU MAS3367NP 0104"
"Type"="DiskPeripheral"

"InquiryData"=hex:00,00,03,12,5b,00,01,3a,46,55,4a,49,54,53,55,20,4d,41,53,3
3,\
33,36,37,4e,50,20,20,20,20,20,20,20,30,31,30,34
"SerialNumber"="A0G0P5700ARU"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 15]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 15\Logical Unit Id 0]
"Identifier"="ADAPTEC HostRAID SCSI 1.0 "
"Type"="OtherPeripheral"

"InquiryData"=hex:03,00,00,00,1f,00,00,00,41,44,41,50,54,45,43,20,48,6f,73,7
4,\
52,41,49,44,20,53,43,53,49,20,20,20,31,2e,30,20

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 2]

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target
Id 2\Logical Unit Id 0]
"Identifier"="ADAPTEC RAID 0 1.0 "
"Type"="DiskPeripheral"

"InquiryData"=hex:00,00,00,00,1f,00,00,32,41,44,41,50,54,45,43,20,52,41,49,4
4,\
20,30,20,20,20,20,20,20,20,20,20,20,31,2e,30,20


"Pavel A." wrote:

"abeach" wrote:
I having been searching for many months for documentation about how to
decipher Windows hard disk device names.

For example, in the System Event log would be a message similar to the
following:
"The device, \Device\Harddisk1\D, is not ready for access yet".

Normally there should not be names like \Device\Harddisk1\D.
Maybe this is actually \Device\Harddisk1\DR0 (or DR1 etc?),
or \Device\Harddisk1\DP(1) ?


Is there any documents that explain these device names?

Unfortunately these event log messages contain
low level disk names that look cryptic to users.

If it were \Device\Harddisk1\DR1 this means partition #1 on physical
disk 1.

Then you can open Disk manager and look what driver letter(s)
mapped to this partition.
But this definitely is not a CD drive; CD-ROM usually has name
like \Device\Crdom0

Regards,
--PA

.

Relevant Pages

  • Re: Exercising ATA disks in hopes of revealing errors
    ... <ACPI PCI bus> on pcib0 ... <Parallel port bus> on ppc0 ... Disk ad0 attached to gs0. ... GEOM_STRIPE: Device gs0 activated. ...
    (freebsd-questions)
  • Re: questions about TZ88N-VA
    ... > the DLT system mentioned above from a) a disk on the same SCSI bus, ... will find that the information given there says the "TZ88 is ... a few SCSI-1 and some SCSI-2 drives will be hard pressed to sustain a ... are on the same bus it may be the bus bandwith that is the limit. ...
    (comp.os.vms)
  • Re: questions about TZ88N-VA
    ... > the DLT system mentioned above from a) a disk on the same SCSI bus, ... will find that the information given there says the "TZ88 is ... a few SCSI-1 and some SCSI-2 drives will be hard pressed to sustain a ... are on the same bus it may be the bus bandwith that is the limit. ...
    (comp.sys.dec)
  • Re: (S)ATA performance in FBSD 6.2/7.0
    ... I never got beyond 33 MB/s transfer rate although bonni/bonni++ told me both drives are capable doing much more. ... Two Hitachi T7K250 250 GB/SATA II drives build up a RAID 0, and additionally there is a SAMSUNG Spinpoitn SP2004C attached to the controller. ... For example, if you have two devices on the same bus, then each byte of data copied has to pass over the bus twice, which may run into performance limits on the bus where moving the data over the bus once won't. ... disk performance varies enourmously by location where the I/O is taking place on the disk. ...
    (freebsd-questions)
  • Re: (S)ATA performance in FBSD 6.2/7.0
    ... I never got beyond 33 MB/s transfer rate although bonni/bonni++ told me both drives are capable doing much more. ... Two Hitachi T7K250 250 GB/SATA II drives build up a RAID 0, and additionally there is a SAMSUNG Spinpoitn SP2004C attached to the controller. ... For example, if you have two devices on the same bus, then each byte of data copied has to pass over the bus twice, which may run into performance limits on the bus where moving the data over the bus once won't. ... disk performance varies enourmously by location where the I/O is taking place on the disk. ...
    (freebsd-performance)