Hi Ricky, > :( Seems like I'm talking to myself...
I am sorry nobody else jumps in. Problem with waiting such a long time with your replies is it makes that I already forgot what the precise problem was, what you have already tried to solve it, and what I did recommend you to try. > BTW: I've tried the following: > > # mkinitrd --preload raid1 --with=raid1 raid1-initrd.img 2.4.20-18.7 > > ... and no luck. It booted just fine, just no difference and no RAID. I think we already concluded before that the ramdisk probably is not the problem. Since you are using root raid and can't access the machine physically I think you have a serious problem. Instead of debugging the situation you could try recreating the array (you should test if this works without losing your data on another machine first, and to make sure you know the procedure), but the fact that your root fs is on raid makes this very difficult if you are unable to handle the machine. You could try to setup a rescue system on a spare partition, reboot to that (use the -f flag for shutdown to make sure you do not end up in a filesystem check), boot to this rescue partition, fix things from there and boot back to your original system. This is possible but very tricky if you can't handle the machine. 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
