Unable to unmount rootfs partition

For Developers
22

Added the ubinfo -a and when the mount fails and it output is identical to one from a working system```

root@OpenWrt:/# ubinfo -a
UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:59
Present UBI devices:            ubi0

ubi0
Volumes count:                           3
Logical eraseblock size:                 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks:     624 (79233024 bytes, 75.6 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  40
Current maximum erase counter value:     214
Minimum input/output unit size:          2048 bytes
Character device major/minor:            248:0
Present volumes:                         0, 1, 2

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        31 LEBs (3936256 bytes, 3.8 MiB)
State:       OK
Name:        kernel
Character device major/minor: 248:1
-----------------------------------
Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        339 LEBs (43044864 bytes, 41.1 MiB)
State:       OK
Name:        ubi_rootfs
Character device major/minor: 248:2
-----------------------------------
Volume ID:   2 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        210 LEBs (26664960 bytes, 25.4 MiB)
State:       OK
Name:        rootfs_data
Character device major/minor: 248:3
23

I also encountered this issue, which resulted in the upgrade being unable to save the original configuration. What is the final solution? The link you provided cannot be opened?

24

We couldn't narrow down the issue as the repro was difficult. Knowing this could potentially happen we had a common partition and we used a backup from that partition in case the copy failed.

25

The partition cannot be mounted with commond "mount -t ubifs ubi0:rootfs_data /tmp/overlay" after run_ramfs. You copy the sysupgrade.tgz to a common patition, then after reboot, you copy configuration to rootfs_data partition?