techsolx:

Same issue, a few differences:

Fully functional Chaos Calmer 15.05.1 on a Linksys 1900v2. Update to lede-17.01.4-mvebu-linksys-wrt1900acv2-squashfs-factory.img

Unable to run firstboot as above.
Work around as noted worked.

jeffsf:

This appears to impact multiple devices -- the overlay is NOT erased on next mount, as indicated

Seen on IPQ4019-based Linksys EA8300 (WIP) -- master, Linux 4.19

root@(none):/# firstboot
[ 11.768586] jffs2reset: This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
[ 17.092800] jffs2reset: /dev/ubi0_1 is not mounted
[ 17.092904] jffs2reset: /dev/ubi0_1 will be erased on next mount
[ 17.096545] jffs2reset: writing /dev/ubi0_1 failed: Operation not permitted

as well as being reported at

https://forum.openwrt.org/t/solved-in-recovery-mode-firstboot-fails-jffs2reset-writing-dev-ubi0-1-failed-operation-not-permitted/28097

Mir3G

root@(none):/# firstboot
[ 32.530266] jffs2reset: This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
[ 34.958257] jffs2reset: /dev/ubi0_1 is not mounted
[ 34.963187] jffs2reset: /dev/ubi0_1 will be erased on next mount
[ 34.969244] jffs2reset: writing /dev/ubi0_1 failed: Operation not permitted


jeffsf:

jffs2reset.c:

static int jffs2_mark(struct volume *v)
{
__u32 deadc0de = __cpu_to_be32(0xdeadc0de);
size_t sz;
int fd;

    fd = open(v->blk, O_WRONLY);
    ULOG_INFO("%s will be erased on next mount\n", v->blk);
    if (!fd) {
            ULOG_ERR("opening %s failed\n", v->blk);
            return -1;
    }

    sz = write(fd, &deadc0de, sizeof(deadc0de));
    close(fd);

    if (sz != 4) {
            ULOG_ERR("writing %s failed: %m\n", v->blk);
            return -1;
    }

    return 0;

}


@@ -0,0 +1,10 @@
+--- a/jffs2reset.c
++++ b/jffs2reset.c
+@@ -80,6 +80,7 @@ static int jffs2_mark(struct volume *v)

mpa:

I can confirm the problem with firstboot for the BT Home Hub 5A and a current OpenWrt snapshot (r9851-d1739c6c9a).

jffs2reset was made for a different filesystem. Please try this instead:
ubiupdatevol /dev/ubi0_2 -t
To find the right ubi volume to wipe out:
grep rootfs_data /sys/devices/virtual/ubi/ubi0/*/name

jeffsf:

The core of the problem here is that writing a JFFS2 mark to a UBIFS volume doesn't make any sense.

jeffsf:

Duplicated by

https://bugs.openwrt.org/index.php?do=details&task_id=2121