From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Philippe Troin <phil@fifi.org>
Cc: Patrick Mau <mau@oscar.ping.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question about "Not Ready" SCSI error
Date: Tue, 01 Aug 2006 07:56:14 +0200 [thread overview]
Message-ID: <44CEECFE.4000704@s5r6.in-berlin.de> (raw)
In-Reply-To: <877j1tid0h.fsf@tantale.fifi.org>
Philippe Troin wrote:
> Patrick Mau <mau@oscar.ping.de> 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
linux-scsi@vger.kernel.org.
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/
prev parent reply other threads:[~2006-08-01 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 18:10 Question about "Not Ready" SCSI error Patrick Mau
2006-07-30 21:52 ` Johannes Weiner
2006-07-30 23:22 ` Stefan Richter
2006-07-30 22:28 ` Johannes Weiner
2006-07-31 23:13 ` Philippe Troin
2006-08-01 5:56 ` Stefan Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44CEECFE.4000704@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mau@oscar.ping.de \
--cc=phil@fifi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox