Omega2+ Upgrade from kernel v3 to v4 breaks external overlay
-
Omega2+ was booting fine with Kernel V3 off of an miroSD overlay. I recently upgraded to kernel 4.14 via the oupgrade command. Now the V4.14 kernel rejects mounting the overlay and /dev/mtdblock6 is mounted instead.
~# block info /dev/mtdblock5
/dev/mtdblock5: UUID="2017e343-8e62014c-a4572a07-d0744c88" VERSION="4.0" MOUNT="/rom" TYPE="squashfs"~# block info
/dev/mtdblock6: MOUNT="/overlay" TYPE="jffs2"
/dev/mtdblock7: TYPE="jffs2"
/dev/mmcblk0p1: UUID="827b1b64-091e-48c2-a40d-3c1a46286c10" VERSION="1" TYPE="swap"
/dev/mmcblk0p2: UUID="6af1b15d-c02d-4ddc-a162-2cf2052d3876" VERSION="1.0" TYPE="ext4"~# uci show fstab
fstab.@global[0]=global
fstab.@global[0].anon_swap='0'
fstab.@global[0].anon_mount='0'
fstab.@global[0].auto_swap='1'
fstab.@global[0].auto_mount='1'
fstab.@global[0].delay_root='5'
fstab.@global[0].check_fs='0'
fstab.@swap[0]=swap
fstab.@swap[0].uuid='827b1b64-091e-48c2-a40d-3c1a46286c10'
fstab.@swap[0].enabled='1'
fstab.@mount[0]=mount
fstab.@mount[0].target='/overlay'
fstab.@mount[0].uuid='6af1b15d-c02d-4ddc-a162-2cf2052d3876'
fstab.@mount[0].enabled='1'~# dmesg | grep block
[ 12.319013] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 12.374230] block: extroot: UUID mismatch (root: 2017e343-8e62014c-a4572a07-d0744c88, overlay: 6af1b15d-c02d-4ddc-a162-2cf2052d3876
[ 13.415122] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 13.467749] block: extroot: UUID mismatch (root: 2017e343-8e62014c-a4572a07-d0744c88, overlay: 6af1b15d-c02d-4ddc-a162-2cf2052d3876
[ 49.576505] br-wlan: port 1(ra0) entered blocking state
[ 49.592429] br-wlan: port 1(ra0) entered blocking statesomething is missing from the wiki to fix this bug. The LEDE forums say to delete /mnt/mmcblockp2/etc/.extroot-uuid, (contents: 2017e343-8e62014c-a4572a07-d0744c88) but this file reappears every time the omega reboots.
the swap partition is mounted.
-
It wasn't till i consoled in on the ttyS0 pins, and monitored the boot process before figured the issue out.
The SDcard was partitioned and restored from from a backup on a Linux machine. For some reason uboot was misreading the size of SD overlay partition when booting. Wiping and reformatting the partition [with the omega2+], and rebuilding the SD /overlay partition from scratch, seems to have fixed the boot problem.
-
This post is deleted!