Ubuntu – Can’t boot Wubi after upgrading to 14.04 from 12.04: “Target filesystem doesn’t have requested /sbin/init”

12.0414.04bootupgradewubi

So I decided to upgrade to 14.04 from 12.04 on my Wubi installation, using update-manager -d, but I can no longer boot into Ubuntu. When I try to, I see the message mount:mounting…"etc, then "Target filesystem doesn't have requested /sbin/init". Does anyone know how to solve this?

mount: mounting /dev/loop0 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 requested /sbin/init.
No init found. Try passing init= bootarg.

Best Answer

From https://answers.launchpad.net/ubuntu/+question/247265

Steven, I've found a solution that works, that is, if you haven't tried to reinstall yet:

If you can find your boot commands, find the line that says:

linux /boot/vmlinuz-3.13.0-24-generic root=UUID=D014E45... etc...

Change "ro rootflags= sync" to "rw rootflags=sync"

That's it. Just that one character. Nothing else. Worked for me, hopefully it does the same for you. Here's hoping.

and

Daniel - thanks for posting that solution, my dad's laptop was suffering from this, and I managed to get a remote session on it and repair it for him thanks to your post. He's very pleased :)

For what it's worth, I also updated the grub regeneration files in /etc/grub.d/10_linux to ensure that it remains set to "rw" after a kernel update. Just replace this line:
    linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}
with
    linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} rw ${args}
In summary, to recover, I did (from memory):

boot from xubuntu cd (Try ubuntu without installing)

open terminal, locate root volume on the windows drive, mount it with:

sudo -i

mkdir /mnt/recovery

mount -o loop /media/xubuntu/Data/ubuntu/disks/root.disk /mnt/recovery

apt-get install vim

vim /mnt/recovery/boot/grub/grub.cfg  # set "ro" flags to "rw" as per Daniel's comment (#8 above)

vim /mnt/recovery/etc/grub.d/10_linux  # change "ro" to "rw" as above

reboot

Related Solutions

Target Filesystem Error – Fix ‘Target Filesystem Doesn’t Have Requested /sbin/init’ Error

Quoting:

This morning, a friend came to me with his laptop that won't boot. At every boot attempt, his Ubuntu 10.04 Lucid Lynx system outputs the following error messages:
mount: mounting /dev/disk/by-uuid/***************************** on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
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 file system doesn't have /sbin/init
No init found. Try passing init= bootarg

Busybox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs) _
Booting into "Recovery Mode" as well as choosing the other kernels listed in grub didn't help at all.

Solution:
Boot from the Ubuntu Live CD;

Open/Run Terminal;
Type: sudo fdisk -l (to get the device name) then press ENTER;
Disk /dev/sda: 250.1 GB, 250059350016 bytes 
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: **********

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30238 242886703+ 83 Linux
/dev/sda2 30239 30401 1309297+ 5 Extended
/dev/sda5 30239 30401 1309266 82 Linux swap / Solaris
The device name for my friend's system based on the above: /dev/sda1
Type: sudo fsck /dev/sda1 then press ENTER;

Restart the system and boot normally.

Ubuntu – A TPM error (7) occurred attempting to read a pcr value

First of all TPM is:

Trusted Platform Module (TPM) is an international standard for a secure cryptoprocessor, which is a dedicated microprocessor designed to secure hardware by integrating cryptographic keys into devices.

In practice a TPM can be used for various different security applications such as secure boot and key storage.

TPM is naturally supported only on devices that have TPM hardware support. If your hardware has TPM support but it is not showing up, it might need to be enabled in the BIOS settings.

1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.

2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:

echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf

Where the command tee -a will append the echoed line (blacklist tpm_tis) into the end of /etc/modprobe.d/tpm_tis.conf or will create the file if it's doesn't exists.

3. Sources and other solutions:

Best Answer

Related Solutions

Target Filesystem Error – Fix ‘Target Filesystem Doesn’t Have Requested /sbin/init’ Error

Ubuntu – A TPM error (7) occurred attempting to read a pcr value

Related Question