linux-kernel - Re: Question about "Not Ready" SCSI error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	31 Jul 2006 16:13:34 -0700
From:	Philippe Troin <phil@...i.org>
To:	Patrick Mau <mau@...ar.ping.de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Question about "Not Ready" SCSI error

Patrick Mau <mau@...ar.ping.de> writes:

> Hallo everyone
> 
> Today one of my SCSI drives decided to shutdown for no obvious reason.
> I suspect heat or a bad power supply. Syslog shows a repeating stream
> of the following:
> 
> 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?

Phil.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/