The writable partition is corrupted using the latest ubuntu-image (0.8)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
Fix Released
|
Medium
|
Steve Langasek |
Bug Description
I installed the latest ubuntu-image from git version, and the issue can be reproduced through following steps:
$ ubuntu-image --version
ubuntu-image 0.8+17.04ubuntu1
$ more pi3.model
type: model
authority-id: 9anEFsr3zJAqJ3z
series: 16
brand-id: 9anEFsr3zJAqJ3z
model: pi3
architecture: armhf
gadget: pi3
kernel: pi2-kernel
timestamp: 2016-09-
sign-key-sha3-384: RfSxuO7R8OT_
AcLBXAQAAQoABgU
7rv04iR7JZ8mATv
z/eZphyhDscesDO
HXSfYYAzWr2ONww
usnwA1qBa8VH61g
VjSqcRRvBPHoP/
FBvocHR5SvTfjfZ
IXYCmUuIeUW2bQu
0fYIdlRFYny7w5e
FMtVmp4bXe7jU2n
$ sudo ubuntu-image -c beta -o pi3-test-new.img pi3.model
[sudo] password for u:
5.83 MB / 5.83 MB [======
Fetching ubuntu-core
63.42 MB / 63.42 MB [======
Fetching pi2-kernel
85.44 MB / 85.44 MB [======
Fetching pi3
5.83 MB / 5.83 MB [======
$ sudo kpartx -av pi3-test-new.img
add map loop2p1 (252:0): 0 262144 linear 7:2 2048
add map loop2p2 (252:1): 0 948224 linear 7:2 264192
$sudo mount /dev/mapper/loop2p2 mnt/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
$ dmesg|tail -n 2
[82470.253410] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: (null)
[82493.633046] EXT4-fs (dm-1): bad geometry: block count 118616 exceeds size of device (118528 blocks)
But if I use the snap version (0.5+mvo13), mounting the second partition is OK.
Changed in ubuntu-image: | |
milestone: | none → 0.9 |
Changed in ubuntu-image: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-image: | |
status: | Fix Committed → Fix Released |
summary: |
- The writable partition is corrupted using the latest ubuntu-image(0.8 ) + The writable partition is corrupted using the latest ubuntu-image (0.8) |
Looks like the partition table is incorrect.
The partition table of the created image is:
Device Boot Start End Sectors Size Id Type
pi3-test.img1 * 2048 264191 262144 128M c W95 FAT32 (LBA)
pi3-test.img2 264192 1210367 946176 462M 83 Linux
After I re-create the 2nd partition to be like this, I can then mount it:
Device Boot Start End Sectors Size Id Type
pi3-test.img1 * 2048 264191 262144 128M c W95 FAT32 (LBA)
pi3-test.img2 264192 1212171 947980 462.9M 83 Linux