[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#341177: etch beta1 - raid 5 not working after reboot



On Tue, Nov 29, 2005 at 12:53:28AM +0100, J. de Jong wrote:
> Package: installation-reports
> 
> Debian-installer-version: 11-11-05 (Etch Beta 1)
> uname -a: Linux debian 2.6.12-1-amd64-generic #1 Wed Sep 28 02:05:15 CEST 
> 2005 x86_64 GNU/Linux
> Date: 29-11-05
> Method: I downloaded this image:
> ftp://cdimage.debian.org/pub/cdimage-testing/etch_d-i/i386/beta1/debian-testing-i386-netinst.iso
> burnt it, put it in the cd-drive en booted it.
> 
> Machine: self build machine with an 'Asus K8N4-E Deluxe' motherboard with 
> an nForce 4 chip on it
> Processor: Amd Sempron (2500?)
> Memory: 2 * 256MB (PC 3200) 
> Root Device: IDE 10 gig
> Root Size/partition table: 'Everything in one partition' option selected in 
> instalation
> Output of lspci and lspci -n: 'not found'
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot worked:    [O ]
> Configure network HW:   [O ]
> Config network:         [O ]
> Detect CD:              [O ]
> Load installer modules: [O ]
> Detect hard drives:     [O ]
> Partition hard drives:  [O ]
> Create file systems:    [O ]
> Mount partitions:       [O ]
> Install base system:    [O ]
> Install boot loader:    [O ]
> Reboot:                 [E ]
> 
> Comments/Problems:
> 
> After Instalation the computer reboots everything seems to works fine but 
> debian has not assembled the raid array i made in the installer. It seems 
> that while booting mdadm wants to assemble when the sata drivers/modules 
> are not yet loaded. I tried installing the system without the array and 
> then later add create it but that doesnt help. Any suggestions?

Which controller is your root on and which controller runs your drives
for the raid5?  

If the controller for your raid drives requires a different driver than
the one used for root, then it won't be loaded until
discover/udev/hotplug stuff goes searching for it.  To fix it, simply
add it to /etc/modules which is loaded before mdadm runs, while the auto
detection and loading happens after mdadm runs.

Len Sorensen



Reply to: