Fedora 8 boot failure. "switchroot: mount failed..."
FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fedora 8 boot failure. "switchroot: mount failed..."
After installing XP on a system (In it's own partition, naturally.) and having a period without Linux, I reinstalled GRUB and tried to boot Fedora.
Quote:
mkrootdev: expected fs options
mount: missing mount point
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
switchroot: mount failed: No such file or directory
In the belief that I'd b0rked the Fedora install, I reinstalled.
Unfortunately, I get the same message every single time I try to boot.
could someone please help me fix it? I'm suffering from GNU/Linux-deprivation...
I have seen the same errors you are experiencing when the initrd image is not correct. This could happen as a result of a change in partition or drive information. Here is one way to fix it.
1) Boot using install DVD or rescue CD in rescue mode. When it asks if you should find Fedora installations click on continue so it mounts the installation to /mnt/sysimage.
2) At the command line chroot to /mnt/sysimage.
3) cd /boot, then determine kernel version using ls vmlinuz*
4) mv initrd-2.6.x.x-x.fc8.img initrd-2.6.x.x-x.fc8.old
5) mkinitrd initrd-2.6.x.x-x.fc8.img 2.6.x.x-x.fc8
6) exit, exit and it should reboot.
replace all above x.x.x-x with the latest kernel version-release you have installed.
"An error occured trying to mount some or all of your system, some of it may be located under /mnt/sysimage.
Press return to get a shell. The system will reboot automatically when you exit from the shell."
In /mnt/sysimage there is only sys, proc and something else, but I can't remember what it is right now.
I mounted /dev/sda2 on /mnt/system, and chrooted into that. However, as sys was elsewhere (/mnt/sysimage) mkinitrd failed with:
"error opening /sys/block: no such file or directory."
That is a bummer... As you have figured out, the / and several virtual filesystems need to be mounted in order to use mkinitrd. Rescue mode can usually handle that without much trouble. I don't know the particulars behind mounting /proc, /sys, and any others. If we knew that we could do it all manually since you were able to mount /dev/sda2. I'd fire up rescue mode on my installation, but I had a CPU take a dive and am running off a temporary setup with no CD/DVD drives. Sorry I can't be much help at the moment. If that changes or I get other ideas I'll post them.
I really believe making a new initrd image will solve the problems you are having. The other solution, if you don't have anything major to lose, would be to reinstall Fedora.
I re-installed again, this time the home partition is on the same disc as the OS.
This has booted perfectly *knocks on wood* and I have come to the conclusion that either I did the setup wrong OR that the previous configurations depended on /home being on sdb1.
The drive that used to be sdb has failed (possibly one of a dodgy batch (it's only 2 years old.)), taking /home with it. I had tried to reconfigure around this, but failed.
Therefore, this case is closed! I have Fedora again!
Fedora 8? Are you kidding? It's a 3-year-old release! It is about as EOL as Ubuntu Feisty. Try upgrading to at least F13 or many security flaws that have occurred especially with Red Hat-based Linux distributions (see this for more information) will easily catch up to you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.