Hi! Vagrant Cascadian skribis: > So, this might be sort of a tangent, but I'm wondering why you're > testing raid0 (striping, for performance+capacity at risk of data loss) > instead of raid1 (mirroring, for redundancy, fast reads, slow writes, > half capacity of storage), or another raid level with more disks (raid5, > raid6, raid10). raid1 would be the simplest to switch the code to, since > it uses only two disks. Good point! I guess it would make sense to test RAID1, indeed. I gave it a shot with the patch below. Problem is that installation seemingly hangs here: --8<---------------cut here---------------start------------->8--- + parted --script /dev/vdb mklabel gpt mkpart primary ext2 1M 3M mkpart primary ext2 3M 1.4G mkpart primary ext2 1.4G 2.8G set 1 boot on set 1 bios_grub on + mdadm --create /dev/md0 --verbose --level=mirror --raid-devices=2 /dev/vdb2 /dev/vdb3 mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90 mdadm: size set to 1361920K mdadm: largest drive (/dev/vdb3) exceeds size (1361920K) by more than 1% --8<---------------cut here---------------end--------------->8--- As you can see, it’s attempting to make a RAID1 device out of two partitions (not two disks), which makes no sense in the real world, but is easier to handle here. So I wonder if this is what’s causing it to hang… Thoughts? Ludo’.