Ijust upgrade my kernel from 2.6.0.1.104 to 2.6.0.1.107 and then reboot my system and I got the following error kernel panic: vfs unable to mount fs on unknown -block(0,0) what could be the cause of that an how to solve that problem
try root=/dev/hdax in grub.conf, hdax is your root partition. I hope it works.
Regards, Bartolomeus Irwanto
Ijust upgrade my kernel from 2.6.0.1.104 to 2.6.0.1.107 and then reboot my system and I got the following error kernel panic: vfs unable to mount fs on unknown -block(0,0) what could be the cause of that an how to solve that problem
-- fedora-test-list mailing list fedora-test-list@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-test-list
__________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
On Tue, 2003-12-30 at 11:21, Bartolomeus Irwanto wrote:
try root=/dev/hdax in grub.conf, hdax is your root partition. I hope it works.
Got this one today (just updated to latest arjanv kernel); specifying the root device by name instead of by label works, but the root is mounted as ext2 instead of ext3...
Klaasjan
Looking back, it seems nobody in that thread had the syntax right, it should be root=LABEL=/ if the label of your root fs is "/"
This root= thing is actually at least 2 distinct buglets that are becoming an overall problem that should probably be bugzilla'd as "inconsistent support for root= option"
root=/dev/sda6 wasn't working for me with 2.6.x, and I spent some time tearing my hair out before figuring out I needed to label things. This will cause headaches with upgrades to FC2 for people who originally installed redhat 6 and got to fedora through a series of upgrades (so they dont have labelled filesystems)
And now apparently the root=LABEL=/ system may not work for some people--I assume it applies to those who aren't using initial ramdisks.(?) (Under what kernel versions, 2.4 2.6? This info should go into bugzilla)
Seems both those pieces of logic in the kernel could stand to be rewritten as a single subroutine
Klaasjan Brand wrote:
On Tue, 2003-12-30 at 11:21, Bartolomeus Irwanto wrote:
try root=/dev/hdax in grub.conf, hdax is your root partition. I hope it works.
Got this one today (just updated to latest arjanv kernel); specifying the root device by name instead of by label works, but the root is mounted as ext2 instead of ext3...
Klaasjan
-- fedora-test-list mailing list fedora-test-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-test-list
On Sat, 03 Jan 2004 09:37:14 -0500 Nathan Bryant nbryant@optonline.net wrote:
root=/dev/sda6 wasn't working for me with 2.6.x, and I spent some time tearing my hair out before figuring out I needed to label things. This will cause headaches with upgrades to FC2 for people who originally installed redhat 6 and got to fedora through a series of upgrades (so they dont have labelled filesystems)
You are not forced to use labels. Specifying the correct drive/partition will work. Not sure what you were doing wrong in the example you mention.
And now apparently the root=LABEL=/ system may not work for some people--I assume it applies to those who aren't using initial ramdisks.(?) (Under what kernel versions, 2.4 2.6? This info should go into bugzilla)
It does not work without an initrd. The system as supplied by the Fedora project has an initrd. If people using labels customize their system they can provide an initrd. It's the way it works, it's not a bug.
Seems both those pieces of logic in the kernel could stand to be rewritten as a single subroutine
Labels are not in the kernel. They're in the initrd. The kernel doesn't know anything about it.
Sean.
Sean Estabrooks wrote:
On Sat, 03 Jan 2004 09:37:14 -0500 Nathan Bryant nbryant@optonline.net wrote:
root=/dev/sda6 wasn't working for me with 2.6.x, and I spent some time tearing my hair out before figuring out I needed to label things. This will cause headaches with upgrades to FC2 for people who originally installed redhat 6 and got to fedora through a series of upgrades (so they dont have labelled filesystems)
You are not forced to use labels. Specifying the correct drive/partition will work. Not sure what you were doing wrong in the example you mention.
And now apparently the root=LABEL=/ system may not work for some people--I assume it applies to those who aren't using initial ramdisks.(?) (Under what kernel versions, 2.4 2.6? This info should go into bugzilla)
It does not work without an initrd. The system as supplied by the Fedora project has an initrd. If people using labels customize their system they can provide an initrd. It's the way it works, it's not a bug.
Seems both those pieces of logic in the kernel could stand to be rewritten as a single subroutine
Labels are not in the kernel. They're in the initrd. The kernel doesn't know anything about it.
Baloney. have you read the linuxrc?
Sean.
-- fedora-test-list mailing list fedora-test-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-test-list
On Sat, 03 Jan 2004 10:12:31 -0500 Nathan Bryant nbryant@optonline.net wrote:
Labels are not in the kernel. They're in the initrd. The kernel doesn't know anything about it.
Baloney. have you read the linuxrc?
Ouch, i wonder if you will be as forthright in admitting your mistake. Look a little deeper before you jump to conclusions.
Good luck with that. Sean
On Sat, 2004-01-03 at 08:37, Nathan Bryant wrote:
This root= thing is actually at least 2 distinct buglets that are becoming an overall problem that should probably be bugzilla'd as "inconsistent support for root= option"
Actually it's already bugzilla'd via against mkinitrd as that is the problem. It has recently been happening against the recently supplied versions of mkinitrd in rawhide/development with the 2.6 kernels.
See the below bug..
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112623
-
alton bailey -
Bartolomeus Irwanto -
Klaasjan Brand -
Mike Chambers -
Nathan Bryant -
Sean Estabrooks