search for: md127p3

...RAID volume and partitions? No. Brand new machine, pulled it out of the box and racked it. NOTHING on the internal SSDs. Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No partitions, nothing. However, when I bring it up, fdisk shows an MBR with no partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. Did I need to make a single partition, on each drive, and then make the RAID 1 out of *those*? I don't think I need to have /boot not on a RAID. mark

...itions. But after a thorough review, I found my earlier suggestion of partitioned RAID with the kickstart and RAID management script I provided was the least work for me, in the long term. > However, when I bring it up, fdisk shows an MBR with no partitions. I > can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. I assume you're booting with BIOS, then? One explanation for fdisk showing nothing is that you're using GPT instead of MBR (I think). In order to boot on such a system, you'd need a bios_boot partition at the beginning of the RAID volume to provi...

...wrote: > > No. Brand new machine, pulled it out of the box and racked it. NOTHING on the > internal SSDs. Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No > partitions, nothing. However, when I bring it up, fdisk shows an MBR with no > partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. > > Did I need to make a single partition, on each drive, and then make the RAID 1 > out of *those*? I don't think I need to have /boot not on a RAID. > > mark > > > > ------------------------------ > > -- Eugene Poole Wood...

So, it installed happily. Then wouldn't boot. No problem, I'll bring it up with pxe, then chroot and grub2-install. Um, nope. I edited the device map from hd0 and hd1 being the RAID to /dev/sda and /dev/sdb, then ran grup2-install. It now tells me can't identify the filesystem on hd0, and can't perform a safety check, and gives up. What am I missing? Google is not giving me any