[SOLVED] Boot-Up err Msg. after kitten tap danced on keyboard
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Boot-Up err Msg. after kitten tap danced on keyboard
Our kitten did a lightening tap dance on the computer keyboard and 'hung it up'.
Doing a cold Re-boot, I am presented with:
mount: mounting /dev on /root/dev failed: no such file
mount: mounting /sys on /root/sys failed: no such file
" " " /proc on /root/proc " " "
target file system doesn't have /sbin/init
no init found
###The cursor follows this:
##The init=bootarg, didn't help. I am not familiar with the shell command sequences during boot-up. Any Help would be appreciated.
Scroll down to "Method 3 - CHROOT" which is a generic way to fix this from any linux live CD. Basically, what you do is mount your hard drive partitions, then use chroot to make the live CD think it is working from the hard disk files. From there, you just repair grub with update-grub and or grub-install. If you have to go the "grub-install" route, make sure you have the proper partition name mounted or you'll install grub somewhere else...
It looked too easy and I shouldn't have shouted victory so quickly.
I am on the live CD (on my other computer), have a root shell and my target partition is sda1, which I mounted as instructed.
When I entered
grub install --root-directory=/mnt /dev/sda1
/bin/shell: grub-install: not found
similarly with update-grub.
I can change directory and looked in /sbin but it was not found.
apropos the kitten dance: I was not logged in as root. I don't believe the password is that vulnerable; according to my wife,, the kitten sprung onto the keyboard while she was downloading a google page?
Thanks for all your interest.
Thank you everybody!
The problem is solved. So far, no harm done. fsck showed no disk errors. I played around with various options on the root menu of the live cd and somehow managed to get it to re-install grub.
TobiSGD, your comments are taken into consideration.
In retrospect, though solved, my experience with this problem and the solution, will prove to be useless for anyone else reading this.
a. I have no idea of just what the problem was and no chance of finding out. What combination of keys the kitten's dance across the keyboard entered, at a time when the Firefox was downloading a file-(is this even relative?) has to remain unknown.
b. every try to cold boot the Ubuntu system up, ended with a boot into the normal boot sequence, at the command line, plus Err. Msg's. I assumed the problem was a faulty or absent grub installer because that was what the Err Msg.s projected. However, in my very limited experience, Err. Msg.s are frequently erroneous. However, I did try to re-install the Grub from the command line but the Err. Msg. stated File unknown, no such file.
c. Going over the procedures outlined on Linux Questions, I came upon this:
" 7. You may find you get a repeated "error: Cannot open /boot/grub/device.map" message. If this happens try rebooting. The UUID method may actually work but throws an error message falsely. Using the label name does not seem to evoke the same repeated error message. "
This is possibly what transpired after fooling around with the "MENU" options, such as fsck, etc. Reboot is a Menu option and I chose it blindly and voila!, up came the ubuntu splash page.
Thanks for the tip, I have done so and all is right.