I maintain a large inventory of hard drives used in surveillance equipment. I have always used the GSmartControl interface to analyse these drives. Recently we upgraded our equipment and the new equipment uses the Toshiba MK1665GSX 160G hard drive. This drive is totally not detected using GSmartControl, no smartctl commands will work, and no smart information can be obtained from these drives.
I have looked over your website and have not found anyone else having issues with the Toshiba drives. This drive is normally connected through a JMicron usb/sata interface but nothing changes by connecting the hard drive directly. This is the output from connecting the drive through usb: Dec 13 05:48:18 Voyager kernel: [585396.728042] usb 1-4: new high speed USB device using ehci_hcd and address 13 Dec 13 05:48:19 Voyager kernel: [585396.846538] usb 1-4: New USB device found, idVendor=152d, idProduct=2336 Dec 13 05:48:19 Voyager kernel: [585396.846543] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Dec 13 05:48:19 Voyager kernel: [585396.846546] usb 1-4: Product: JM20336 SATA, USB Combo Dec 13 05:48:19 Voyager kernel: [585396.846548] usb 1-4: Manufacturer: JMicron Dec 13 05:48:19 Voyager kernel: [585396.846550] usb 1-4: SerialNumber: 2010E1888888 Dec 13 05:48:19 Voyager kernel: [585396.857314] scsi14 : usb-storage 1-4:1.0 Dec 13 05:48:20 Voyager kernel: [585397.859041] scsi 14:0:0:0: Direct-Access TOSHIBA MK1665GSX PQ: 0 ANSI: 2 CCS Dec 13 05:48:20 Voyager kernel: [585397.859307] sd 14:0:0:0: Attached scsi generic sg4 type 0 Dec 13 05:48:20 Voyager kernel: [585397.862030] sd 14:0:0:0: [sdd] 312581808 512-byte logical blocks: (160 GB/149 GiB) Dec 13 05:48:20 Voyager kernel: [585397.869900] sd 14:0:0:0: [sdd] Write Protect is off Dec 13 05:48:20 Voyager kernel: [585397.869906] sd 14:0:0:0: [sdd] Mode Sense: 00 38 00 00 Dec 13 05:48:20 Voyager kernel: [585397.869909] sd 14:0:0:0: [sdd] Assuming drive cache: write through Dec 13 05:48:20 Voyager kernel: [585397.875947] sd 14:0:0:0: [sdd] Assuming drive cache: write through Dec 13 05:48:20 Voyager kernel: [585397.875957] sdd: sdd1 Dec 13 05:48:20 Voyager kernel: [585397.911001] sd 14:0:0:0: [sdd] Assuming drive cache: write through Dec 13 05:48:20 Voyager kernel: [585397.911051] sd 14:0:0:0: [sdd] Attached SCSI disk Here is the output using smartctl -i and -all options: Voyager:/home/dave # smartctl -i /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [x86_64-unknown-linux-gnu] (openSUSE RPM) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Voyager:/home/dave # smartctl -all /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [x86_64-unknown-linux-gnu] (openSUSE RPM) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net =======> INVALID ARGUMENT TO -l: l =======> VALID ARGUMENTS ARE: error, selftest, selective, directory[,g|s], background, scttemp[sts|hist], sasphy[,reset], sataphy[,reset], gplog,N[,RANGE], smartlog,N[,RANGE], xerror[,N][,error], xselftest[,N] [,selftest] <======= Use smartctl -h to get a usage summary Voyager:/home/dave # Is this drive a known issue? How can I get smartctl working with this drive? I will be willing to try anything you might suggest to get this drive working with smartctl. Thanks, Dave ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Smartmontools-database mailing list Smartmontools-database@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/smartmontools-database
