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>, Phil Turmel <philip@turmel.org>
Cc: John Stoffel <john@stoffel.org>, NeilBrown <neilb@suse.com>,
	linux-raid@vger.kernel.org
Subject: Re: RAID 6, 6 device array - all devices lost superblock
Date: Sun, 28 Aug 2022 18:16:55 +0100	[thread overview]
Message-ID: <64746727-8555-291d-d569-c562fc58c55f@youngman.org.uk> (raw)
In-Reply-To: <CAKAPSkJAQYsec-4zzcePbkJ7Ee0=sd_QvHj4Stnyineq+T8BXw@mail.gmail.com>

On 28/08/2022 18:01, Peter Sanders wrote:
> It was set up on the device level, not partitions.  (I remember getting 
> some advice on the web that device was better than partition... Yay for 
> internet advice)

Well, it really SHOULDN'T matter. Except there's plenty of crap software 
that says "ooh a disk with no partition table - it must be empty - let's 
initialise it without asking the user whether it's okay". Or, as in your 
case, it seems like your mobo has wiped the start of the disk for some 
reason. We now recommend partitions, not because it's better, but as a 
defensive mechanism against the idiots out there ... :-(
> 
> I'm surveying my other disks to see what I have available to do the 
> overlay attempt.
> 
> What are the size of the overlay files going to end up being?

I'm not sure what the recommendation is, I think it used to be about 
10%, but I think you'll get away with much less. If you have the space 
ELSEWHERE eg your system partition, try and allow about 1% ie 60GB per 
drive. So you want about 360GB of free space if possible.

I don't think it's dangerous if you don't allow enough space - you'll 
just hit a "disk full" on your overlays which will be a frustration but 
not a disaster. So just give it as much room as you can afford.
> 
> I did run into UEFI vs AHCI issues early in the process.. they are all 
> set to non-UEFI.
> 
> OS update was onto a new SSD...
> 
Cheers,
Wol

  parent reply	other threads:[~2022-08-28 17:17 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
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 [this message]
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=64746727-8555-291d-d569-c562fc58c55f@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=john@stoffel.org \
    --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