Can anyone make head or tail of this in /var/log/messsages ? May 14 18:39:49 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } May 14 18:39:49 linux kernel: hdc: packet command error: error=0x50 May 14 18:39:49 linux kernel: ATAPI device hdc: May 14 18:39:49 linux kernel: Error: Illegal request -- (Sense key=0x05) May 14 18:39:49 linux kernel: Invalid field in command packet -- (asc=0x24, ascq=0x00) May 14 18:39:49 linux kernel: The failed "Start/Stop Unit" packet command was: May 14 18:39:49 linux kernel: "1b 00 00 00 03 00 00 00 00 00 00 00 " May 14 18:39:49 linux kernel: Error in command packet byte 4 bit 0 May 14 18:39:51 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 May 14 18:39:51 linux kernel: ISO 9660 Extensions: RRIP_1991A TIA Nick
At 10:26 AM 5/14/2002 -0700, you wrote:
* Nick Selby (php@nickselby.com) [020514 09:54]:
Can anyone make head or tail of this in /var/log/messsages ?
Probably a hardware error but what kernel is this?
Suse 8.0 brand new clean install on a brand new hard drive.
--
-ckm
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Tuesday 14 May 2002 5:42 pm, you wrote:
Can anyone make head or tail of this in /var/log/messsages ?
May 14 18:39:49 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } May 14 18:39:49 linux kernel: hdc: packet command error: error=0x50 May 14 18:39:49 linux kernel: ATAPI device hdc: May 14 18:39:49 linux kernel: Error: Illegal request -- (Sense key=0x05) May 14 18:39:49 linux kernel: Invalid field in command packet -- (asc=0x24, ascq=0x00) May 14 18:39:49 linux kernel: The failed "Start/Stop Unit" packet command was: May 14 18:39:49 linux kernel: "1b 00 00 00 03 00 00 00 00 00 00 00 " May 14 18:39:49 linux kernel: Error in command packet byte 4 bit 0 May 14 18:39:51 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 May 14 18:39:51 linux kernel: ISO 9660 Extensions: RRIP_1991A
Others have said it's a hardware error, but it might not be. Is hdc your cdrom drive? If not, your disk has a problem. If it is, you might have a faulty CD in it, or a program might be trying to read from the drive in a raw mode (i.e. just opening /dev/cdrom and slurping what's there) without a disk in place. Were you doing anything like that? I get dozens of these reports (exactly the same as yours AFAICT) in my log every time I run Vmware because Vmware samples the CD every so often on Windows' behalf. -- 8:39am up 2 days, 54 min, 1 user, load average: 0.04, 0.06, 0.01
* Derek Fountain (fountai@hursley.ibm.com) [020515 00:46]: ::On Tuesday 14 May 2002 5:42 pm, you wrote: ::> Can anyone make head or tail of this in /var/log/messsages ? ::> ::> May 14 18:39:49 linux kernel: hdc: packet command error: status=0x51 { ::> DriveReady SeekComplete Error } ::> May 14 18:39:49 linux kernel: hdc: packet command error: error=0x50 ::> May 14 18:39:49 linux kernel: ATAPI device hdc: ::> May 14 18:39:49 linux kernel: Error: Illegal request -- (Sense key=0x05) ::> May 14 18:39:49 linux kernel: Invalid field in command packet -- ::> (asc=0x24, ascq=0x00) ::> May 14 18:39:49 linux kernel: The failed "Start/Stop Unit" packet command ::> was: ::> May 14 18:39:49 linux kernel: "1b 00 00 00 03 00 00 00 00 00 00 00 " ::> May 14 18:39:49 linux kernel: Error in command packet byte 4 bit 0 ::> May 14 18:39:51 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 ::> May 14 18:39:51 linux kernel: ISO 9660 Extensions: RRIP_1991A :: ::Others have said it's a hardware error, but it might not be. Is hdc your ::cdrom drive? If not, your disk has a problem. If it is, you might have a ::faulty CD in it, or a program might be trying to read from the drive in a raw ::mode (i.e. just opening /dev/cdrom and slurping what's there) without a disk ::in place. Were you doing anything like that? Also, it could be a problem that I had...the IDE cable simply went bad. I was getting those errors on my root drive and when I replaced the IDE cable they simply disappeared. I don't know how an IDE cable can go bad..but this was the problem. It could be a drive going south, but try replacing the cable first. It's a cheaper solution. :) Cheers! -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
Ben Rosenberg wrote:
Also, it could be a problem that I had...the IDE cable simply went bad. I was getting those errors on my root drive and when I replaced the IDE cable they simply disappeared. I don't know how an IDE cable can go bad..but this was the problem. It could be a drive going south, but try replacing the cable first. It's a cheaper solution. :)
Electrical connections of any kind can become faulty with time, degradating slowly. It's a physical fact, described by reliabitily. Hardware is hard to debug. ;-) -- [---------------------------------------------------------------] [ Prof. Andres Augusto Nogueiras Melendez ] [ Departamento de Tecnologia Electronica - Universidad de Vigo ] [ Campus Lagoas Marcosende, 9 http://www.dte.uvigo.es ] [ 36280 - Vigo, Pontevedra mailto:aaugusto@uvigo.es ] [ Spain tel: +34 986 812 091 fax: +34 986 469 547 ] [---------------------------------------------------------------]
Here's the word from Jens Axboe: Ok, the drive is telling us that there's an invalid bit set in the command data byte. The opcode is start/stop unit, which is used for loading and ejecting media -- the value here is both LoEj and Start bit set, which means "Load the disc (close tray)" simply. So yeah, the drive should be returned for non-compliance to specifications. -- -ckm
On Wednesday 15 May 2002 19:22, Christopher Mahmood wrote:
Here's the word from Jens Axboe:
Ok, the drive is telling us that there's an invalid bit set in the command data byte. The opcode is start/stop unit, which is used for loading and ejecting media -- the value here is both LoEj and Start bit set, which means "Load the disc (close tray)" simply. So yeah, the drive should be returned for non-compliance to specifications.
THANKS! Now, does this mean the hard drive or the CD-ROM? I noticed someone else mentioned the DVD/CD drive as a possibility and also the cable. I had been taking the drive in and out of the notebook (it's a notebook) many times and it's possible it;s just not sitting right.... I'll give it a shot. Thanks so much for following up on this, I really appreciate the help!! Nick
* Nick Selby (php@nickselby.com) [020515 11:02]:
THANKS! Now, does this mean the hard drive or the CD-ROM?
The cdrom.
I noticed someone else mentioned the DVD/CD drive as a possibility and also the cable. I had been taking the drive in and out of the notebook (it's a notebook) many times and it's possible it;s just not sitting right....
It's possibly but axboe's comments suggested that the device was just violating the ATAPI protocol.
Thanks so much for following up on this, I really appreciate the help!!
No problem... -- -ckm
Thanks for the help. It is MUCH appreciated. I wonder if this has anything to do with leaving the Suse DVD in the drive all the time!! Nick Mahmood wrote:
* Nick Selby (php@nickselby.com) [020515 11:02]:
THANKS! Now, does this mean the hard drive or the CD-ROM?
The cdrom.
I noticed someone else mentioned the DVD/CD drive as a possibility and also the cable. I had been taking the drive in and out of the notebook (it's a notebook) many times and it's possible it;s just not sitting right....
It's possibly but axboe's comments suggested that the device was just violating the ATAPI protocol.
Thanks so much for following up on this, I really appreciate the help!!
No problem...
Nick Selby
I wonder if this has anything to do with leaving the Suse DVD in the drive all the time!!
If you mean the errors, the answer is most definitely no! For that the manufacturer is to blame for producing crap hardware. Philipp
participants (6)
-
Andrés A. Nogueiras Meléndez
-
Ben Rosenberg
-
Christopher Mahmood
-
Derek Fountain
-
Nick Selby
-
Philipp Thomas