I was sending a message in Pine, quite innocently, this morning, when my
GUI went black and scrolling across the screen where errors such as
the ones below I pulled out of /var/log/messages. After rebooting, I was
told to run fsck as root. I ran the following command:
fsck -A -V ; echo == $? ==
and said yes to everything that passed my way, and the system came back up
again. I have my filesystem partitioned in such a way that /tmp is its own
partition and that's where all the problems were. A lost+found directory
was created and most of the contents moved into it.
What happened, basically? And did what I do remedy the situation? Should I
reformat that partition completely? Is this a sign of disk trouble or
something you inevitably should expect in a 3 year old Redhat 5 system?
Thanks for any help. See errors below:
gary
Dec 14 08:44:38 localhost kernel: hda: read_intr: error=0x01 {
AddrMarkNotFound }, LBAsect
=4894921, sector=10
Dec 14 08:44:39 localhost kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete Da
taRequest Error }
Dec 14 08:44:39 localhost kernel: hda: read_intr: error=0x01 {
AddrMarkNotFound }, LBAsect
=4894921, sector=10
Dec 14 08:44:40 localhost kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete Da
taRequest Error }
Dec 14 08:44:40 localhost kernel: hda: read_intr: error=0x01 {
AddrMarkNotFound }, LBAsect
=4894921, sector=10
Dec 14 08:44:40 localhost kernel: ide0: reset: success
Dec 14 08:44:45 localhost kernel: end_request: I/O error, dev 03:0b,
sector 10
Dec 14 08:46:32 localhost kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete Da
taRequest Error }
Dec 14 08:46:32 localhost kernel: hda: read_intr: error=0x01 {
AddrMarkNotFound }, LBAsect
=4894921, sector=10
Dec 14 08:46:33 localhost kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete Da
taRequest Error }
Dec 14 08:46:33 localhost kernel: hda: read_intr: error=0x01 {
AddrMarkNotFound }, LBAsect
=4894921, sector=10
Dec 14 08:46:34 localhost kernel: hda: read_intr: status=0x59 { DriveReady
SeekComplete Da
taRequest Error }
Dec 14 08:46:40 localhost kernel: EXT2-fs error (device 03:0b):
ext2_write_inode: unable t
o read inode block - inode=2, block=5
Dec 14 08:57:26 localhost kernel: EXT2-fs error (device 03:0b):
ext2_write_inode: unable t
o read inode block - inode=2, block=5
Dec 14 09:04:31 localhost kernel: end_request: I/O error, dev 03:0b,
sector 10
Dec 14 09:04:31 localhost kernel: EXT2-fs error (device 03:0b):
ext2_write_inode: unable t
o read inode block - inode=2, block=5
Dec 14 09:05:01 localhost PAM_pwdb[9494]: (su) session opened for user
root by gnielson(ui
d=0)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
