Thanks Reindl. Is xfs_repair an option? And, if it is, do I run it on md125 or the individual sd devices? Unfortunately, restore from back up isn't an option - after all to where do you back up 200TB of data? This storage was originally set up with the understanding that it wasn't backed up and so no valuable data was supposed to have been stored on it. Unfortunately, people being what they are, valuable data has been stored there and I'm the mug now trying to get it back - it's a system that I've inherited. So, any help or constructive advice would be appreciated. Thanks, Bob -----Original Message----- From: Reindl Harald <h.reindl@xxxxxxxxxxxxx> Sent: Saturday, 21 May 2022 1:41 AM To: Bob Brand <brand@xxxxxxxxxxxxxxx>; Roger Heflin <rogerheflin@xxxxxxxxx>; Wols Lists <antlists@xxxxxxxxxxxxxxx> Cc: Linux RAID <linux-raid@xxxxxxxxxxxxxxx>; Phil Turmel <philip@xxxxxxxxxx>; NeilBrown <neilb@xxxxxxxx> Subject: Re: Failed adadm RAID array after aborted Grown operation Am 20.05.22 um 17:13 schrieb Bob Brand: > UPDATE: > > The array finally finished the reshape process (after almost two > weeks!) and I now have an array that's showing as clean with the original > 30 disks. > However, when I try to mount it, I get the message "mount: /dev/md125: > can't read superblock". > > Any suggestions as to what my next step should be? Note: it's still > running from the rescue disk restore from a backup - the array is one thing, the filesystem is a different layer and it seems to be heavily damag after all the things which happened CAUTION!!! This E-mail originated from outside of WMA Water. Do not click links or open attachments unless you recognize the sender and know the content is safe.
