Activity log for bug #1079729

Date Who What changed Old value New value Message
2012-11-16 15:22:43 James Brierley bug added bug
2012-11-16 17:07:42 Chris Van Hoof ubuntu-nexus7: importance Undecided High
2012-11-16 17:07:45 Chris Van Hoof ubuntu-nexus7: status New In Progress
2012-11-16 17:07:49 Chris Van Hoof ubuntu-nexus7: assignee Chris Van Hoof (vanhoof)
2012-11-16 22:07:13 James Brierley ubuntu-nexus7: status In Progress Invalid
2012-11-20 18:28:01 Chris Van Hoof bug task added ac100-tarball-installer (Ubuntu)
2012-11-20 18:28:34 Chris Van Hoof ac100-tarball-installer (Ubuntu): status New Confirmed
2012-11-20 18:28:37 Chris Van Hoof ac100-tarball-installer (Ubuntu): importance Undecided High
2012-11-20 18:28:44 Chris Van Hoof ac100-tarball-installer (Ubuntu): assignee Oliver Grawert (ogra)
2012-11-20 18:28:57 Chris Van Hoof nominated for series Ubuntu Raring
2012-11-20 18:28:57 Chris Van Hoof bug task added ac100-tarball-installer (Ubuntu Raring)
2012-11-20 18:32:14 Chris Van Hoof ubuntu-nexus7: status Invalid Confirmed
2012-11-20 18:32:23 Chris Van Hoof bug added subscriber Chris Van Hoof
2012-11-20 18:34:15 Chris Van Hoof description 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. 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.
2012-11-22 14:12:59 Launchpad Janitor branch linked lp:ubuntu/raring-proposed/ac100-tarball-installer
2012-11-22 14:26:13 Launchpad Janitor ac100-tarball-installer (Ubuntu Raring): status Confirmed Fix Released
2012-11-23 20:42:02 Oliver Grawert ac100-tarball-installer (Ubuntu Raring): status Fix Released In Progress
2012-11-23 21:24:19 Launchpad Janitor ac100-tarball-installer (Ubuntu Raring): status In Progress Fix Released
2012-12-10 18:29:02 Chris Van Hoof ubuntu-nexus7: status Confirmed Fix Released