I have also tried placing the mdadm binary from the feisty initrd into the gutsy initrd. This didn't work either. I guess the problem exists somewhere else in the initrd.
Does anyone think this could be a problem with the version of mdadm that created the raid device? I.e. The feisty initrd is the only one that can start the array after an upgrade, because the array was created with a previous version of madam. In this vein, a fresh install may work because the version of mdadm that created the array is the one that now attempts to activate it. I think that this bug may be filed under the wrong package - it has nothing to do with missing modules. Could a developer or the package maintainer please take a look and make a judgment as to whether this bug needs to be moved? -- gutsy md module not present in ramdisk https://bugs.launchpad.net/bugs/133765 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
