Fedora - InstallationThis forum is for the discussion of installation issues with Fedora.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
i am having the same problem with FC4...im installing it on a server (2 AMD 250's, 3 Gigs ECC Ram, 2 Sata II 67GB harddrive (hardware RAID 1), Tyan Mobo)
I have been looking in other forums and they say its because FC4 installer "forgets" to name the mount points...and that if you partition manually it will fix it...
in my case, i can do a full install then hit reboot. everything boots fine..but the next time i restart it (no matter how i set up the partitions) i get the following:
mkrootdev: label / not found
mount: error 2 mounting ext3
ERROR opening /dev/console!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!
kinda looks like my problem is a little bit different than yours?
Its funny too..i installed it from the same disk and had it running for atleast a couple of days..i could shut it down or restart or whatever...then i let it sit for a week...and now this!
Can anybody help?
I having the same problem, and it looks like alot of other people
are as well. I am really in a fix because I can't use linux at
all since there are no other bootable kernels after the installation of FC4. Have you tried to go through manual partioning? I, as yet, have not. If the root=LABEL=/ is replaced by root=0x804 or root=/dev/sda4 it still doesn't work, and I am sure that this is the right device.
I found that the problem with not finding the root device and getting the panic is fixed by doing the FC4 install as an INSTALL and not an UPGRADE.
I found that when you get to the part where you are using Disk Druid, you label the root device (in my case /dev/sda4) as "/".
It believe the partition was labeled this in the past (FC2) so the upgrade somehow seems to have stripped the labels off of the devices. When I did this the root=LABEL=/ line on the kernel line will cause the booter to find it. I had no success by setting root to anything else before.