I have been having difficulty upgrading my ZimaCube to the most recent 2 upgrades.
The updates install but on reboot the system gets stuck. I have to attach monitor/keyboard and bypass some error messages or hit Ctr Alt Del.
After I log back in I do get a message saying that the upgrade was successful, however, I am still running v. 1.3.1-1 and the update message still persists.
rauc status indicates that Slot A boot status is bad.
I suppose I have 2 problems to resolve. A bad boot slot, and the inability to upgrade.
Thank you for your feedback.
More information is needed to pinpoint the issue.
1.Log in via SSH, manually update to the latest version, and then restart.
2.Connect a monitor. If an error occurs, please provide a screenshot of the error. If there’s no error, log in and confirm the ZimaOS version.
If it’s convenient, we hope you can provide a remote ID so we can assist you in troubleshooting the issue.
Thank you for the advice.
I have tried a manual update of the OS and the problem still persists.
While rebooting I get a FAILED mount then it goes into emergency mode (see attached image)
rebooting again I press up and down arrows to change my slot to slot B.
This successfully reboots, but to version 1.3.1, not 1.3.3. (even though the Update Completed message appears)
rauc status indicates Slot A is bad.
Screenshots/images attached.
journalctl file cannot be attached but available
It seems your manual update has failed. We need a screenshot of a successful manual update, similar to this output. terminal manual install, and then reboot
Please first remove the line “/media/ZiMARRK /mnt/raid none bind 0 0” from /etc/fstab and /mnt/overlay/upper_etc, then switch to the slot corresponding to version 1.3.3. When creating a RAID or mounting disks individually, try to use the Storage feature in the ZimaOS WebUI as much as possible.
Since version 1.3.2, the loading strategy has been adjusted, and the contents of /etc/fstab may affect the boot process.
