On Wed, 12 Sep 2007, Mark Lord wrote: > Chuck Ebbert wrote: > >>> ========= > >>> sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2 > >>> ASC=0x4 ASCQ=0x2 > >>> end_request: I/O error, dev sda, sector 126693711 > >>> sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2 > >>> ASC=0x4 ASCQ=0x2 > >>> end_request: I/O error, dev sda, sector 126693711 > >>> sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2 > >>> ASC=0x4 ASCQ=0x2 > >>> end_request: I/O error, dev sda, sector 126693711 > >>> ========= > >>> > >> Using a new PSU and a powered hub made no difference. But I found a solution > >> here: > >> > >> http://alienghic.livejournal.com/382903.html > >> > >> Basically, the problem is, as suspected, that the drive spins down / goes to > >> suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda". > >> > >> It seems to me to be an error that the kernel reports this as something like > >> a hardware failure. Or at least very misleading. > >> > > > > Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. > > Should we be disabling auto-spindown when we connect the device, or be able to > > handle this by sending the start command when needed? > > There's more to this. > > My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression. I seriously doubt that. Are you claiming that your USB stick spins itself down during a suspend? And then requires to be spun back up before it will resume proper operation? (Hint: Flash memory devices don't contain rotating media...) Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
