From: Reindl Harald <h.reindl@thelounge.net>
To: linux-raid@zq3q.org, Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: pls help/review: fed 32 | LVM over raid1, on SSDs & spinning disks
Date: Tue, 6 Oct 2020 19:00:28 +0200 [thread overview]
Message-ID: <1f21b8cb-a9eb-74e8-24b5-550d016b6473@thelounge.net> (raw)
In-Reply-To: <202010061607.096G7CgT4052287@epjdn.zq3q.org>
Am 06.10.20 um 18:07 schrieb linux-raid@zq3q.org:
> Is it possible to get the 2MiB "bios boot" partition into raid1?
> This seems to be the most vulnerable part of my setup.
should be no problem when you have the same partitioning on all disks,
"BIOS boot" normally have no writes at boot time
RAID1 is handeled like a single disk at early boot
the only thing you need to do manually is install the bootloaer on all
disks and don#t forget repeat it after replace one
the only thing i am not sure is the partition type, until now my setups
are MBR and sda1 is a RAID1 over all 4 disks
[root@srv-rhsoft:~]$ fdisk -l /dev/sda
Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000d9ef2
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M fd Linux raid
autodetect
/dev/sda2 1026048 31746047 30720000 14.7G fd Linux raid
autodetect
/dev/sda3 31746048 3906971647 3875225600 1.8T fd Linux raid
autodetect
[root@srv-rhsoft:~]$ df
Filesystem Type Size Used Avail Use% Mounted on
/dev/md1 ext4 29G 7.4G 22G 26% /
/dev/md2 ext4 3.6T 1.2T 2.5T 33% /mnt/data
/dev/md0 ext4 485M 49M 432M 11% /boot
next prev parent reply other threads:[~2020-10-06 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 16:07 pls help/review: fed 32 | LVM over raid1, on SSDs & spinning disks linux-raid
2020-10-06 17:00 ` Reindl Harald [this message]
2020-10-06 22:24 ` antlists
2020-10-06 22:56 ` Roger Heflin
2020-10-07 11:18 ` linux-raid
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=1f21b8cb-a9eb-74e8-24b5-550d016b6473@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=linux-raid@zq3q.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).