public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Brand <brand@wmawater.com.au>
To: "Reindl Harald" <h.reindl@thelounge.net>,
	"Roger Heflin" <rogerheflin@gmail.com>,
	"Wols Lists" <antlists@youngman.org.uk>
Cc: "Linux RAID" <linux-raid@vger.kernel.org>,
	"Phil Turmel" <philip@turmel.org>, "NeilBrown" <neilb@suse.com>
Subject: RE: Failed adadm RAID array after aborted Grown operation
Date: Sun, 22 May 2022 14:13:06 +1000 (AEST)	[thread overview]
Message-ID: <054401d86d92$3c59cac0$b50d6040$@wmawater.com.au> (raw)
In-Reply-To: <06995c9b-2dc5-3c0b-9ba1-59be171a7de8@thelounge.net>

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@thelounge.net>
Sent: Saturday, 21 May 2022 1:41 AM
To: Bob Brand <brand@wmawater.com.au>; Roger Heflin <rogerheflin@gmail.com>; 
Wols Lists <antlists@youngman.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>; Phil Turmel 
<philip@turmel.org>; NeilBrown <neilb@suse.com>
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.



  reply	other threads:[~2022-05-22  4:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 13:18 Failed adadm RAID array after aborted Grown operation Bob Brand
2022-05-08 15:32 ` Wols Lists
2022-05-08 22:04   ` Bob Brand
2022-05-08 22:15     ` Wol
2022-05-08 22:19       ` Bob Brand
2022-05-08 23:02         ` Bob Brand
2022-05-08 23:32           ` Bob Brand
2022-05-09  0:09             ` Bob Brand
2022-05-09  6:52               ` Wols Lists
2022-05-09 13:07                 ` Bob Brand
     [not found]                 ` <CAAMCDecTb69YY+jGzq9HVqx4xZmdVGiRa54BD55Amcz5yaZo1Q@mail.gmail.com>
2022-05-11  5:39                   ` Bob Brand
2022-05-11 12:35                     ` Reindl Harald
2022-05-11 13:22                       ` Bob Brand
2022-05-11 14:56                         ` Reindl Harald
2022-05-11 14:59                           ` Reindl Harald
2022-05-13  5:32                             ` Bob Brand
2022-05-13  8:18                               ` Reindl Harald
2022-05-20 15:13                   ` Bob Brand
2022-05-20 15:41                     ` Reindl Harald
2022-05-22  4:13                       ` Bob Brand [this message]
2022-05-22 11:25                         ` Reindl Harald
2022-05-22 13:31                         ` Wols Lists
2022-05-22 22:54                           ` Bob Brand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='054401d86d92$3c59cac0$b50d6040$@wmawater.com.au' \
    --to=brand@wmawater.com.au \
    --cc=antlists@youngman.org.uk \
    --cc=h.reindl@thelounge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=philip@turmel.org \
    --cc=rogerheflin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox