lkml.org 
[lkml]   [2000]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectbad CD-ROM disc brought down my machine
Greetings! :)

Here's hoping that this is the right place to report some nastiness I ran
into today.

The problem: A friend burned a CD for me on his Windows machine, which
blue-screened somewhere along the way. We didn't know whether the burn had
finished or not first. So, I put it into my linux machine, grabbed a handy
`md5sum' and started checking files. After checking a few files from the
CD against the originals on my hard drive, many many messages were being
printed to the console. Following is a short snippet from my
/var/log/messages file:

Why I am writing: I couldn't get the messages to stop. Attempts to umount
the disc were unsucessful (umount, when run as root, hung). The messages
didn't stop when I changed to single-user mode. I had to reboot to make
them stop, and, here is the kicker -- none of my filesystems would umount!
So, coming back up, I faced fsck.

What could I have done differently? (Everything on this machine worked
right off the bat with the generic debian distributed kernel, so I found
no need to recompile and never got around to putting in support for the
SysRq key.. ooh how I wish I had that. Oh well, I lost no data afaict.)

I hope this information helps someone down the line from having to reboot
their machine when a bad CD is put in the drive. :)

Thanks!

$ uname -a
Linux sarnold 2.2.15 #1 Tue Apr 25 17:13:48 EST 2000 i686 unknown

Jul 7 14:23:55 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:23:55 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:23:55 sarnold kernel: hdc: ATAPI reset complete
Jul 7 14:23:55 sarnold kernel: end_request: I/O error, dev 16:00 (hdc), sector 426600
Jul 7 14:23:55 sarnold kernel: ATAPI device hdc:
Jul 7 14:23:55 sarnold kernel: Error: Unit attention -- (Sense key=0x06)
Jul 7 14:23:55 sarnold kernel: Power on, reset or bus device reset occurred -- (asc=0x29, ascq=0x00)
Jul 7 14:23:58 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:23:58 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:02 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:24:02 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:05 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:24:05 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:08 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:24:08 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:08 sarnold kernel: hdc: ATAPI reset complete
Jul 7 14:24:08 sarnold kernel: ATAPI device hdc:
Jul 7 14:24:08 sarnold kernel: Error: Unit attention -- (Sense key=0x06)
Jul 7 14:24:08 sarnold kernel: Power on, reset or bus device reset occurred -- (asc=0x29, ascq=0x00)
Jul 7 14:24:12 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:24:12 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:15 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
Jul 7 14:24:15 sarnold kernel: hdc: cdrom_decode_status: error=0x34
Jul 7 14:24:18 sarnold kernel: hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }


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

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.025 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site