Thanks Dan -- What this shows is that user data resides in partition 10,
and the installation routine (after flashing) assumes user data (UDA) is
on partition 9, where it resides on devices without 3G support.
I've added a task to track this bug against the appropriate source
package.
James -- Once you receive your new device this will also impact you as
well.
--chris
** Also affects: ac100-tarball-installer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ac100-tarball-installer (Ubuntu)
Status: New => Confirmed
** Changed in: ac100-tarball-installer (Ubuntu)
Importance: Undecided => High
** Changed in: ac100-tarball-installer (Ubuntu)
Assignee: (unassigned) => Oliver Grawert (ogra)
** Also affects: ac100-tarball-installer (Ubuntu Raring)
Importance: High
Assignee: Oliver Grawert (ogra)
Status: Confirmed
** Changed in: ubuntu-nexus7
Status: Invalid => Confirmed
** Description changed:
- 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.
+ Description: Nexus7 variants without 3G support map their user data
+ partition (UDA) to mmcblk0p9, where variants with 3G support map UDA to
+ mmcblk0p10
+
+
=======================================================================================
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079729
Title:
Ubuntu uninstallable on 32GB 3G Nexus 7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1079729/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
