Issues with UBIFS, rebooting and dashboard

General Discussions
, ,
21 
ubi0
Volumes count:                           2
Logical eraseblock size:                 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks:     2030 (257761280 bytes, 245.8 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:     7
Minimum input/output unit size:          2048 bytes
Character device major/minor:            244:0
Present volumes:                         0, 1

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        993 LEBs (126087168 bytes, 120.2 MiB)
State:       OK
Name:        rootfsA
Character device major/minor: 244:1
-----------------------------------
Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        993 LEBs (126087168 bytes, 120.2 MiB)
State:       OK
Name:        rootfsB
Character device major/minor: 244:2
22

You don’t have a data partition which is where the Mender client normally stores its state. In my vexpress-qemu build I have 5 volumes; two rootfs, one data, and two u-boot environments.

Is your u-boot stored in a different media?

Where do you store the mender client state?

Drew

23

U-Boot is on raw flash, and I have no data partition.
I used an usb-stick for that purpose, because there were no statements about the needed minimal size.

24

@kacf will this work?

25

If the USB stick is inserted permanently, it should work, but I would not consider this a robust solution. I would recommend generating a data volume on UBI as well, like the .ubimg type in meta-mender does.

For rootfs-image Artifacts, Mender requires very little space, even 1MiB should be more than enough. However, if you plan to use Update Modules (such as the single-file type that was mentioned earlier), you need at least as much space as the biggest Artifact you plan to deploy, because the files are temporarily stored on the data partition.

1 Like
26

Well, thank you ! I will create a little data partition and try this. The usb-stick was only for testing purposes to evaluate the needed size. The offline update was stored in tmpfs.