Does the /boot partition get written to much? The reason why I ask is because I want to install Leap 42.1 on a software raid 0 and I've heard that you can't have the /boot partition on a software raid 0.

Not that it is written to often (generally only when installing an new kernel), but that the software raid probably won't be instantiated when the system needs to read from /boot.

I don't see the point of implementing a software RAID 0 as it provides no fault tolerance. Use LVM instead.

Partition your first disk with a "real" /boot and then provision the remainder of the disk and the whole of the second disk as LVM

1 members found this post helpful.

The /boot partition does not get written to much. Basically, it only gets written to when there is a kernel update. Depending on the frequency of your distribution's updates...maybe a couple times per month.

The point is moot, though, because you can't boot from a software raid 0 boot partition anyway.

I have one system built as a software RAID0 on 4 spare 80GB drives. But /boot is on a normal partition, because it needs to be. (Okay, software RAID1 will work, but that's only because the bootloader sees a member of a RAID1 mirroring array as a normal partition.) My partition setup is:

Basically, everything is in the RAID0 array except for /boot. Note that software RAID0 does not require all members to be the same size. I just did it that way for my own sense of elegance. Normally, I don't even use swap partitions anymore; I prefer swap files.

A more typical setup would be to use a different RAID level because RAID0 will utterly fail if any single member fails. In that case, it would be more typical to put /boot in a RAID1 array - mirrored across all members. That way, if any drive fails, the remaining drives will have a working copy of /boot.

But in my case, any drive failure would sink the entire system anyway. So I put /boot only on the first drive for simplicity.