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-next>] [day] [month] [year] [list]
Message-ID: <20060730181014.GA13456@oscar.prima.de>
Date:	Sun, 30 Jul 2006 20:10:19 +0200
From:	Patrick Mau <mau@...ar.ping.de>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Question about "Not Ready" SCSI error

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.

Regards,
Patrick

Additional Info:

Kernel:		2.6.18-git (from 29-July-2006)

SCSI HW:	Adaptec 3960D Ultra160 SCSI adapter
		aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Harddisk:	Vendor: IBM
		Model: IC35L036UCD210-0
		Rev: S5BA
		Type: Direct-Access
		ANSI SCSI revision: 03
		Tagged Queuing enabled.  Depth 64
		FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 63)

[1] http://en.wikipedia.org/wiki/KCQ
2     04      02      Not Ready - need initialise command (start unit)

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ