[FS#533] anon_mount 1 in fstab freezes boot in wrt3200acm
LEDE Bugs
lede-bugs at lists.infradead.org
Sun Feb 19 03:35:01 PST 2017
The following task has a new comment added:
FS#533 - anon_mount 1 in fstab freezes boot in wrt3200acm
User who did this - Hannu Nyman (hnyman)
----------
Really strange.
I flashed the other partition with LEDE master with kernel 4.9, and tested fstab anon_mount there. It seemed to work there, so I switched the router to boot again from the same 17.01 firmware that failed yesterday with anon_mount 1. And to my surprise anon_mount 1 works now with the 17.01 firmware, too. (The same firmware as yesterday, as I have not reflashed it)
The only difference is that now the other partition has been flashed once with LEDE, as yesterday there was still the Netgear OEM firmware in the other partition.
Now "/sbin/block mount" works also with anon_mount 1 active, and shows a second ubi partition. Unlike yesterday:
17.01.0-rc2, r3131-42f3c1f
root at LEDE:~# /sbin/block mount
block: /dev/ubiblock0_0 is already mounted on /rom
block: /dev/ubi0_1 is already mounted on /overlay
block: /dev/ubi1_0 is already mounted on /mnt/ubi1_0
root at LEDE:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 2560 2560 0 100% /rom
tmpfs 256812 592 256220 0% /tmp
/dev/ubi0_1 58604 5512 50064 10% /overlay
overlayfs:/overlay 58604 5512 50064 10% /
ubi1:syscfg 71908 476 67724 1% /tmp/syscfg
tmpfs 512 0 512 0% /dev
/dev/ubi1_0 71908 476 67724 1% /mnt/ubi1_0
It looks like the syscfg partition gets now mounted both as /tmp/syscfg and /mnt/ubi1_0
So, just a hypothesis, but possibly /sbin/block misdetects something when it scans the partitions, if the other partition contains the Netgear OEM firmware. Possibly some naming or formatting is slightly different?
----------
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=533#comment1878
More information about the lede-bugs
mailing list