@^%#@^#!$@#
How the hell do you prevent the kernel/init from trying to start RAID at boot time?
Because so far, I've commented out the array entry in fstab, I've added to mdadm.conf, and I've appended "nomdmonddf" "nomdmonisw" "nodmraid" and "raid=noautodetect" ALL to the kernel boot parameters
and it STILL TRIES TO START RAID.
I'm going to go on a rampage here.
Because so far, I've commented out the array entry in fstab, I've added to mdadm.conf, and I've appended "nomdmonddf" "nomdmonisw" "nodmraid" and "raid=noautodetect" ALL to the kernel boot parameters
and it STILL TRIES TO START RAID.
I'm going to go on a rampage here.
Show all 10 replies
I'm not trying to go after you personally, please understand. Please do not take offense.
I've already wasted six hours on this, and there is literally no way to get a solution, and it's extraordinarily frustrating.
I've already wasted six hours on this, and there is literally no way to get a solution, and it's extraordinarily frustrating.
Ah, the fact that the system doesn't even boot wasn't clear from the original rant.
Don't worry, I don't take offense, I can relate to the frustration.
Maybe a LiveCD + chroot?
EDIT: Also, just theorizing, but maybe this kind of thing needs to be changed inside the initrd.
Did you make sure to update your initramfs after updating your mdadm.conf?
I suspect it's not the kernel, but init/udev that's starting raid. Try booting with init=/bin/sh or /bin/bash or whatever shell you have in initrd, and that should get you a shell prompt without any of the userland initialization. It won't even have the root filesystem mounted, probably, but starting from that point, you can assemble by hand any arrays however you like, mount root, and whatnot. It is a bit inconvenient to use, especially if you should need binaries or libraries that are in the root filesystem only, but PATH and LD_LIBRARY_PATH are your friends.