[Wylug-discuss] It never rains, but it pours...

[Tim Fletcher]

On Mon, 2012-02-06 at 14:53 +0000, james riley wrote:
> I just discovered and read xfs_repair. It failed. Log dumped. I must
> now rush to a lecture....
> 
> trisquel at trisquel:~$ sudo xfs_repair /dev/sda6
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
> 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_repair.  If you are unable to mount the filesystem, then use
> the -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.
> trisquel at trisquel:~$ sudo xfs_repair -L /dev/sda6
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
> ALERT: The filesystem has valuable metadata changes in a log which is being
> destroyed because the -L option was used.
>         - scan filesystem freespace and inode maps...

> xfs_repair: read failed: Input/output error
> cannot read inode 268436512, disk block 71705104, cnt 16
> Aborted

That reads like a hardware error, the first thing I would do is get a
copy of the disk, with dd or ddrescue before going any further.

If you are still stuck with xfs_repair, you can try something like
photoreq to recover the files from the raw partition.

-- 
Tim Fletcher <tim at night-shade.org.uk>