Dear fellow testers,
new kernel does not boot on ext4dev machine, should I file a bug, when I boot up I get:
Creating root device. Mounting root filesystems. mount: error mounting /dev/root on /sysroot as ext4dev: No such device 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 runing init. switchroot: mount failed: No such file or directory Booting has failed.
Thanks for advice/suggestions
Regards,
Antonio
this is caused because ext4dev was renamed to ext4,
have you tried to rebuild initrd with ext4 module ?
On 10/10/2008 9:54 AM, Antonio Olivares wrote:
Dear fellow testers,
new kernel does not boot on ext4dev machine, should I file a bug, when I boot up I get:
Creating root device. Mounting root filesystems. mount: error mounting /dev/root on /sysroot as ext4dev: No such device 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 runing init. switchroot: mount failed: No such file or directory Booting has failed.
Thanks for advice/suggestions
Regards,
Antonio
--- On Fri, 10/10/08, Itamar - IspBrasil itamar@ispbrasil.com.br wrote:
From: Itamar - IspBrasil itamar@ispbrasil.com.br Subject: Re: new kernel 2.6.27-1.fc10 does not boot To: olivares14031@yahoo.com, "For testers of Fedora Core development releases" fedora-test-list@redhat.com Date: Friday, October 10, 2008, 5:58 AM this is caused because ext4dev was renamed to ext4,
have you tried to rebuild initrd with ext4 module ?
No :( Previous kernels booted properly by default. The updates should just work, should they not?
BTW, How do I run mkinitrd against new kernel, I have done that only 1 or two times, so I am not very familiar with the process :(
Thank you for answering!
Regards,
Antonio
On 10/10/2008 9:54 AM, Antonio Olivares wrote:
Dear fellow testers,
new kernel does not boot on ext4dev machine, should I
file a bug, when I boot up I get:
Creating root device. Mounting root filesystems. mount: error mounting /dev/root on /sysroot as
ext4dev: No such device
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 runing init. switchroot: mount failed: No such file or directory Booting has failed.
Thanks for advice/suggestions
Regards,
Antonio
Antonio Olivares wrote:
Dear fellow testers,
new kernel does not boot on ext4dev machine, should I file a bug, when I boot up I get:
Creating root device. Mounting root filesystems. mount: error mounting /dev/root on /sysroot as ext4dev: No such device 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 runing init. switchroot: mount failed: No such file or directory Booting has failed.
Thanks for advice/suggestions
Regards,
Antonio
There is actually a newer kernel in koji you could try that one.
But I saw this couple of day's ago before I wiped out the installations for some anaconda testing then it did not work on ext3, ext3 encrypted and ext4 encrypted ( Propably I keept these 3 installation equally updated ) but I did not encounter it on an unencrypted ext4 installation ( probably because I had not updated but I did at that time and I did not hit that error) .
Dont think these errors are filesystem related.
JBG
On Fri, Oct 10, 2008 at 2:54 PM, Antonio Olivares olivares14031@yahoo.com wrote:
Dear fellow testers,
new kernel does not boot on ext4dev machine, should I file a bug, when I boot up I get:
I guess no bug is needed: http://thread.gmane.org/gmane.linux.redhat.fedora.devel/94211
--- On Fri, 10/10/08, Gianluca Sforna giallu@gmail.com wrote:
From: Gianluca Sforna giallu@gmail.com Subject: Re: new kernel 2.6.27-1.fc10 does not boot To: olivares14031@yahoo.com, "For testers of Fedora Core development releases" fedora-test-list@redhat.com Date: Friday, October 10, 2008, 6:56 AM On Fri, Oct 10, 2008 at 2:54 PM, Antonio Olivares olivares14031@yahoo.com wrote:
Dear fellow testers,
new kernel does not boot on ext4dev machine, should I
file a bug, when I boot up I get:
I guess no bug is needed: http://thread.gmane.org/gmane.linux.redhat.fedora.devel/94211
-- Gianluca Sforna
http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna
Thanks Gianluca for linking to that message. How should we proceed to fix the mounting part and get it to work?
Regards,
Antonio
On Fri, Oct 10, 2008 at 4:30 PM, Antonio Olivares olivares14031@yahoo.com wrote:
Thanks Gianluca for linking to that message. How should we proceed to fix the mounting part and get it to work?
Not sure. I suggest you ask Eric in that thread
Gianluca Sforna wrote:
On Fri, Oct 10, 2008 at 4:30 PM, Antonio Olivares olivares14031@yahoo.com wrote:
Thanks Gianluca for linking to that message. How should we proceed to fix the mounting part and get it to work?
Not sure. I suggest you ask Eric in that thread
Sorry guys.
Here's what I suggest...
Boot back to an older kernel, update e2fsprogs, and rebuild the initrd for the new kernel.
If rebuilding the initrd is daunting to you, just uninistall the newer kernel, then re-install it.
-Eric
--- On Fri, 10/10/08, Eric Sandeen sandeen@redhat.com wrote:
From: Eric Sandeen sandeen@redhat.com Subject: Re: new kernel 2.6.27-1.fc10 does not boot To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Date: Friday, October 10, 2008, 9:17 AM Gianluca Sforna wrote:
On Fri, Oct 10, 2008 at 4:30 PM, Antonio Olivares olivares14031@yahoo.com wrote:
Thanks Gianluca for linking to that message. How
should we proceed to fix the mounting part and get it to work?
Not sure. I suggest you ask Eric in that thread
Sorry guys.
Here's what I suggest...
Boot back to an older kernel, update e2fsprogs, and rebuild the initrd for the new kernel.
If rebuilding the initrd is daunting to you, just uninistall the newer kernel, then re-install it.
-Eric
--
Tried that to no avail :( Does not work!
How do I rebuild initrd, I have done it before but do not know the steps :( I normally do not do it often :(
Thanks,
Antonio
Antonio Olivares wrote:
Tried that to no avail :( Does not work!
same failure?
How do I rebuild initrd, I have done it before but do not know the steps :( I normally do not do it often :(
mkinitrd -f /boot/initrd-$UNAME.img $UNAME
i.e.
mkinitrd -f /boot/initrd-2.6.27-1.fc10.img 2.6.27-1.fc10
the -f will overwrite the old image.
Ugh I might know what's going on here.
the initrd hard-codes the name of the root fs, IIRC.
Try replacing ext4dev with ext4 in /etc/fstab before you re-make the initrd...
Also add -v to the mkinitrd commandline, see if it is including the ext4 module?
-Eric
Eric Sandeen wrote:
Antonio Olivares wrote:
Tried that to no avail :( Does not work!
same failure?
How do I rebuild initrd, I have done it before but do not know the steps :( I normally do not do it often :(
mkinitrd -f /boot/initrd-$UNAME.img $UNAME
i.e.
mkinitrd -f /boot/initrd-2.6.27-1.fc10.img 2.6.27-1.fc10
the -f will overwrite the old image.
Ugh I might know what's going on here.
the initrd hard-codes the name of the root fs, IIRC.
Try replacing ext4dev with ext4 in /etc/fstab before you re-make the initrd...
Also add -v to the mkinitrd commandline, see if it is including the ext4 module?
-Eric
Per notting's excellent suggestion, I think we can just put a module alias for ext4dev into the now-called-ext4 module, and it'll all Just Work.
I'll make sure the other ext4 devs are happy with that change, and commit it.
Thanks, -Eric
Eric Sandeen wrote:
Per notting's excellent suggestion, I think we can just put a module alias for ext4dev into the now-called-ext4 module, and it'll all Just Work.
I'll make sure the other ext4 devs are happy with that change, and commit it.
Note to self: test first, email later.
the module alias isn't sufficient either - I think you will have to hand-edit fstab to say "ext4" and re-make the initrd. Sorry. Thanks for running devel code! :)
-Eric
On 2008-10-10, 19:09 GMT, Eric Sandeen wrote:
the module alias isn't sufficient either - I think you will have to hand-edit fstab to say "ext4" and re-make the initrd. Sorry. Thanks for running devel code! :)
There is one more problem, but more likely in ex2fsprogs or something. Apparently fsck when running autocheck is not able to resolve LABEL=boot (which happens to be my /boot) and hangs. I had to edit /etc/fstab and rerun mkinitrd to make my system boot. /var/log/messages, /var/log/dmesg and the output of tune2fs -l /dev/sda1 is available on http://mcepl.fedorapeople.org/tmp/2.6.27-1.fc10.i686/
Best,
Matěj
Matej Cepl wrote:
On 2008-10-10, 19:09 GMT, Eric Sandeen wrote:
the module alias isn't sufficient either - I think you will have to hand-edit fstab to say "ext4" and re-make the initrd. Sorry. Thanks for running devel code! :)
There is one more problem, but more likely in ex2fsprogs or something. Apparently fsck when running autocheck is not able to resolve LABEL=boot (which happens to be my /boot) and hangs. I had to edit /etc/fstab and rerun mkinitrd to make my system boot. /var/log/messages, /var/log/dmesg and the output of tune2fs -l /dev/sda1 is available on http://mcepl.fedorapeople.org/tmp/2.6.27-1.fc10.i686/
Best,
Matěj
(the "messages" file is read-only)
You have /boot on ext4dev? that's not supposed to work at all...
Hm, on further inspection this looks like an ext3 filesystem but with test_fs set? Strange.
How did you edit fstab? I guess you mean for s/ext4dev/ext4/ on root? Did you change something for /boot ?
Thanks, -Eric
On 2008-10-10, 21:44 GMT, Eric Sandeen wrote:
You have /boot on ext4dev? that's not supposed to work at all...
Hm, on further inspection this looks like an ext3 filesystem but with test_fs set? Strange.
Yeah, this was the problem. However, when fixing this, I've made another disaster -- I unfortuantely removed also test_fs from / partition (not only /boot). And the result was pretty wild -- I got panicking kernel on boot with that (Linux refused to mount / on a partition with ext4 filesystem but without test_fs option). We should really have some protection against stupid users -- kernel panic is not a good reaction IMHO.
Matěj
--- On Fri, 10/10/08, Eric Sandeen sandeen@redhat.com wrote:
From: Eric Sandeen sandeen@redhat.com Subject: Re: new kernel 2.6.27-1.fc10 does not boot To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Date: Friday, October 10, 2008, 12:09 PM Eric Sandeen wrote:
Per notting's excellent suggestion, I think we can
just put a module
alias for ext4dev into the now-called-ext4 module, and
it'll all Just Work.
I'll make sure the other ext4 devs are happy with
that change, and
commit it.
Note to self: test first, email later.
the module alias isn't sufficient either - I think you will have to hand-edit fstab to say "ext4" and re-make the initrd. Sorry. Thanks for running devel code! :)
-Eric
--
I edited /etc/fstab and changed ext4dev to ext4, tried mkintrd command failed with it, but removed kernel and reinstalled it and now I'm back with new kernel :)
[olivares@riohigh ~]$ uname -ipr 2.6.27-1.fc10.i686 athlon i386 [olivares@riohigh ~]$
Thanks for your help and all others who answered this thread! Without you guys this would have been a pain in the #$$?$##$#
Regards,
Antonio