Gaspar Bakos wrote:
Hi,
I'll check the cable, or swap it, and see what
happens.
Swapping the cable did not change things, unfortunately.
The main question now is recovery: how to start gently without loosing
things - if this is possible at all.
I remember that the last time I had to run xfs_repair -L, because the
filesystems were not mountable, and simple xfs_repair suggested used of
-L. So, I lost a lot of things (not a surprise, but there seemed to be
no other way to proceed, at least with my knowledge)
Here is the cable situation a bit more detailed:
Originally the failed disk was connected as hda with a cable that indeed
shows some wear (cable #1). The hdb on the same cable, however, showed no
problems (also XFS, what else).
After the crash, I replaced the faulty hda to another linux disk to boot
in, and the faulty disk went in place of hdd, which has a seemingly new
cable, and with which the previous hdd worked fine. All the xfs_check
messages I reported were done with this setup, ie. with cable #2.
Then I put back fauly to hda, and changed cable #1 to yet another cable
(#3), but the same kernel panic happens. Seems like all disks work fine
with all the cables I have (as the faulty one also used to).
So the data probably was corrupted as it was being written to disk. There is
not a lot you can do about this after the fact, you do not know if the
bit is
supposed to be set or not. If you looked at these sectors you will
probably find
the bad bit set in every other byte. repair will do its best on the fs,
you will
probably end up with a lot of stuff in lost+found with numbers as file
names.
The smart utilities are the best way to check the health of the drive
itself, it
may well be fine.
Steve
|