df -h
fdisk -l hdparm -i device (probably /dev/hda)
Using the 'sudo hdparm -i /sda' command I was able to get the following data:
/dev/sda: Model=WDC, FwRev=01.04A01, SerialNo=WD-WXEY07X26552 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50 BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=312581808 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7 * signifies the current active mode
However, this didn't work for the new Fantom Drives. I get the following error instead:
/dev/sdb: HDIO_DRIVE_CMD(identify) failed: Invalid exchange HDIO_GET_IDENTITY failed: Invalid argument
I would guess that this has something to do with it being a USB drive.
Will this be fixed by USB3?
How did linux know if was a Fantom Drive?
USB Info
Using 'lsusb --verbose' I still don't see anything that would enable to ID drive.
No comments:
Post a Comment