[NBLUG/talk] mount and fsck errors
micxz
micxz at slashdomain.com
Sun May 16 14:34:02 PDT 2004
Hi All'
I'm trying to help my friend in debugging some file system errors he
started getting after the power went out!
dmesg reads:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=786495,
sector=786432
end_request: I/O error, dev 03:01 (hda), sector 786432
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=786503,
sector=786440
Then 13-15 lines more with higher "LBAsect" numbers.
blueberry:/ # mount -t reiserfs /dev/hda1 /home
mount: wrong fs type, bad option, bad superblock on /dev/hda1,
or too many mounted file systems
/dev/sdb2 and /dev/sda1 are SCSI and /dev/hda1 is IDE. The issue lie
within the IDE drive or hda1.
When I run fsck on /dev/hda1 I get the output:
blueberry:~ # fsck /dev/hda1
fsck 1.26 (3-Feb-2002)
reiserfsck 3.x.1b (2002)
Will read-only check consistency of the filesystem on /dev/hda1
Will put log info to 'stdout'
###########
reiserfsck --check started at Sun May 16 14:06:43 2004
###########
reiserfs_fetch_ondisk_bitmap: bread failed reading bitmap (98304)
reiserfs_fetch_ondisk_bitmap: bread failed reading bitmap (163840)
reiserfs_fetch_ondisk_bitmap: bread failed reading bitmap (9830400)
reiserfs_fetch_ondisk_bitmap: bread failed reading bitmap (9863168)
reiserfs_fetch_ondisk_bitmap: bread failed reading bitmap (9895936)
Replaying journal..
0 transactions replayed
Checking S+tree../ 2 (of 2)/ 83 (of 86)/ 41 (of 170)
pass_through_tree: unable to read 52959 block on device 0x3
Warning... fsck.reiserfs for device /dev/hda1 exited with signal 6.
fsck.reiserfs /dev/hda1 failed (status 0x8). Run manually!
"Run manually"? "fsck.reiserfs /dev/hda1" Gives the same output.
I've read, "In a particularly bad case you can try mke2fs -S (make
superblocks and group descriptors only). This is described in the man
page --- and is for "last ditch" efforts only." But I'm afraid to try
this as there is data we would love to have on there. Any suggestions
would be great as I have very little experience with disk errors.
--
Micxz
More info:
blueberry:/ # mount -l
/dev/sda1 on / type reiserfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sdb2 on /usr type reiserfs (rw)
shmfs on /dev/shm type shm (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
blueberry:/ # cat /etc/fstab
/dev/sda1 / reiserfs defaults 1 2
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
devpts /dev/pts devpts defaults 0 0
/dev/hda1 /home reiserfs defaults 1 2
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
proc /proc proc defaults 0 0
usbdevfs /proc/bus/usb usbdevfs noauto 0 0
/dev/sdb2 /usr reiserfs defaults 1 2
/dev/sdb1 swap swap pri=42 0 0
blueberry:/ # cat /etc/mtab
/dev/sda1 / reiserfs rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw,mode=0620,gid=5 0 0
/dev/sdb2 /usr reiserfs rw 0 0
shmfs /dev/shm shm rw 0 0
usbdevfs /proc/bus/usb usbdevfs rw 0 0
blueberry:/ # cat /proc/mounts
/dev/root / reiserfs rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/sdb2 /usr reiserfs rw 0 0
shmfs /dev/shm shm rw 0 0
usbdevfs /proc/bus/usb usbdevfs rw 0 0
(odd thing about the mounts above is:
blueberry:/ # ls -l /dev/root
ls: /dev/root: No such file or directory
?)
More information about the talk
mailing list