Ok, closing. Thanks for the feedback.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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 subscribed to Ubuntu.
--
IMHO this bug can be closed, cause only Gutsy was affected.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-ubuntu-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remain
I had this bug happen to me when I did some Feisty to Gutsy upgrades
this weekend. The MD UUIDs are correct in the
initrd.img-2.6.22-14-generic files, but the scripts are not assembling
the arrays.
The computers with the bug are panic'ing into "VFS: Cannot mount root
filesystem" without providing
Can somebody relabel this one? And I think it can be marked as solved,
too.
--
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 li
dpkg-reconfigure mdadm did not work for me. It turns out that *somehow*
the UUID on my raid array changed and the mdadm.conf never got updated
(possibly when I grew the array with mdadm -grow?) and the change wasn't
obvious, because the first two segments were identical. I only noticed
it when I
I also had this problem. Running "dpkg-reconfigure mdadm" and accepting
all the defaults rebuilt an initrd which fixed the problem for me.
YMMV.
--
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
Thx Paul, works here now!
ARRAY /dev/md0 UUID=
was missing in my mdadm.conf.
--
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 mai
I think I have solved this one now, but cant test till the weekend.
After further scrutiny of the difference between feisty and gutsy
initrd's, I now see that gutsy simply copies your /etc/mdadm/mdadm.conf
into the initramfs. Feisty appears to generate a correct
/etc/mdadm/mdadm.conf with UUID's in
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
> karaluh do you have an lvm inside your raid?
Yes, on the fresh install that boots, no, on the upgrade that doesn't.
--
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 cont
I tried extracting the contents of both the 2.6.20 and 2.6.22 kernels. I
copied the lib/modules/2.6.22-14-generic (gutsy) into the lib/modules
directory of the feisty initrd. This booted up no problem. This proves
that the kernel is NOT the issue here.
As I said before, I believe the problem to be
I have also tried booting up with the gutsy CD into `rescue mode' and
rebuilt the initrd with dpkg-reconfigure linux-image-2.6.22-14-generic.
Needless to say, this didnt help.
I am beginning to wonder if this has anything to do with the version of
mdadm in the initrd? From the look of debugging in
karaluh do you have an lvm inside your raid?
--
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
I cannot reproduce it on fresh install on the other box, so it has to be
some upgrade problem.
--
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.
--
ubu
I have tried installing 2.6.22-14-386 in addition to 2.6.22-14-generic
(default). neither of these kernels will boot. Are you saying that the
2.6.22-13-386 kernel worked for you as opposed to the 2.6.22-13-generic?
Note: its now 14 and not 13...
I am still not so sure its got anything to do with t
Hi,
sorry for the delay - I forgot to say that since one month or so, I managed
to boot my Gutsy without using the Feisty kernel & ramdisk, just updgrading to
linux kernel 2.6.22-13-386.
I think the problem of the md module is gone in that release as I now
boot without problems... please let
Ok. I tried backing out initramfs-tools and recreated the initrd. This
didnt help. I was able to capture the debug output. I did this by
appending `debug' at the kernel command line in grub. The attached is
the output generated in /tmp/ of the initramfs.
** Attachment added: "Initramfs debug outpu
I can confirm this problem too after an upgrade from Feisty to Gutsy,
but I don't think that the problem is a missing module (see below). Here
is my configuration:
Single hard disk (/dev/sda) configured with two Linux RAID Auto partitions.
$ sudo fdisk -l:
=
Disk /dev/sda:
On 20/10/2007, Mike Rutz <[EMAIL PROTECTED]> wrote:
>
> Trying to generate a new initrd for the working feisty kernel produces
> the same result here. Raid isn't detected only the lvms outside the
> raid. Every Initramfs generated with feisty works.
Ok. So it looks like the problem may well be i
Trying to generate a new initrd for the working feisty kernel produces
the same result here. Raid isn't detected only the lvms outside the
raid. Every Initramfs generated with feisty works.
--
gutsy md module not present in ramdisk
https://bugs.launchpad.net/bugs/133765
You received this bug noti
Confirmed. Gutsy 2.6.22 does not boot, while old feisty 2.6.20-16 does.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: New => Confirmed
--
gutsy md module not present in ramdisk
https://bugs.launchpad.net/bugs/133765
You received this bug notification because you are a member
22 matches
Mail list logo
