Hi Ricky, > The last recommendation I noticed was to try and create a custom ramdisk > to force it to load the raid1 module.
Yeah, but I think you already compared the two images and came to the conclusion that they are identical. In that case creating a ramdisk by hand does not solve anything. O yes, I did suggest you edited linuxrc in the ramdisk to get some debug info. Some commands to get some info on the state of the machine during startup, and probably some sleep's to study / write down the info before it scrolls by. But this editing you can do on the original ramdisk. And yes, you can just re-gzip it. If you edit it a lot it might get somewhat bigger due to the fact that dirty unused sectors/bytes are still available in the image, but for this purpose that is probably not a big problem. > I've recreated the situation on a VMware virtual machine I set up. The > only difference is that I have no control over the type of hard-drives > are "emulated", per se, as it only allows SCSI. The real machine has > IDE drives. Same problem. Upgrade from 2.4.7 -> 2.4.9, just fine. > Upgrade to 2.4.9 -> 2.4.20, no RAID. You should definitely file a bug at http://bugzilla.redhat.com . It's reproducible, and that way you might get the attention of a developer that might actually solve your problem. Maybe the problem has already been reported and somebody might have entered a workaround. Check it out. > Argh. :\ I really wish I had hardware RAID support... bleh. Yup. RAID1 controllers are quite cheap, but when running RAID5 the software solution does save quite some money (on hardware that is). Bye, Leonard. -- How clean is a war when you shoot around nukelar waste? Stop the use of depleted uranium ammo! End all weapons of mass destruction. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
