From: Wols Lists <antlists@youngman.org.uk>
To: Jun-Kai Teoh <kai.teoh@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID5 up, but one drive removed, one says spare building, what now?
Date: Fri, 10 Nov 2017 23:17:38 +0000 [thread overview]
Message-ID: <5A063392.4060809@youngman.org.uk> (raw)
In-Reply-To: <e23f4047-9e7d-73b5-0dad-81575a04649c@turmel.org>
On 10/11/17 21:58, Phil Turmel wrote:
>>> But don't add any more complete devices to the array -- use a
>>> >> partition that starts at 1MB and covers the rest of the device
>>> >> (default for most partition tools nowadays).
>> >
>> > Where can I read about how to do this properly? I tried googling it
>> > but I'm pretty lost. Or what tool I should use etc.
> parted or gdisk or a very modern version of fdisk will let you partition
> your new drives. They will default to a "GPT" disk label and will
> generally place the first partition you create in the "right" place -- a
> multiple of 4K, typically 1MB. When you save the new partition table
> (aka disk label), the #1 partition will show up in your list of devices.
>
>>> >> I recommend that when/if your array is stable again, you add one
>>> >> more spare (with partition) and then use mdadm's --replace
>>> >> operation to move complete-device members to the new member. When
>>> >> each is done, take the newly freed device and partition it and do
>>> >> the next. When you have no more complete-device members and have
>>> >> the last freed device partitioned, consider converting to raid6
>>> >> with that spare.
>> >
>> > I think I understand what you mean here, but it sounds like I need to
>> > figure out the top two parts first and that'll take me awhile.
If you take the wiki slowly, you'll hopefully grasp what's going on.
https://raid.wiki.kernel.org/index.php/Linux_Raid#Overview
Especially the bit about setting up a new system or converting an
existing system. Okay, they're not at all about what you're doing, but
if you work your way through and get what's happening there straight in
your head, you'll then be able to apply it to your setup.
Note that they're written from my perspective as a gentoo user, so I
have to do everything from scratch - boot into a live/rescue CD, and
then configure/setup the system from there.
I know it doesn't cover LVM - that is very patchy at the moment - but I
just need to troubleshoot my new machine to get a bios screen, and I'll
be setting that up with LVM and all that should be appearing on the wiki.
(My new system at the moment isn't even POSTing :-( I'm not used to
troubleshooting builds, I've usually been lucky, so I hope everything is
working soon :-)
Cheers,
Wol
next prev parent reply other threads:[~2017-11-10 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 3:09 RAID5 up, but one drive removed, one says spare building, what now? Jun-Kai Teoh
2017-11-10 11:31 ` Wols Lists
2017-11-10 13:01 ` Phil Turmel
2017-11-10 13:13 ` Mark Knecht
2017-11-10 17:25 ` Jun-Kai Teoh
2017-11-10 18:01 ` Phil Turmel
2017-11-10 18:15 ` Jun-Kai Teoh
2017-11-10 19:04 ` Phil Turmel
2017-11-10 19:22 ` Jun-Kai Teoh
2017-11-10 21:58 ` Phil Turmel
2017-11-10 23:17 ` Wols Lists [this message]
2017-11-10 23:22 ` Wols Lists
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=5A063392.4060809@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=kai.teoh@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.