Possible hardware failure? Cryptic kernel messages...

Eric Skaug (eskaug@beta.insolwwb.net)
Sat, 14 Mar 1998 12:31:14 GMT

I need help. The other day a friend accidently kicked my hard drive (don't ask how), and it seems to be acting up. Here's the problem: every time I try to encrypt an mp3 from a .wav file, I get this series of error messages:
ide0: reset: success
hda: status error: status=0x00 { }
end_request: I/O error, dev 03:03, sector 967566
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
ide0: reset: success
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
hda: status error: status=0x00 { }
hda: drive not ready for command
ide0: reset: success
This is repeated until I can't even shift+pageup to the beginning. Also, this appears in /var/log/syslog:
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Mar 14 08:35:42 bogomip kernel: EXT2-fs error (device 03:03): IO error syncing ext2 inode [<2>EXT2-fs error (device 03:03): IO error syncing ext2 inode [%s:%08lx]:0804cb0c]
Mar 14 08:35:43 bogomip kernel: EXT2-fs error (device 03:03): ext2_write_inode:
unable to read inode block - inode=10254, block=40971
After it stops, the mp3 layer has died, and sometimes I get errors like /bin/ls: command not found, or file not found or something, but after a short period of time (sometimes after switching consoles and coming back), it seems to be working well. However, I still can't make mp3s (sometimes it happens when I'm not doing that). I seem to be in over my head here. I don't know if it's a hardware failure or a messed up filesystem or what. I have run e2fsck and badblocks and niether seems to fix the problem.

Please send replies to eskaug@insolwwb.net because I am not a subscriber to the mailing list. Thanks very much.

Eric Skaug

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu