0

I had an old drive beginning to fail and my backups were no good apparently.
I got a new drive larger than the failed one and was able to ddrescue it over, with bad/missing superblocks of course.
Through some fiddling around I was able to mount the new drive, but there were errors of course displayed on a directory listing. I began to copy what I could, and I'm assuming subdirectories had issues, because it errored mid-copy on the new drive and the partition stopped responding.
I cannot get xfs_repair to salvage the new drive saying to secondary superblocks were found.

What are my options here?

I suppose I could ddrescue off the old drive again, which unfortunately took over a day last time, but even then how do I proceed? Running testdisk/photorec would be a nightmare.

Improve this question
3
  • It is not very clear to me why you can't get xfs_repair, in some extreme case xfs_repair -L working. Commented Mar 2, 2023 at 23:24
  • I previously (before partial success mounting the partition) tried the -L flag with the same results (no secondary superblock) but just started it again because why not? Worst case I start over with ddrescue. Commented Mar 3, 2023 at 3:56
  • consider using readonly mounts and/or snapshots / copy-on-write overlays so you don't have to repeate ddrescue after every botched experiment. with snapshots you can just revert any changes made. unfortunately its very difficult to tell remotely what else could be done, it depends on how much data is missing where / the specific nature of the corruption. you can also try your luck with xfsdump. Commented Mar 3, 2023 at 9:19

1 Answer 1

Reset to default
0

My 64TB RAID5 crashed yesterday. The superblock was gone and it would not mount.

I bit the bullet and did a xfs_repair -L. Hours later, the RAID was back, no data lost.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.