Recovery Methods Mangoh Yellow

Hi there,
I am currently trying to understand the rollback behaviours on a mangoh yellow. First of all, I realized it is necessary to mark the deployed applications as good (as in legato status) to avoid rollbacks of the applications in case of for instance brown outs.
But now I have a setup, where in a brown out the the legato apps will survive, but the content of the filesystem is presumably getting lost, specifically files in /etc. I tried to use AT!NVBACKUP to mark it as a valid image and executed, for testing purposes, AT!RMARESET=3 after deleting on of the files to check if the files would magically reappear. Unfortunately, they do not.

Hence, I am now a little bit confused. Will AT!NVBACKUP only ensure that the apps will get recovered in a reset, or should this also cover the filesystem? And, if if doesn’t, how can I ensure that the content of the filesystem gets persisted, so that in case of a recovery they will be available again?

Regards,
Benedikt

I found something new, the command AT!NVRESTORE. Of course I tried it, but now I am stuck in a state where the virtual network device doesn’t appear anymore. If I remember it correctly one of the devices should get renamed and turned into a network device?

[ 3167.826413] usb 3-2.1: new high-speed USB device number 29 using xhci_hcd
[ 3167.931934] usb 3-2.1: config 1 has an invalid interface number: 8 but max is 3
[ 3167.931942] usb 3-2.1: config 1 has no interface number 1
[ 3167.939754] usb 3-2.1: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 3.18
[ 3167.939765] usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3167.939769] usb 3-2.1: Product: WP7608
[ 3167.939771] usb 3-2.1: Manufacturer: Sierra Wireless, Incorporated
[ 3168.054857] qcserial 3-2.1:1.0: Qualcomm USB modem converter detected
[ 3168.055144] usb 3-2.1: Qualcomm USB modem converter now attached to ttyUSB1
[ 3168.080229] qcserial 3-2.1:1.2: Qualcomm USB modem converter detected
[ 3168.080472] usb 3-2.1: Qualcomm USB modem converter now attached to ttyUSB2
[ 3168.112112] qcserial 3-2.1:1.3: Qualcomm USB modem converter detected
[ 3168.112360] usb 3-2.1: Qualcomm USB modem converter now attached to ttyUSB3
[ 3168.144680] qmi_wwan 3-2.1:1.8: cdc-wdm1: USB WDM device
[ 3168.153722] qmi_wwan 3-2.1:1.8 wwan0: register 'qmi_wwan' at usb-0000:05:00.3-2.1, WWAN/QMI device, be:28:bd:51:5a:5a

I can still flash the board via swiflash, but I am unable to get the SSH connection up and running. Does anybody have an idea how this could have happened and how I can solve it again?

Regards,
Benedikt

What are the return of the followings?

At!entercnd=“A710”
At!usbcomp?

at!entercnd="A710"
OK
at!usbcomp?
Config Index: 1
Config Type:  1 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0) 

OK

This was a really hot tip:

at!entercnd="A710"
OK
at!usbcomp?
Config Index: 1
Config Type:  1 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0) 

OK
at!usbcomp=1,1,8010D
OK
at!usbcomp?
Config Index: 1
Config Type:  1 (Generic)
Interface bitmask: 0008010D (diag,nmea,modem,rmnet0,ecm) 

OK
[ 9009.418408] usb 3-2.4.1: new high-speed USB device number 31 using xhci_hcd
[ 9009.523765] usb 3-2.4.1: config 1 has an invalid interface number: 8 but max is 5
[ 9009.523775] usb 3-2.4.1: config 1 has an invalid interface number: 19 but max is 5
[ 9009.523779] usb 3-2.4.1: config 1 has an invalid interface number: 20 but max is 5
[ 9009.523781] usb 3-2.4.1: config 1 has an invalid interface number: 20 but max is 5
[ 9009.523784] usb 3-2.4.1: config 1 has no interface number 1
[ 9009.523786] usb 3-2.4.1: config 1 has no interface number 4
[ 9009.523788] usb 3-2.4.1: config 1 has no interface number 5
[ 9009.531745] usb 3-2.4.1: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 3.18
[ 9009.531755] usb 3-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9009.531759] usb 3-2.4.1: Product: WP7608
[ 9009.531761] usb 3-2.4.1: Manufacturer: Sierra Wireless, Incorporated
[ 9009.674189] qcserial 3-2.4.1:1.0: Qualcomm USB modem converter detected
[ 9009.674404] usb 3-2.4.1: Qualcomm USB modem converter now attached to ttyUSB1
[ 9009.705089] qcserial 3-2.4.1:1.2: Qualcomm USB modem converter detected
[ 9009.705271] usb 3-2.4.1: Qualcomm USB modem converter now attached to ttyUSB2
[ 9009.737094] qcserial 3-2.4.1:1.3: Qualcomm USB modem converter detected
[ 9009.737536] usb 3-2.4.1: Qualcomm USB modem converter now attached to ttyUSB3
[ 9009.769206] qmi_wwan 3-2.4.1:1.8: cdc-wdm1: USB WDM device
[ 9009.778504] qmi_wwan 3-2.4.1:1.8 wwan0: register 'qmi_wwan' at usb-0000:05:00.3-2.4.1, WWAN/QMI device, be:28:bd:51:5a:5a
[ 9009.784257] cdc_ether 3-2.4.1:1.19 usb0: register 'cdc_ether' at usb-0000:05:00.3-2.4.1, CDC Ethernet Device, 46:20:ae:c5:20:d4
[ 9009.813310] cdc_ether 3-2.4.1:1.19 enx4620aec520d4: renamed from usb0

Thanks a lot for that tip, I can connect now again via SSH.

Unfortunately, my filesystem changes for testing are still there. Hence, AT!NVRESTORE and AT!NVBACKUP are presumably not the recovery mechanism for the filesystem?

What is the reproducible step?

So far I could not reproduce it, that is the reason why I played around with NVRESTORE and RMARESET. It happened once, probably caused by a series of brown outs, that the content of the filesystem was lost but the legato app still existed. This is what I would like to avoid, I do not want to lose the content of the filesystem in any case.