Troubleshooting for automatic upgrades that fail to restart
When users cannot boot after an automatic upgrade, they are directed to the page
In this page there are some commands to run, but this commands are meant for a booting Tails:
the output of the five following commands, run in a Terminal: ls -l /lib/live/mount/medium/live cat /lib/live/mount/medium/live/Tails.module mount df -h free -m
The user cannot run the broken Tails, so the instructions should be more:
- Start another Tails
- Mount the Tails partition with Disk Utility (not TailsData)
- Report a bug with the output of the five following commands, run in a Terminal:
ls -lh /lib/live/mount/medium/live
or something like that.
Related to Tails -
|Related to Tails - Feature #15130: Restructure our support page and content||Confirmed||2013-09-28|
Related to Tails -
Blocks Tails -
#3 Updated by intrigeri 2015-10-10 02:53:22
> When users cannot boot after an automatic upgrade, they are directed to the page
Just to clarify: is that true in general, or only when we explicitly and manually ask them to provide the same information as the instructions on that page would produce?
#4 Updated by emmapeel 2015-10-10 03:04:53
Well, I think it that the page says ‘might be unable to start’, so maybe we can add a note for this case specifically, like: “If you cannot start then you need to mount it from another Tails”
Tails partition is not mounted automatically, and I think users new to Linux could not provide us with the debugging info during the problems with Tails 1.6 because of this little detail.
#6 Updated by sajolida 2016-02-08 16:33:00
- Subject changed from Debugging steps in 'upgrade error' documentation must be adjusted to Troubleshooting for automatic upgrades that fail to restart
- QA Check changed from Dev Needed to Info Needed
The page “/upgrade/error/install” reads “The upgrade could not be installed. Your Tails device needs to be repaired and might be unable to restart.” and this page is pointed to from “/doc/first_steps/upgrade” with the label “If an error occurs while installing the upgrade”.
So this page correctly corresponds to an automatic upgrade that fails while Tails is still running.
What you are referring to is the lack of troubleshooting information if the automatic upgrade succeeds but it’s impossible to restart on the device.
I think this should be treated as a different case from “/upgrade/error/install”. Maybe as “/upgrade/error/restart”. Renaming this ticket accordingly.
emmapeel: do you agree? do you want to work on this?
#32 Updated by cbrownstein 2019-09-25 07:23:53
- Status changed from Needs Validation to In Progress
- Assignee changed from cbrownstein to sajolida
I’ve pushed a few changes to my branch. Otherwise, looks good!