Sluggish USB hard drives
in [General Linux]
|
From: J G Miller on 12 Feb 2010 15:39 On Fri, 12 Feb 2010 20:00:51 +0000, Harold Johanssen wrote: > I thought that hdparm was meant for IDE drives, not USB ones. It can be used with both IDE and SATA drives at the man page indicates. > Anyway, I tried the following: > > # hdparm -C /dev/sde Why are you using a parameter for an IDE drive? Are you sure that the drive is IDE rather than SATA. I suggest you try hdparm -I /dev/sde to get information about the drive (whether it is IDE or SATA) and what parameter (including spin up /spin down) can be set or enabled or disabled. > I am a bit reluctant to tinker with my USB drive using hdparm any > further until I understand it better. And in order to understand it better, are you reading the manual page?
From: Harold Johanssen on 12 Feb 2010 16:58 On Fri, 12 Feb 2010 21:39:18 +0100, J G Miller wrote: > On Fri, 12 Feb 2010 20:00:51 +0000, Harold Johanssen wrote: > >> I thought that hdparm was meant for IDE drives, not USB ones. > > It can be used with both IDE and SATA drives at the man page indicates. > >> Anyway, I tried the following: >> >> # hdparm -C /dev/sde > > Why are you using a parameter for an IDE drive? Are you sure that the > drive is IDE rather than SATA. Actually, I have no clue. The only thing I know is that it is an external disk that gets connected to my PC via a USB port. hdparm just does not seem to be able to do anything much right with it, hence my reluctance. > I suggest you try > > hdparm -I /dev/sde > > to get information about the drive (whether it is IDE or SATA) and what > parameter (including spin up /spin down) can be set or enabled or > disabled. This is what I get: /dev/sde: SG_IO: bad/missing ATA_16 sense data:: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing ATA_16 sense data:: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(identify) failed: Input/output error You see what I mean?
From: J G Miller on 12 Feb 2010 17:16 On Fri, 12 Feb 2010 21:58:42 +0000, Harold Johanssen wrote: > Actually, I have no clue. You should be able to get a clue from the dmesg output when you connect your drive to the USB cable. For example -- [ 9.995550] usb-storage: device scan complete [ 10.024553] scsi 6:0:0:0: Direct-Access WD 10EAVS External 1.75 PQ: 0 ANSI: 4 [ 10.025467] sd 6:0:0:0: Attached scsi generic sg5 type 0 You can then do a Web Search on any model number which is reported to try and get more information about the drive. > This is what I get: Okay, fair enough. That does seem to indicate that your drive does not have the capablities needed for hdparm to work. > /dev/sde: > SG_IO: bad/missing ATA_16 sense data:: I would be a little bit worried about that line. Does your drive have SMART capabilities? Does smartctl -H /dev/sde give any meaningful information?
From: AZ Nomad on 12 Feb 2010 18:41 On Fri, 12 Feb 2010 21:58:42 +0000 (UTC), Harold Johanssen <noemail(a)please.net> wrote: >On Fri, 12 Feb 2010 21:39:18 +0100, J G Miller wrote: >> On Fri, 12 Feb 2010 20:00:51 +0000, Harold Johanssen wrote: >> >>> I thought that hdparm was meant for IDE drives, not USB ones. >> >> It can be used with both IDE and SATA drives at the man page indicates. >> >>> Anyway, I tried the following: >>> >>> # hdparm -C /dev/sde >> >> Why are you using a parameter for an IDE drive? Are you sure that the >> drive is IDE rather than SATA. > Actually, I have no clue. The only thing I know is that it is an >external disk that gets connected to my PC via a USB port. hdparm just >does not seem to be able to do anything much right with it, hence my >reluctance. hdparm is for internal IDE and SATA drives. An IDE or SATA drive connected via USB operates through a completely different interface and driver.
From: J G Miller on 12 Feb 2010 19:21
On Fri, 12 Feb 2010 17:41:24 -0600, AZ Nomad wrote: > hdparm is for internal IDE and SATA drives. An IDE or SATA drive > connected via USB operates through a completely different interface and > driver. If that is the case, why does hdparm return the following for my USB drive? hdparm -I /dev/sdd /dev/sdd: ATA device, with non-removable media Model Number: WDC WD10EAVS-00M4B0 Serial Number: WD-WCAV50793611 Firmware Revision: 01.00A01 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 1953525168 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 953869 MBytes device size with M = 1000*1000: 1000204 MBytes (1000 GB) cache/buffer size = 8192 KBytes Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5 udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * NCQ priority information DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 220min for SECURITY ERASE UNIT. 220min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee25873a1eb NAA : 5 IEEE OUI : 0014ee Unique ID : 25873a1eb Checksum: correct |