Hi Pete, You may not have seen my other post. /boot is a seperate partition on /dev/sda1 If the raid of / were an issue wouldn't I expect to see the same issue when using a standard boot disk (via mkbootdisk). They are the same initrd, right? Cheers, Harry Quoting Pete Nesbitt <pete@xxxxxxxxx>: *> *> Hi, *> The software RAID is required before you can access the software raided *> drives. Are you trying to load that as a module or is compiled into the *> kernel. *> If I have this right, if raid is comiled into the kernel, then /boot needs *> to *> be a regular partition (non raid) if your using modules, you cannot set *> either / or /boot as a raid partition because it needs to access the modules *> on / to load the raid. *> *> So it boot / as raid, compile your kernel with raid and make sure /boot is *> not *> in the raid set. *> -- *> Pete Nesbitt, rhce -- Harry Hoffman hhoffman@xxxxxxxxxxxxxxxx ------------------------- The next time your boss says: "Let's not focus on the negative, but rather look at the positive", punch them in the gut and respond: "Let's not focus on how negative this makes you feel but rather how positive I am now feeling". ------------------------------------------------- This mail sent through IpSolutions: http://www.ip-solutions.net/ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
