mount: mounting /dev/disk/by-uuid/267... on /root failed Invalid argument
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
No init found. Try passing init = bootarg.
BusyBox v1.10.2 (Ubuntu 1:1.10.2-2ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)_
Monday, September 6. 2010
Target filesystem doesn't have /sbin/init
So I woke up this morning, and as always booted up my laptop while i was still half-awake and willing myself back into reality. Once I was fully awake, I saw to my surprise that the laptop hadn't booted up fully and was displaying a message similar to this one, (I didn't copy my message down word for word, to replicate here, but this is a similar one from a forum posting at ubuntuforums.org)
Needless to say, a bit of research online showed like a good dozen ways to fix this and some being more complicated than others. Some posts even suggested recompiling the kernel! Thinking that the best way was to start by the simplest solutions and making my way up, i decided to run a filesystem check first.
I ran it in two ways, once off the options of a Ubuntu 10.04 CD. So instead of choosing to install or test the Ubuntu system, there is another option to check the filesystem, test the memory or boot from first hard disk. This file system check came back clean with no errors, and upon a reboot the problem came back as is. Thus, problem not solved!
The second attempt was to run Ubuntu off of the CD (don't install it, just run the OS) and then go into the terminal window and run fsck. For those that aren't familiar with that command, here is a brief summary,
So, for me since the boot drive is the first drive, and the first partition, i had to run fsck on /dev/sda1 (FYI, sd denotes that it is a SCSI or SATA drive, the 'a' shows that it is in the first position, and the 1 shows that we are talking about first partition). Upon running that command (sudo fsck /dev/sda1), it came back with one error that it corrected. I crossed my fingers and did a reboot, and voila my Ubuntu 10.04 LTS install was back to normal!
Why did I have that problem in the first place remains unknown. Since no new hardware or software was installed on this machine. I'll give that up to 'freak of nature', unless it happens again! For all those that had problems similar to mine, hopefully the fsck command helps you out as well!
I ran it in two ways, once off the options of a Ubuntu 10.04 CD. So instead of choosing to install or test the Ubuntu system, there is another option to check the filesystem, test the memory or boot from first hard disk. This file system check came back clean with no errors, and upon a reboot the problem came back as is. Thus, problem not solved!
The second attempt was to run Ubuntu off of the CD (don't install it, just run the OS) and then go into the terminal window and run fsck. For those that aren't familiar with that command, here is a brief summary,
fsck is used to check and optionally repair one or more Linux file systems. It can be run on a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).
So, for me since the boot drive is the first drive, and the first partition, i had to run fsck on /dev/sda1 (FYI, sd denotes that it is a SCSI or SATA drive, the 'a' shows that it is in the first position, and the 1 shows that we are talking about first partition). Upon running that command (sudo fsck /dev/sda1), it came back with one error that it corrected. I crossed my fingers and did a reboot, and voila my Ubuntu 10.04 LTS install was back to normal!
Why did I have that problem in the first place remains unknown. Since no new hardware or software was installed on this machine. I'll give that up to 'freak of nature', unless it happens again! For all those that had problems similar to mine, hopefully the fsck command helps you out as well!
Trackbacks
Trackback specific URI for this entry
No Trackbacks
