Looks like I have a failing HD, or bad blocks, on my SME 5.03 server. Any suggestions as to what my next actions should be?
Will going to runlevel 1, and running fsck do the trick? Is there anything else I can do to recover the files from this bad block?
I have the following in my /var/log/messages:
Jan 1 04:02:06 gluon kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 1 04:02:06 gluon kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=38049025, sector=37486680
Jan 1 04:02:06 gluon kernel: end_request: I/O error, dev 03:06 (hda), sector 37486680
Jan 1 04:02:06 gluon kernel: EXT2-fs error (device ide0(3,6)): ext2_write_inode: unable to read inode block - inode=2333955, block=4685835
Jan 1 04:02:11 gluon kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 1 04:02:11 gluon kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=38049025, sector=37486680
Jan 1 04:02:11 gluon kernel: end_request: I/O error, dev 03:06 (hda), sector 37486680
Jan 1 04:02:11 gluon kernel: EXT2-fs error (device ide0(3,6)): ext2_write_inode: unable to read inode block - inode=2333956, block=4685835
Jan 1 04:02:11 gluon kernel: EXT2-fs error (device ide0(3,6)): ext2_write_inode: unable to read inode block - inode=2333954, block=4685835
Jan 1 04:02:11 gluon kernel: EXT2-fs error (device ide0(3,6)): ext2_write_inode: unable to read inode block - inode=2333953, block=4685835