问题原文
原帖链接 · Kieran · CC BY-SA 3.0
I have a disk from a Buffalo LinkStation that has an XFS partition on it that I cannot mount.
Plugging the disk into an SATA->USB caddy on an Ubuntu box. I get the following:
$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 63 594404 297171 83 Linux
/dev/sdb2 594405 1590434 498015 83 Linux
/dev/sdb4 1590435 976768064 487588815 5 Extended
/dev/sdb5 1590498 1863539 136521 82 Linux swap / Solaris
/dev/sdb6 1863603 976494959 487315678+ 83 Linux
The problem partition is /dev/sdb6.
$ sudo xfs_check /dev/sdb6
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_check. If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
So trying the xfs_repair -L option gets me to the situation I can't get beyond:
$ sudo xfs_repair -L /dev/sdb6
Phase 1 - find and verify superblock...
superblock read failed, offset 382252089344, size 131072, ag 89, rval -1
fatal error -- Input/output error
Using photorec I have been able to pull some files off that partition, so the data is there and the disk is physically working. However, there is a problem with the superblocks.
How would I recover this partition?
社区高分解答
原帖链接 · ChrisR · CC BY-SA 4.0
The answers above did not help me when I had this issue today (about 9.5 hours ago now). I'll present here the solution that worked for me, along with the reasons why the previous answer did not help.
Symptoms
- Out of nowhere, any file in
/homecould not be saved/edited, etc. or any directory listed. dmesgshowed somewherexfs_do_force_shutdown calledaround a few other xfs messages.xfs_repairfailed in Phase 1 withsuperblock read failedfollowed byfatal error -- Input/output error- The rest of my disk was operating flawlessly (including
/, i.e. only/homewas not working). - Attempting to
mountwould lead tosuperblock cannot be found(or analogous) error, but no hint as to what to do next.
Solution
The solution is based on this post Nigel Smith, the main author of XFS (if I understand correctly). I'll repost the steps here in case the previous link becomes obsolete. All the following operations must be ran as root (evidently).
- Run a long self test of the drive:
smartctl -t long /dev/sda. This may take a while. You can also run a short test withsmartctl -t short /dev/sdaif there is a relatively recent long test (as there was in my case). - Examine the test with either:
smartctl -l selftest /dev/sdaorsmartctl -a /dev/sda(the latter displays everything, but the information you need is almost at the very end). - The last column of the test report is called
LBA_of_first_error. This is the position of the first error on the disk. From the latest test (which will be numbered "#1" and sit at the top of the list), grab the number displayed and divide this by eight and truncating to an integer value (cf. original post as to why). - Then, you will zero-out this specific block. This will lead to the specific file at this position to be corrupted. (But if you have exhausted every other method, a few corrupted files isn't that big a deal.). Do to so, run the following command:
# dd if=/dev/zero of=/dev/sda conv=sync bs=4096 count=1 seek=*NUMBER_COMPUTED_EARLIER* - Perform a short test and wait a minute or two for the result. Repeat this until the short test does not display any error. Or, you can check the approximate number of erroneous block with
smartctl -A /dev/hda | egrep 'Reallocated|Pending|Uncorrectable'In my case, I repeated steps 1 through 4 until I was down to 24 errors. - Run
xfs_repair /dev/sda(without the-Lflag). This will likely report that you should attempt to mount the filesystem because of the journal log errors. - Attempt to mount that system. In my case, that failed, so I had to run
xfs_repair -L /dev/sdawhich deletes the journal log (which may result in data being deleted). - Mount your file system and do a recent backup!
Why the above solutions don't work anymore
- The initial post is several years old. In the meantime, there have been enough changes to XFS for it be considered stable enough by the SuSE team to use as the primary FS for
/home. xfs_checkhas been made obsolete in favor ofxfs_repair -n.- The Debian solution was a horrible hassle and waste of time. As of now, Debian does not support UEFI boot, and that information is not on their download page nor on their main FAQ page (it's on their Wiki). So in order to boot with that, you need to disable UEFI Secureboot in your BIOS and then boot on the key. Afterwards, you'll note that there no xfs tools installed by default. So you'll do
apt-get install xfsprogsonly to realize that, this being Debian, their "stable" packages are literally years behind. Long story short,xfs_repair /dev/sdajust hung forever. The process could not be killed (even with a sigterm). - UFS Explorer is paid-for software.
- photorec only supports specific file types (say bye-bye to your GPG keys) and restores all files with arbitrary names all in one folder. Good luck going through all that and finding relevant information.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
