From: Leslie Rhorer <lesrhorer@att.net>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Need to move RAID1 with mounted partition
Date: Wed, 20 Apr 2022 07:24:08 -0500 [thread overview]
Message-ID: <6c3ff307-23b4-8ad5-9061-b6076ebd2195@att.net> (raw)
In-Reply-To: <11e5dc60-1c00-4cfa-8b4e-ab0839a5fd9f@plouf.fr.eu.org>
On 4/20/2022 7:07 AM, Pascal Hambourg wrote:
> Le 20/04/2022 à 13:08, Andy Smith wrote:
>>
>> On Wed, Apr 20, 2022 at 03:40:12AM -0500, Leslie Rhorer wrote:
>>> The third partition on each drive is assigned as swap, and of
>>> course it was easy to resize those partitions, leaving an
>>> additional 512MB between the second and third partitions on each
>>> drive. All I need to do is move the second partition on each
>>> drive up by 512MB.
>>
>> I'd be tempted to just make these two new 512M spaces into new
>> partitions for a RAID-1 and move your /boot to that, abandoning the
>> RAID-1 you have for the /boot that is using the partitions at the
>> start of the disk.
>
> I agree, unless the BIOS cannot read sectors at that offset.
>
> Or you could create a RAID10 array with the 4 partitions if they have
> similar sizes.
They don't. 'Not even close.
>
> Or you could move /boot back into the / filesystem.
I would rather not.
>
> In either case, the BIOS restriction applies and you may need to
> reinstall the boot loader on both drives.
I did so just for safety. Whether it was actually needed or not, who
knows?
> Or you could try to reduce the required space in /boot :
> - remove old kernels
I did that. It wasn't enough. Eventually I just moved the kernel files
and created symlinks before completing the upgrade on one system. The
other got the resize treatment.
> - reduce initramfs size with MODULES=dep instead of MODULES=most in
> /etc/initramfs-tools/initramfs.conf
I didn't try that. It probably would have worked.
> - remove plymouth if installed
Nope.
next prev parent reply other threads:[~2022-04-20 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 16:44 Trying to rescue a RAID-1 array Bruce Korb
2022-03-31 17:06 ` Wols Lists
2022-03-31 18:14 ` Bruce Korb
2022-03-31 21:34 ` Wols Lists
2022-04-01 17:59 ` Bruce Korb
2022-04-01 18:21 ` Bruce Korb
2022-04-01 19:45 ` Wol
2022-04-01 20:23 ` Bruce Korb
2022-04-01 21:02 ` Wol
2022-04-01 21:24 ` Bruce Korb
2022-04-01 21:33 ` Wol
2022-04-20 8:40 ` Need to move RAID1 with mounted partition Leslie Rhorer
2022-04-20 8:55 ` Roman Mamedov
2022-04-20 9:21 ` Leslie Rhorer
2022-04-20 11:08 ` Andy Smith
2022-04-20 12:07 ` Pascal Hambourg
2022-04-20 12:24 ` Leslie Rhorer [this message]
2022-04-20 12:16 ` Leslie Rhorer
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=6c3ff307-23b4-8ad5-9061-b6076ebd2195@att.net \
--to=lesrhorer@att.net \
--cc=linux-raid@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox