← Back to team overview

kernel-packages team mailing list archive

[Bug 358971] Re: superblock on md0 confuses boot


** This bug is no longer a duplicate of bug 1003309
   Boot fails after installing updates, error: “cryptsetup: evms_activate is not available"

** No longer affects: mdadm (Ubuntu)

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  superblock on md0 confuses boot

Status in “linux” package in Ubuntu:
  Won't Fix

Bug description:
  My linux system isn't booting anymore and
  boot does halt/not drop to busybox anymore

  My system setup:
  4 sata drives which are combined to a raid10 on /dev/md0

  After one of the later updates of the jaunty 2.6.28-11 kernel my system did not boot properly anymore. When I disable "quiet splash" in the boot args it shows to set up the sata drives and md0.
  Trying to use the md0 as root it says "md0: Unknown partition table".
  Once that's done it prints a "Done." message and then nothing happens (does not even drop to busybox).
  When I hit CTRL+ALT+DEL it says it's stopping the md device.
  Even when I tell the kernel to use a non existant root "/dev/efghr" it does not drop to busybox.
  I had also a previous 2.6.28-10 kernel which booted fine. So I figured it had to be a bug in the kernel so I did a update-initramfs on the 2.6.28-10 kernel and afterwards I have the same behaviour as with the 2.6.28-11 kernel.
  The thing that IMO changed is via update-initramfs a newer version of mdadm seems to be put in the initramfs which seems to be screwed - that's at least the only plausible thing I can think of.

To manage notifications about this bug go to: