Message: 3 Date: Sat, 11 Oct 2008 19:55:32 +0200 From: "Bruno GARDIN" bgardin@gmail.com Subject: Rawhide does not boot since 2.6.27-0.398 To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Message-ID: 4a2527c40810111055h3c7b9e7bqb3fd93de477b7cbc@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I am testing rawhide for a few month now but i have problem of boot since kernel 2.6.27-0.398. My rawhide is a virtual system on vmware server now in version 2.0. Whenever i try to boot, i got the following errors at the end : Activating logical volumes VOlume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device Mounting root file system mount: error mounting /dev/root on /sysroot as ext3. No such file or directory Setting up other filesystems setuproot: moving /dev failed:No such file or directory setuproot: error mounting/proc: No such file or directory setuproot: error mounting /sys: No such file or directory Mount failed for selinuxfs on /selinux: No such file or directory Switching to new root and running init swithroot: mount failed: No such file or directory Booting has failed Boot works fine with kernel 2.6.27-0.382 but fails also with 2.6.27-1. I have looked at the thread related to ext4 but i am using ext3. I have also tried a new mkinitrd on 2.6.27-1 but no change. Any idea of what the problem could be ? -- BeGe
Exactly same problem here.
On Sat, 2008-10-11 at 19:46 -0500, Cory Rainey wrote:
Message: 3 Date: Sat, 11 Oct 2008 19:55:32 +0200 From: "Bruno GARDIN" bgardin@gmail.com Subject: Rawhide does not boot since 2.6.27-0.398 To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Message-ID: 4a2527c40810111055h3c7b9e7bqb3fd93de477b7cbc@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I am testing rawhide for a few month now but i have problem of boot since kernel 2.6.27-0.398. My rawhide is a virtual system on vmware server now in version 2.0. Whenever i try to boot, i got the following errors at the end : Activating logical volumes VOlume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device Mounting root file system mount: error mounting /dev/root on /sysroot as ext3. No such file or directory Setting up other filesystems setuproot: moving /dev failed:No such file or directory setuproot: error mounting/proc: No such file or directory setuproot: error mounting /sys: No such file or directory Mount failed for selinuxfs on /selinux: No such file or directory Switching to new root and running init swithroot: mount failed: No such file or directory Booting has failed Boot works fine with kernel 2.6.27-0.382 but fails also with 2.6.27-1. I have looked at the thread related to ext4 but i am using ext3. I have also tried a new mkinitrd on 2.6.27-1 but no change. Any idea of what the problem could be ? -- BeGe
Exactly same problem here.
Seems to be a race condition in the initrd. Recent changes in the kernel have removed dm-mirror, dm-zero, and dm-snapshot as initrd modules. That's resulted in a race condition where lvm starts up too soon, before the scsi devices have settled. More details are in another response in a parallel branch of this thread but there are a couple of workarounds.
Mike
Michael i am following the bugzilla 466071 on this problem but there is no obvious bypass (as far as i understand). What do you suggest as the simplest one ?
Regards.
On Mon, Oct 13, 2008 at 5:54 PM, Michael H. Warfield mhw@wittsend.com wrote:
On Sat, 2008-10-11 at 19:46 -0500, Cory Rainey wrote:
Message: 3 Date: Sat, 11 Oct 2008 19:55:32 +0200 From: "Bruno GARDIN" bgardin@gmail.com Subject: Rawhide does not boot since 2.6.27-0.398 To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Message-ID: 4a2527c40810111055h3c7b9e7bqb3fd93de477b7cbc@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I am testing rawhide for a few month now but i have problem of boot since kernel 2.6.27-0.398. My rawhide is a virtual system on vmware server now in version 2.0. Whenever i try to boot, i got the following errors at the end : Activating logical volumes VOlume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device Mounting root file system mount: error mounting /dev/root on /sysroot as ext3. No such file or directory Setting up other filesystems setuproot: moving /dev failed:No such file or directory setuproot: error mounting/proc: No such file or directory setuproot: error mounting /sys: No such file or directory Mount failed for selinuxfs on /selinux: No such file or directory Switching to new root and running init swithroot: mount failed: No such file or directory Booting has failed Boot works fine with kernel 2.6.27-0.382 but fails also with 2.6.27-1. I have looked at the thread related to ext4 but i am using ext3. I have also tried a new mkinitrd on 2.6.27-1 but no change. Any idea of what the problem could be ? -- BeGe
Exactly same problem here.
Seems to be a race condition in the initrd. Recent changes in the
kernel have removed dm-mirror, dm-zero, and dm-snapshot as initrd modules. That's resulted in a race condition where lvm starts up too soon, before the scsi devices have settled. More details are in another response in a parallel branch of this thread but there are a couple of workarounds.
Mike
-- Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@WittsEnd.com //|=mhw=|// | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Mon, 2008-10-13 at 18:03 +0200, Bruno GARDIN wrote:
Michael i am following the bugzilla 466071 on this problem but there is no obvious bypass (as far as i understand). What do you suggest as the simplest one ?
What I would recommend for the moment is to boot into a working kernel and edit /sbin/mkinitrd and go to line 1411 or there about and change:
wait_for_scsi="no"
to
wait_for_scsi="yes"
Then rebuild your initrd like this:
mkinitrd -f /boot/initrd-2.6.27-3.fc10.i686.img 2.6.27-3.fc10.i686
This may not be the final solution. This is just a workaround to force wait_for_scsi for all initrd builds. That may be suboptimal in the long run but necessary here for now.
Mike
Regards.
On Mon, Oct 13, 2008 at 5:54 PM, Michael H. Warfield mhw@wittsend.com wrote:
On Sat, 2008-10-11 at 19:46 -0500, Cory Rainey wrote:
Message: 3 Date: Sat, 11 Oct 2008 19:55:32 +0200 From: "Bruno GARDIN" bgardin@gmail.com Subject: Rawhide does not boot since 2.6.27-0.398 To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Message-ID: 4a2527c40810111055h3c7b9e7bqb3fd93de477b7cbc@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I am testing rawhide for a few month now but i have problem of boot since kernel 2.6.27-0.398. My rawhide is a virtual system on vmware server now in version 2.0. Whenever i try to boot, i got the following errors at the end : Activating logical volumes VOlume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device Mounting root file system mount: error mounting /dev/root on /sysroot as ext3. No such file or directory Setting up other filesystems setuproot: moving /dev failed:No such file or directory setuproot: error mounting/proc: No such file or directory setuproot: error mounting /sys: No such file or directory Mount failed for selinuxfs on /selinux: No such file or directory Switching to new root and running init swithroot: mount failed: No such file or directory Booting has failed Boot works fine with kernel 2.6.27-0.382 but fails also with 2.6.27-1. I have looked at the thread related to ext4 but i am using ext3. I have also tried a new mkinitrd on 2.6.27-1 but no change. Any idea of what the problem could be ? -- BeGe
Exactly same problem here.
Seems to be a race condition in the initrd. Recent changes in the
kernel have removed dm-mirror, dm-zero, and dm-snapshot as initrd modules. That's resulted in a race condition where lvm starts up too soon, before the scsi devices have settled. More details are in another response in a parallel branch of this thread but there are a couple of workarounds.
Mike
-- Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@WittsEnd.com //|=mhw=|// | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
-- BeGe
On Mon, 2008-10-13 at 15:39 -0400, Michael H. Warfield wrote:
On Mon, 2008-10-13 at 18:03 +0200, Bruno GARDIN wrote:
Michael i am following the bugzilla 466071 on this problem but there is no obvious bypass (as far as i understand). What do you suggest as the simplest one ?
What I would recommend for the moment is to boot into a working kernel and edit /sbin/mkinitrd and go to line 1411 or there about and change:
wait_for_scsi="no"
to
wait_for_scsi="yes"
Then rebuild your initrd like this:
mkinitrd -f /boot/initrd-2.6.27-3.fc10.i686.img 2.6.27-3.fc10.i686
This may not be the final solution. This is just a workaround to force wait_for_scsi for all initrd builds. That may be suboptimal in the long run but necessary here for now.
From the discussion in bugzilla, there's now another option (and a half).
If you use the option --with=scsi_wait_scan with mkinitrd, it should do almost the same thing. It should achieve the same result just slightly differently.
The half option is the same option just another way. It's the fact that this you can stick into /etc/sysconfig/mkinitrd as follows:
MODULES=scsi_wait_scan
So now you don't have to modify the mkinitrd script and you don't have to specify it explicitly on the command line either.
Mike
Mike
Regards.
On Mon, Oct 13, 2008 at 5:54 PM, Michael H. Warfield mhw@wittsend.com wrote:
On Sat, 2008-10-11 at 19:46 -0500, Cory Rainey wrote:
Message: 3 Date: Sat, 11 Oct 2008 19:55:32 +0200 From: "Bruno GARDIN" bgardin@gmail.com Subject: Rawhide does not boot since 2.6.27-0.398 To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Message-ID: 4a2527c40810111055h3c7b9e7bqb3fd93de477b7cbc@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I am testing rawhide for a few month now but i have problem of boot since kernel 2.6.27-0.398. My rawhide is a virtual system on vmware server now in version 2.0. Whenever i try to boot, i got the following errors at the end : Activating logical volumes VOlume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device Mounting root file system mount: error mounting /dev/root on /sysroot as ext3. No such file or directory Setting up other filesystems setuproot: moving /dev failed:No such file or directory setuproot: error mounting/proc: No such file or directory setuproot: error mounting /sys: No such file or directory Mount failed for selinuxfs on /selinux: No such file or directory Switching to new root and running init swithroot: mount failed: No such file or directory Booting has failed Boot works fine with kernel 2.6.27-0.382 but fails also with 2.6.27-1. I have looked at the thread related to ext4 but i am using ext3. I have also tried a new mkinitrd on 2.6.27-1 but no change. Any idea of what the problem could be ? -- BeGe
Exactly same problem here.
Seems to be a race condition in the initrd. Recent changes in the
kernel have removed dm-mirror, dm-zero, and dm-snapshot as initrd modules. That's resulted in a race condition where lvm starts up too soon, before the scsi devices have settled. More details are in another response in a parallel branch of this thread but there are a couple of workarounds.
Mike
-- Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@WittsEnd.com //|=mhw=|// | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
-- BeGe
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list