Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices
On Sun, Dec 19, 2004 at 03:00:13PM +0100, Frederik Schueler wrote:
> Hello,
>
> On Sat, Dec 18, 2004 at 04:35:37PM -0800, Marc Singer wrote:
> > I'm testing this kernel on a machine that resently boots to 2.6.7 with
> > no initrd and, therefore, all drivers for boot are compiled into the
> > kernel.
> > There are four drives in the array, all with type 0xfd. The
> > 2.6.7 kernel finds them automatically. The 2.6.8 package does not,
> > but that isn't the issue as this device isn't needed at boot-time.
>
> Did you add the needed md and raid modules to your initrd?
>
> > Once the kernel boots, I load the raid5 module and look at
> > /proc/mdstat. It looks OK. mdadm --assemble /dev/md0, however,
> > crashes. I haven't saved error messages, though I could write then to
> > a file if need be.
>
> you need to put the modules into /etc/mkinitrd/modules, and recreate you
> initrd with
>
> mkinitrd -o /boot/initrd.img-2.6.8-9-amd64-k8 2.6.8-9-amd64-k8
Added
raid1
raid5
md
to the modules file and booted with the updated initrd. Indeed, the
modules are loaded. The error persists.
>
> and rerun lilo, if you use it.
Using grub.
> This should fix the problem.
Here're the messages from the dmesg log:
On running fdisk -l:
ioctl32(fdisk:4187): Unknown cmd fd(5) cmd(80081272){00} arg(ffffdab8) on /dev/hda
ioctl32(fdisk:4187): Unknown cmd fd(6) cmd(80081272){00} arg(ffffdab8) on /dev/hdb
ioctl32(fdisk:4187): Unknown cmd fd(7) cmd(80081272){00} arg(ffffdab8) on /dev/hdd
ioctl32(fdisk:4187): Unknown cmd fd(8) cmd(80081272){00} arg(ffffdab8) on /dev/sda
ioctl32(fdisk:4187): Unknown cmd fd(9) cmd(80081272){00} arg(ffffdab8) on /dev/sdb
ioctl32(fdisk:4187): Unknown cmd fd(10) cmd(80081272){00} arg(ffffdab8) on /dev/sdc
ioctl32(fdisk:4187): Unknown cmd fd(11) cmd(80081272){00} arg(ffffdab8) on /dev/sdd
On running mdadm --assemble /dev/md0
mdadm[4247]: segfault at 000000000000002c rip 000000000804b19e rsp 00000000ffffdb80 error 4
mdadm[4253]: segfault at 000000000000002c rip 000000000804b19e rsp 00000000ffffdb80 error 4
Reply to: