[SOLVED] Target filesystem doesn't have /sbin/init - ubuntu
If you try and boot Ubuntu and get this error,
Killed
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
(and then something about initramfs)
I think you are in a big trouble. But don’t worry, you can fix it easily. Follow our step by step guide to get rid of this headache. First of all download required files and burn a live CD/DVD or USB stick to boot your system and then download boot info script to get information about your drive and finally run the “e2fsck” command.
Download Required Files:
- Download ubuntu for booting your system
- Download unetbootin to create a bootable pendrive
- Download boot info script
Or, you can learn here how to create bootable USB stick on different platforms:
- Ubuntu
- Windows
- Mac OSX
If you do manage to get it booted, please do the following so we can get a better idea of what is going on. Once the desktop loads come back here and do the following:
1. Download the boot info script from here which is in a zipped file.
2. Once downloaded, unzip the contents by using right-click Extract here.
3. Open the extracted folder and copy the script to the desktop.
4. Open a terminal and run the following command.
$ sudo bash ~/Desktop/bootinfoscriptRESULT:
Boot Info Script 0.61 [1 April 2012]
"gawk" could not be found, using "busybox awk" instead.This may lead to unreliable results.
Identifying MBRs...Computing Partition Table of /dev/sda...Computing Partition Table of /dev/sdb...Searching sda1 for information...Searching sda2 for information...Searching sda5 for information...Searching sdb1 for information...
Finished. The results are in the file "RESULTS.txt"located in "/home/ubuntu/Desktop/".Open your “RESULTS.txt” file and check for errors. you will get a similar file like what i got here.
Boot Info Script 0.60 from 17 May 2011
============================= Boot Info Summary: ===============================
=> Grub2 (v1.97-1.98) is installed in the MBR of /dev/sda and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks in partition 1 for /boot/grub. => Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ext4 Boot sector type: - Boot sector info: Mounting failed: mount: unknown filesystem type 'ext4'
sda2: __________________________________________________________________________
File system: Extended Partition Boot sector type: - Boot sector info:
sda5: __________________________________________________________________________
File system: swap Boot sector type: - Boot sector info:
sdb1: __________________________________________________________________________
File system: vfat Boot sector type: SYSLINUX 3.71 2008-07-31 Boot sector info: Syslinux looks at sector 540800 of /dev/sdb1 for its second stage. No errors found in the Boot Parameter Block. Operating System: Boot files: /boot/syslinux/syslinux.cfg /boot/syslinux/ldlinux.sys
sdb2: __________________________________________________________________________
File system: Extended Partition Boot sector type: - Boot sector info:
sdb5: __________________________________________________________________________
File system: swap Boot sector type: - Boot sector info:
sdh: ___________________________________________________________________________
File system: vfat Boot sector type: FAT16 Boot sector info: According to the info in the boot sector, sdh has 1415168 sectors.. But according to the info from the partition table, it has 31506432 sectors. Operating System: Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 500.1 GB, 500107862016 bytes255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk identifier: 0x00084d8b
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 973,848,575 973,846,528 83 Linux/dev/sda2 973,850,622 976,773,119 2,922,498 5 Extended/dev/sda5 973,850,624 976,773,119 2,922,496 82 Linux swap / Solaris
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 4063 MB, 4063232000 bytes125 heads, 62 sectors/track, 1024 cylinders, total 7936000 sectorsUnits = sectors of 1 * 512 = 512 bytesDisk identifier: 0x000e29e1
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 2,048 7,473,151 7,471,104 b W95 FAT32/dev/sdb2 7,475,198 7,933,951 458,754 5 Extended/dev/sdb5 7,475,200 7,933,951 458,752 82 Linux swap / Solaris
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 249cd791-45d0-45f8-9d8b-65bac7e8d70f ext4/dev/sda5 c3f67a6e-3291-496d-a4a3-1b8a45e29062 swap/dev/sdb1 1CEC-1AD6 vfat/dev/sdb5 f49dfc99-2007-4c7a-a0f4-6561b2b662e2 swap/dev/sdh 8C84-649B vfat
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sdb1 /mnt/sdb1 vfat (rw,noatime,quiet,umask=0,check=s,shortname=mixed)/dev/sdg /mnt/sdg vfat (rw)/dev/sdh /mnt/sdh vfat (rw)
======================= sdb1/boot/syslinux/syslinux.cfg: =======================
--------------------------------------------------------------------------------INCLUDE /boot/slax.cfg--------------------------------------------------------------------------------
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
?? = ?? boot/initrd.gz ?? = ?? boot/vmlinuz
================= sdb1: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
?? = ?? boot/syslinux/ldlinux.sys ?? = ?? boot/syslinux/menu.c32 ?? = ?? boot/syslinux/syslinux.cfg
============== sdb1: Version of COM32(R) files used by Syslinux: ===============
boot/syslinux/menu.c32 : COM32R module (v4.xx)
========= Devices which don't seem to have a corresponding hard drive: =========
hda sdc sdd sde sdf
=============================== StdErr Messages: ===============================
File descriptor 11 (socket:[12153]) leaked on lvscan invocation. Parent PID 8993: /bin/bashmdadm: No arrays found in config fileThere is possible damage to the file-system which is most likely why those errors appeared. You can use the ubuntu live boot USB to try and fix this by running the following command:
$ sudo e2fsck -f -y -v /dev/sda1RESULT:
e2fsck 1.42 (29-Nov-2011)/dev/sda1: recovering journalClearing orphaned inode 24379404 (uid=121, gid=132, mode=0100600, size=0)Clearing orphaned inode 24379405 (uid=121, gid=132, mode=0100600, size=0)Clearing orphaned inode 24379398 (uid=0, gid=0, mode=0100644, size=0)Clearing orphaned inode 24379403 (uid=117, gid=126, mode=0100600, size=0)Clearing orphaned inode 24379402 (uid=117, gid=126, mode=0100600, size=0)Clearing orphaned inode 24379401 (uid=117, gid=126, mode=0100600, size=0)Clearing orphaned inode 24379400 (uid=117, gid=126, mode=0100600, size=0)Clearing orphaned inode 24379399 (uid=117, gid=126, mode=0100600, size=0)Pass 1: Checking inodes, blocks, and sizesPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationFree blocks count wrong (104783285, counted=104783276).Fix? yes
Free inodes count wrong (29656150, counted=29656243).Fix? yes
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
744269 inodes used (2.45%) 12650 non-contiguous files (1.7%) 361 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 697224/673/316791636 blocks used (13.81%) 0 bad blocks 3 large files
655942 regular files 26961 directories 58 character device files 25 block device files 2 fifos 16 links 61238 symbolic links (46242 fast symbolic links) 34 sockets-------- 744276 filesOnce the command completes, and assuming there are no errors, reboot the computer taking out the Live CD/USB. I hope it will work for you.