A JM schrieb:
I've managed to get an image file of the drive that was dying using
dd_rescue and have tried to run xfs_repair -f /dev/hdb1 with the following
um, what was hdb1 again? in  you showed us your fstab, hdb1 is not
listed there? is it part of your LVM setup? iirc it was the latter - a
part of your LVM setup. if this is so and if i understand LVM correctly,
you *always* work with fs-related tools on the logical volume.
so you really should try to
0) find out your lvm-setup ( /etc/lvm/lvm.conf !)
1) setup your LVM, e.g.:
% vgcreate VGforMyth /dev/hdb1 /dev/hdb4 /dev/hdb...
% lvcreate -n video VGforMyth
2) xfs_repair -n /dev/VGforMyth/video
but if you really have trouble with LVM you should probably ask some
lvm-user . i've never really used LVM, just played around with it a
bit. after LVM issues are sorted out, you can go on and 1) find out what
filesystem was on your logical volume and 2) run the right fsck tool.
PS: as to what the error shows here:
.....found candidate secondary superblock...
superblock read failed, offset 209002168320, size 2048, ag 0, rval 22
fatal error -- Success
i don't know. it's bad, it's not something i expect from any fsck tool
and the message is not very userfriendly at all. win95 error messages
come to my mind...aaargh.