I just had a MAJOR accident on my computer, and I absolutely can
not believe what happened.
The short story:
I accidentally pryed the power plug from my main hard disk WHILE
THE COMPUTER WAS ON AND RUNNING LINUX! I plugged the cable back
in and linux kept running! Below is the detailed version, along
with a copy of the Linux error messages from /var/log/syslog.
The long story:
I had just downloaded some CD writer software, and other CD
programs. I ran a program called "cd-info" to test some CD's I
have and see what type they are, and how they're stored. Neat
program. I put the Warcraft 2 CD in the CDROM, and ran cd-info.
Neat, Warcraft has audio tracks. I ran "cdp" the cd player
program to try and play the Warcraft audio tracks. It had a
couple errors due to the data track on the CD, but I got it
going.
What? No audio? I checked my speakers, etc... AH! My CDROM
audio cable is not connected to my CDROM! I reached in the case
and tried to free the cable from where it was stuck. I got it
out, ok, but when I went to manipulate the cable to where I
wanted it to go, I bumped the power cable on my hard disk and
jolted it enough that it disconnected. OH SHIT! The computer
seemed to be ok still... I pressed some keys... no problem... I
was freaking! I carefully grabbed the power cable and put it
back on WHILE THE COMPUTER REMAINED ON!! Some error messages
appeared on my console, and I immediately logged out of all
consoles, terminated my ppp session, and rebooted. I powered
down, and powered back up.
Linux came back up like nothing happened. I forced a filesystem
check with "fsck", NO PROBLEMS! I went into /var/log and looked
at the "messages" file: Here is what I found:
Jun 5 08:48:44 red kernel: hdd: media changed
Jun 5 08:49:34 red kernel: hdd : tray open or drive not ready
Jun 5 08:50:22 red last message repeated 4 times
Jun 5 08:50:29 red last message repeated 7 times
Jun 5 08:50:30 red kernel: hdd: media changed
Jun 5 08:51:01 red kernel: hdd: packet command error: status=0x51
Jun 5 08:51:01 red kernel: hdd: packet command error: error=0x50
Jun 5 08:51:01 red kernel: hdd: code: 0x70 key: 0x05 asc: 0x64
ascq: 0x00
Jun 5 08:51:10 red kernel: hdd : tray open or drive not ready
Jun 5 08:51:19 red kernel: hdd: media changed
Jun 5 08:51:19 red kernel: hdd: packet command error: status=0x51
Jun 5 08:51:19 red kernel: hdd: packet command error: error=0x50
Jun 5 08:51:19 red kernel: hdd: code: 0x70 key: 0x05 asc: 0x64
ascq: 0x00
Jun 5 08:53:16 red kernel: hda: read_intr: status=0x51 {
DriveReady SeekComplete Error }
Jun 5 08:53:16 red kernel: hda: read_intr: error=0x04 {
DriveStatusError }
Jun 5 08:53:16 red kernel: hda: read_intr: status=0x51 {
DriveReady SeekComplete Error }
Jun 5 08:53:16 red kernel: hda: read_intr: error=0x04 {
DriveStatusError }
Jun 5 08:53:16 red kernel: hda: read_intr: status=0x51 {
DriveReady SeekComplete Error }
Jun 5 08:53:16 red kernel: hda: read_intr: error=0x04 {
DriveStatusError }
Jun 5 08:53:16 red kernel: hda: read_intr: status=0x51 {
DriveReady SeekComplete Error }
Jun 5 08:53:16 red kernel: hda: read_intr: error=0x04 {
DriveStatusError }
Jun 5 08:53:16 red kernel: ide0: reset: success
As you can see above: My /dev/hda lost power I plugged it in,
and Linux logged a drive error at 08:53:16. ide0 reset: success
I am absolutely ASTONISHED! LINUX RULES!!! Is there ANY
possible way to crash the damned thing? How about if I pour a
cup of coffee onto my motherboard? I'd probably get an error
logged to syslog like this:
Jun 5 08:53:16 red kernel: motherboard: sticky_coffee_detector:
status=0xFC { CoffeeReady CommenceCoffeeBreak Done }
Heheheh!! You guys are doing a WONDERFUL job!!!!!!! I can't
wait to tell everyone I can think of about this incident!
Escape from the confines of Microsoft's operating systems and push your
PC to it's limits with LINUX - a real OS. http://www.redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
