public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Peter Sanders <plsander@gmail.com>, linux-raid@vger.kernel.org
Cc: Phil Turmel <philip@turmel.org>, NeilBrown <neilb@suse.com>
Subject: Re: RAID 6, 6 device array - all devices lost superblock
Date: Sun, 28 Aug 2022 10:14:56 +0100	[thread overview]
Message-ID: <70e2ae22-bbba-77a4-c9bc-4c02752f4cb7@youngman.org.uk> (raw)
In-Reply-To: <CAKAPSkJLd836Zp3xU=zSOHg3qcEmi29Y2qOwWzeAFaDp+dNTvg@mail.gmail.com>

On 28/08/2022 03:00, Peter Sanders wrote:
> have a RAID 6 array, 6 devices.  Been running it for years without much issue.
> 
> Had hardware issues with my system - ended up replacing the
> motherboard, video card, and power supply and re-installing the OS
> (Debian 11).
> 
> As the hardware issues evolved, I'd crash, reboot, un-mount the array,
> run fsck, mount and continue on my way - no problems.
> 
> After the hardware was replaced, my array will not assemble - mdadm
> assemble reports no RAID superblock on the devices.
> root@superior:/etc/mdadm# mdadm --assemble --scan --verbose
> mdadm: looking for devices for /dev/md/0
> mdadm: cannot open device /dev/sr0: No medium found
> mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000)
> mdadm: no RAID superblock on /dev/sda
> mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000)
> mdadm: no RAID superblock on /dev/sdb
> 
> Examine reports
> /dev/sda:
>     MBR Magic : aa55
> Partition[0] :   4294967295 sectors at            1 (type ee)
> 
> Searching for these results indicate I can rebuild the superblock, but
> details on how to do that are lacking, at least on the pages I found.

Ouch. That's not nice, but we should be able to get things back, I hope.

I notice it's looking for your superblock on the drive itself. Were your 
drives partitioned? Because unfortunately, it's well known for drives 
moving between hardware to have their MBR/GPT wiped :-( Hopefully that's 
the case, and examining the drives with gdisk/fdisk will come up with 
"your GPT is damaged. Recover?". If so, you're probably good. If not, do 
you have a record of your partitions? Can you just recreate them? If you 
don't know what you're doing here, I'd wait for a bit more advice unless 
you can back the drives up first.

Whatever happens, do you have a backup? Can you make one?

If your drives were NOT partitioned, then I'm afraid we're into 
forensics here. Read up on overlays, so you can make the drives 
read-only, re-create the superblock, and check if you got it right. I've 
not done this myself, so I would hesitate to advise you, but loads of 
people have said the instructions do work, and they've recovered their 
arrays.
> 
> Currently I have no /dev/md* devices.
> I have access to the old mdadm.conf file - have tried assembling with
> it, with the default mdadm.conf, and with no mdadm.conf file in /etc
> and /etc/mdadm.

It looks like the drives weren't partitioned :-( I think you're into 
forensics.
> 
> Suggestions for how to get the array back would be most appreciated.

Not what you're asking for, but another suggestion - DITCH THOSE DRIVES. 
WD Greens are just plain unsuitable for raid, and if your P300s are new, 
they are too :-( (Greens will be damaged as their optimisation is 
completely wrong for raid, the new P300s are SMR) I notice that ERC is 
disabled ...

I'd get 4x6TB N300s or Seagate Ironwolves (if cost is an issue, you can 
get away with two). If you do get four, swap out two greens, and rebuild 
onto the 6TBs. If you can only afford two, swap out two P300s, raid-0 
them and rebuild as raid-5 onto the 6TB/P300 drives, then you CAN go 
raid-6 raid-0ing a green and your last P300 together. Just get rid of 
the greens asap, and the P300s after.
> 
> Thanks
> - Peter
> 
Cheers,
Wol

  reply	other threads:[~2022-08-28  9:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28  2:00 RAID 6, 6 device array - all devices lost superblock Peter Sanders
2022-08-28  9:14 ` Wols Lists [this message]
2022-08-28  9:54   ` Wols Lists
2022-08-28 16:47     ` Phil Turmel
     [not found]       ` <CAKAPSkJAQYsec-4zzcePbkJ7Ee0=sd_QvHj4Stnyineq+T8BXw@mail.gmail.com>
2022-08-28 17:16         ` Wols Lists
2022-08-28 18:45         ` John Stoffel
2022-08-28 19:36           ` Phil Turmel
2022-08-28 19:49             ` John Stoffel
2022-08-28 23:24               ` Peter Sanders
2022-08-29 13:12                 ` Peter Sanders
2022-08-29 21:45                 ` John Stoffel
2022-08-29 22:29                   ` Eyal Lebedinsky
2022-08-29 23:53                     ` Peter Sanders
2022-08-30 13:27                       ` Peter Sanders
2022-08-30 18:03                         ` Wols Lists
2022-08-31 17:48                           ` Peter Sanders
2022-08-31 20:37                             ` John Stoffel
2022-09-02 14:56                               ` Peter Sanders
2022-09-02 18:52                                 ` Peter Sanders
2022-09-02 19:12                                   ` John Stoffel
2022-09-03  0:39                                     ` Peter Sanders
2022-09-03  5:51                                       ` Peter Sanders
2022-09-05 19:36                                         ` John Stoffel
2022-09-05 20:16                                           ` Peter Sanders
2022-09-05 19:25                                       ` John Stoffel
2022-08-28 15:10 ` John Stoffel
2022-08-28 17:11 ` Andy Smith
2022-08-28 17:22   ` Andy Smith
2022-08-28 17:34     ` Peter Sanders

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=70e2ae22-bbba-77a4-c9bc-4c02752f4cb7@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=philip@turmel.org \
    --cc=plsander@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