Hi all,
Recently we swapped out our old-boot disk for a newer high-capacity disk due to the database logging.
Ever since we’ve done this, the machine breaks during forced auto-update restarts.
During regular planned reboots the machine reboots perfectly fine, without any issues.
It seems to re-write the old UUID back to the /etc/fstab /boot partition, this causes the machine to reboot into an emergency shell.
The only way we are able to fix this is by manually settings the /boot UUID back to its correct value within a live cd environment.
Is there some hard-coded UUID that we are not aware of that forced the UUID to return back to its old value?
As far as we can see, there is no sign of an old UUID in the sqlite3 app.db.