[vivid] emulator fails to mount root partition (Invalid argument), landing in busybox

Bug #1413271 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
android-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

These days the emulator fails to boot:

$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel devel
$ ubuntu-emulator run devel
[...]
Begin: Running /scripts/local-premount ... [ 0.190059] mmc0: new SDHC card at address e118
done.
[ 0.195316] mmcblk0: mmc0:e118 SU02G 3.72 GiB
[ 0.195983] mmcblk0: unknown partition table
[ 0.270180] initrd: checking filesystem integrity for the userdata partition
[ 0.271256] EXT4-fs (mmcblk0): couldn't mount as ext3 due to feature incompatibilities
[ 0.273543] EXT4-fs (mmcblk0): couldn't mount as ext2 due to feature incompatibilities
[ 0.284652] EXT4-fs (mmcblk0): bad geometry: block count 976562 exceeds size of device (976512 blocks)
[ 0.333267] yaffs: dev is 187695104 name is "mmcblk0" rw
[ 0.333330] yaffs: passed flags "errors=remount-ro"
[ 0.333359] yaffs: Bad mount option "errors=remount-ro"
[ 0.343222] yaffs: dev is 187695104 name is "mmcblk0" rw
[ 0.343271] yaffs: passed flags "errors=remount-ro"
[ 0.343300] yaffs: Bad mount option "errors=remount-ro"
mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument
umount: can't umount /tmpmnt: Invalid argument
[ 0.370651] mmcblk0: unknown partition table
[ 0.375414] initrd: checking filesystem for userdata took (including e2fsck) 0 seconds
[ 0.375497] initrd: mounting /dev/mmcblk0
[ 0.464983] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
[ 0.465039] EXT4-fs (mmcblk0): couldn't mount as ext3 due to feature incompatibilities
[ 0.473248] EXT4-fs (mmcblk0): couldn't mount as ext2 due to feature incompatibilities
[ 0.483957] EXT4-fs (mmcblk0): bad geometry: block count 976562 exceeds size of device (976512 blocks)
[ 0.533049] yaffs: dev is 187695104 name is "mmcblk0" rw
[ 0.533113] yaffs: passed flags "discard,data=journal"
[ 0.533140] yaffs: Bad mount option "discard"
[ 0.543012] yaffs: dev is 187695104 name is "mmcblk0" rw
[ 0.543059] yaffs: passed flags "discard,data=journal"
[ 0.543086] yaffs: Bad mount option "discard"
mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument
[ 0.554010] initrd: boot mode: ubuntu
[ 0.554108] initrd: Couldn't find a system partition.
Couldn't find a system partition. Spawning adbd ...
[ 0.558145] initrd: enabling USB debugging
/scripts/panic/adbd: line 22: can't create /sys/class/android_usb/android0/idVendor: nonexistent directory
/scripts/panic/adbd: line 23: can't create /sys/class/android_usb/android0/idProduct: nonexistent directory
/scripts/panic/adbd: line 24: can't create /sys/class/android_usb/android0/functions: nonexistent directory
/scripts/panic/adbd: line 25: can't create /sys/class/android_usb/android0/enable: nonexistent directory
[ 0.559371] initrd: starting adbd for USB debugging
[ 0.560620] adbd[168]: segfault at c ip 0804cb29 sp bf98e2d8 error 4 in adbd[8048000+20000]
Segmentation fault

BusyBox v1.22.1 (Ubuntu 1:1.22.0-9ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

So the primary problem seems to be

  mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument

The adbd crash also seems important, but secondary.

Revision history for this message
Martin Pitt (pitti) wrote :

$ ubuntu-emulator list
devel ubuntu=20141201,device=20141119,custom=20141201,version=1

I also just checked with devel-proposed, same problem.

summary: - [vivid] emulator fails to find a root partition, landing in busybox
+ [vivid] emulator fails to mount root partition (Invalid argument),
+ landing in busybox
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.