Philippe Troin wrote:
> Patrick Mau <[email protected]> writes:
...
>> Jul 30 15:51:30 tony kernel: sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
>> Jul 30 15:51:30 tony kernel: ASC=0x4 ASCQ=0x2
>> Jul 30 15:51:30 tony kernel: end_request: I/O error, dev sda, sector 617358
>>
>> Google revealed[1] that the drive is waiting for a START UNIT command,
>> but it seems that the kernel is not attempting to spin up the drive
>> again.
>>
>> After a complete power-cycle the drive worked again. I just wanted to
>> know if this is a shortcoming in the SCSI error handling codepath.
>
> I'll have to report that I've seen a few drives behaving similarly,
> both on 2.4.x and 2.6.x.
>
> Is that an expected behavior from SCSI hard drives? Any SCSI guru
> would be able to answer this one?
I am not a SCSI guru but answer anyway. The gurus are over at
[email protected].
Doug Gilbert has an overview about SCSI power management:
http://sg.torque.net/sg/power.html
Long ago Brian King submitted code to the SCSI error handler of Linux
2.6 that issues the START STOP UNIT command. This code is inactive per
default to avoid clashes with USB disks.
http://marc.theaimsgroup.com/?l=linux-scsi&m=107702811830956
A recently merged patch allows to activate this code via a sysfs
attribute. http://lkml.org/lkml/2006/7/30/261
I don't know if there is similar code for Linux 2.4.
--
Stefan Richter
-=====-=-==- =--- ----=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
