Comment 0 for bug 1079729

Revision history for this message
James Brierley (jmb8710) wrote :

Since opening my new Nexus 7 this morning I have been trying without success to install Ubuntu. I have tried both the 32GB and 16GB images with the same result.

I have been just as unsuccessful in taking a picture of the error messages that I receive that isn't blurry and unreadable, so I will do my best to copy them out:

NTFS signature is missing.
Failed to mount /dev/mmcblk0p9: Invalid argument
The device '/dev/mmcblk0p9' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way round?
mount: mounting /dev/mmcblk0p9 on /root failed: Invalid argument
mount: mounting /dev/mmcblk0p9 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 required /sbin/init.
No init found. Try passing init= bootarg.

I am then dropped at an (of course unusable) BusyBox shell.

I bought my N7 specifically to help the developers test Ubuntu on tablets and am disappointed that I am so far unable to install. Is this a bug, or have I overlooked something?

As a side note, the Nexus 7 installer displayed strange behavior such as failing to verify the checksum on the 16GB image (despite me verifying the images as undamaged with sha256sum) and sticking on erasing the boot partition. Both problems required a reboot.