No root device found; exiting to /bin/sh
I installed Kile 1.6.3 (latest version) from source code in Suse 9.1 Pro. After that while rebooting, I got the following error. How to overcome this?
Waiting for device /dev/304 to appear: .....not found -- device nodes:
by-id by-path console fb0 fd0 hda hda1 hda2 hda3 hda4 loop0 loop1 loop2
loop3 loop4 loop5 loop6 loop7 md0 null ram ram0 ram1 ram10 ram11 ram12
ram13 ram14 ram15 ram2 ram3 ram4 ram5 ram6 ram7 ram8 ram9 ramdisk shm
tty1 tty2 zero No root device found; exiting to /bin/sh
I tried to use the option "boot installed system" from Suse 9.1 Installation CD. It worked, but while booting I have seen some errors, but I couldn't copy those as it runs fast.
Tried to repair installed system using the Suse 9.1 Installation CD, even thou failed.
Thanks in Advance,
Have a nice weekend.
I have exactly the same problem (in my case is /dev/306). I just updated online and everything was ok until I restarted. Then I got the same error. I've tried to repair and boot from the Suse 9.1 Installation CD but it hangs.
Somebody knows how to repair this mess?:cry:
Thanks!!! (and sorry for my English, if you forgive me then I will forgive you when you don't speak a perfect Spanish :D :D :D ).
It is not reiser, it is an update or mkinitrd
Same problem here
I reinstalled to ext3 to avoid the reiser problem
I also did not install a new kernel, although I did install other stuff
I ran mkinitrd to have bootsplash (for some reason it didn't come up)
that did it: "no root device found: exiting to /bin/sh"
please mail solutions to firstname.lastname@example.org
May be this helps you..?
You can resume booting if you enter "exit".
After this, install the older version of mkinitrd (the one from the cd or ftp).
make a new initrd.
Please leave a message if this helps.
I've found a possible solution just 5 minutes ago and, when I enter to post that solution, I read your post, Natron:D .
I think you are right. The problem may be mkinitrd. When the system hangs just press Ctrl+D and it will continue booting. If you tried to repair or reinstall but the system hanged when rebooting, it's possible that the installation continues. In my case, it hanged again after the installation finished but rebooting again and pressing Ctrl+D everything was ok. Now it's too late so I will continue tomorrow solving this problem. I will install the older version of mkinitrd as Natron says. Then I'll post the results.
Look this page:
Thanks a lot Natron. I'll tell you if thats the solution.:)
Thanks a lot BeOiR and Natron. But it's late. Already i have reinstalled from Scratch. As a newbie to Linux, I don't know much to solve this and I have no patience to wait for some days :D :D
new mkinitrd update cause boot error
I got same problem like you guys, after follow Autoupdate. After reboot error occur and stop me from going any further, I have to do 'CTRL+D' to continue bypass booting sequence/ it's really annoying.
After go through Internet and forum search and I found result.
Problem are not kernel update, it actually mkinitrd update that cause problem.
By follow fschmidt solution, i have solve boot problem without reinstall everything over again :D
|All times are GMT -5. The time now is 05:47 AM.|