From: Roman Mamedov <rm@romanrm.net>
To: Alexander Shenkin <al@shenkin.org>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Upgrading motherboard + CPU
Date: Fri, 24 Jun 2022 23:44:53 +0500 [thread overview]
Message-ID: <20220624234453.43cf4c74@nvm> (raw)
In-Reply-To: <dab2fe0a-c49e-5da7-5df3-4d01c86a65a7@shenkin.org>
On Fri, 24 Jun 2022 11:27:08 -0700
Alexander Shenkin <al@shenkin.org> wrote:
> I have 1 RAID6 (root) and 1 RAID1 (boot) array running across 7 drives
> in my Ubuntu 20.04 system. I bought a new motherboard and CPU that I'd
> like to replace my current ones. In non-raid systems, I get the sense
> that it's not a very risky operation. However, I suspect RAID makes it
> more tricky.
Luckily with software RAID using mdadm it does not.
> Wondering if anyone can offer any advice here? Do I have to make sure sata
> cables are plugged into corresponding ports in the new motherboard?
No, the order of cables is unimportant. Just plug everything in, and it should
work.
May have to check in BIOS that it doesn't require a UEFI boot partition, but
allows to boot from a legacy-style bootloader, in settings such as "Launch
CSM: Enabled" and "Boot device control: (UEFI and) Legacy".
--
With respect,
Roman
next prev parent reply other threads:[~2022-06-24 18:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:11 a new install - - - putting the system on raid o1bigtenor
2022-06-23 12:56 ` Wols Lists
2022-06-23 14:46 ` ESP and its file system (Re: a new install - - - putting the system on raid) Paul Menzel
2022-06-23 18:54 ` a new install - - - putting the system on raid Pascal Hambourg
2022-06-23 21:39 ` Wols Lists
2022-06-23 22:27 ` Pascal Hambourg
2022-06-23 23:44 ` Wol
2022-06-25 8:27 ` Pascal Hambourg
2022-06-25 11:41 ` Wols Lists
2022-06-26 21:58 ` Pascal Hambourg
2022-06-27 10:50 ` swapping (was "Re: a new install - - - putting the system on raid") David T-G
2022-06-24 18:20 ` a new install - - - putting the system on raid Roman Mamedov
2022-06-24 18:27 ` Upgrading motherboard + CPU Alexander Shenkin
2022-06-24 18:44 ` Roman Mamedov [this message]
2022-06-24 18:46 ` Alexander Shenkin
2022-06-24 19:14 ` Wol
2022-06-24 20:23 ` Alexander Shenkin
2022-06-24 22:00 ` Wol
2022-06-24 22:06 ` Alexander Shenkin
2022-06-24 22:42 ` Ram Ramesh
2022-06-24 22:08 ` Roman Mamedov
2022-06-25 7:14 ` Wols Lists
2022-06-25 7:54 ` Pascal Hambourg
2022-06-25 13:35 ` Stephan
2022-06-25 17:10 ` Wols Lists
2022-06-25 17:38 ` Alexander Shenkin
2022-06-25 17:43 ` Wols Lists
2022-06-25 17:53 ` Alexander Shenkin
2022-06-25 18:41 ` Wols Lists
2022-06-25 22:37 ` Reindl Harald
2022-06-25 22:45 ` Roman Mamedov
2022-06-25 23:40 ` Reindl Harald
2022-06-25 23:50 ` Roman Mamedov
2022-06-25 23:56 ` Reindl Harald
[not found] ` <CAAMCDecEd1po2WpGT_SyimkJLoitRL-=RxKgDdsFA0LX7=2QuQ@mail.gmail.com>
2022-06-26 15:34 ` Alexander Shenkin
2022-06-26 15:44 ` Alexander Shenkin
2022-06-26 16:25 ` Andy Smith
2022-06-26 21:46 ` Pascal Hambourg
2022-06-27 1:32 ` Alexander Shenkin
2022-06-27 8:49 ` Pascal Hambourg
2022-06-27 11:05 ` Roman Mamedov
[not found] ` <693d4b1c-ee58-4cc2-854b-4ae445ff7d24@Spark>
2022-06-27 14:26 ` Pascal Hambourg
2022-06-28 21:32 ` Alexander Shenkin
2022-06-28 21:57 ` Ram Ramesh
2022-06-29 1:05 ` Alexander Shenkin
2022-06-29 2:10 ` Ram Ramesh
2022-06-29 11:23 ` Pascal Hambourg
2022-06-27 7:13 ` Stephan
2022-06-27 10:03 ` Pascal Hambourg
2022-06-25 8:00 ` a new install - - - putting the system on raid Pascal Hambourg
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=20220624234453.43cf4c74@nvm \
--to=rm@romanrm.net \
--cc=al@shenkin.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).