Software raid-5 on root partition (2.6.32.1)

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

 



Q: Does the 2.6.32.1 kernel still support raid-5 on the root device if
using an initial ram disk?
Q: Since this isn't working for me, have any suggestions of things to
look at?
Q: Is order important when doing an "mkinitrd --preload"?

Background:

When booting with busybox, I can mount the partitions, modify them, etc.
 I'm simply having problems booting.

The raid devices are clean and aren't sync'ing.

I've been running a 2.6.20 variant kernel with a machine who's root
partition is a software raid-5 device (/dev/mdX).  I was not using any
kernel modules to boot, so no initrd was needed.

I'm now trying to run 2.6.32.1 + some additional kernel modules via an
initrd (I put several of the modules in initrd at this point).
Unfortunately, I'm no longer able to boot with the root partition as a
raid-5 device.

The initrd was created using mkinitrd.  I requested that the following
modules should loan on startup with the --preload option:

 - pata_it8213
 - sata_sis
 - pata_sis
 - pata_sch
 - pata_mpiix
 - pata_it821x
 - ata_generic
 - dm-mod
 - dm-multipath
 - dm-mirror
 - dm-log
 - raid1
 - raid456
 - sr_mod
 - aic94xx
 - aic79xx
 - aic7xxx
 - scsi_transport_spi
 - BusLogic
 - mptbase
 - mptsas
 - mptspi
 - mptctl
 - mptfc
 - mptlan
 - mptscsih

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux