Bug#358153: testing (etch): cannot boot on software raid

2006-03-26 Thread Vegard Svanberg
[snip] OK, seems it was an easy one. The it821x controller is detected during installation, but no kernel module existed in the initrd, so it wouldn't work when rebooting after the installation. Made a new one with the module. Works now. Thanks. -- Vegard Svanberg <[EMAIL PROTECTED]

Bug#358153: testing (etch): cannot boot on software raid

2006-03-23 Thread Vegard Svanberg
* Vegard Svanberg <[EMAIL PROTECTED]> [2006-03-23 21:21]: > As it seems now, I assume the reason the machine doesn't boot is because > /dev/hdc and /dev/hde is missing. Any ideas why /dev/hdc and /dev/hde > are not created? Would creating the /dev entries manually get me >

Bug#358153: testing (etch): cannot boot on software raid

2006-03-23 Thread Vegard Svanberg
* Geert Stappers <[EMAIL PROTECTED]> [2006-03-23 09:24]: > On Tue, Mar 21, 2006 at 12:41:08PM +0100, Vegard Svanberg wrote: > > > Grub has set root=/dev/md0. > > That doesn't look "grub". I would expect [snip] True, sort of. I meant that grub in

Bug#358153: testing (etch): cannot boot on software raid

2006-03-21 Thread Vegard Svanberg
; # check if /dev/md0 is there Not there. > mountroot "/dev/md0 does not exist, dropping to a shell!" -- Vegard Svanberg <[EMAIL PROTECTED]> [EMAIL PROTECTED] (EFnet)] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#358153: testing (etch): cannot boot on software raid

2006-03-21 Thread Vegard Svanberg
pts/local-top ... Done. ALERT! /dev/md0 does not exist. Dropping to a shell! Busybox [...] [snip] The raid1 kernel module appears to be in the initrd image, but is not loaded. Loading it manually does not create /dev/md{012}. Grub has set root=/dev/md0. -- Vegard Svanberg <[EMAIL PRO