You may encounter a failure where the system boots into a textual display with the following messages:
Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/innitramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
This error condition can emerge for a number of reasons, explained below.
It's possible that filesystem corruption has been detected and the bootup process is unable to automatically repair it, perhaps because there is a chance of data loss during the repair process.
Before your proceed with the repair process, you are advised to back up your data, perhaps using an Endless USB Stick to access your system. There is a possibility of data loss during the recovery process.
Two options for recovery are detailed below, you only need to follow one.
At this point, you should be able to successfully boot into your Endless OS installation once again, however there is a small chance that the problem will reoccur in future.
The following advanced procedure is intended for technicians who are comfortable with the command line shell prompt.
It is possible to run the filesystem checker directly from the emergency shell. You will likely be asked a series of detailed technical questions about what actions to take as the filesystem damage is handled.
The command to enter is:
# fsck /dev/disk/by-label/ostree
Because of the way we set things up in our Windows & Endless OS dual boot, we don't support booting Endless OS when Windows is hibernated. We would normally detect this situation and instruct the user to reboot into Windows and do a proper shutdown before trying to boot Endless OS again, but for systems installed using an Endless OS version between 3.8.0 and 3.9.3, there was a regression with this detection mechanism, which led to Endless OS failing to start and ending up in the system's emergency shell.
This problem is solved in Endless OS 3.9.4, but unfortunately the fix does not affect existing installations.
You can see which version was used for your original installation by generating a debug log and checking the
Endless OS imagesection.
You can work around this situation by simply rebooting into Windows and performing a full shutdown before trying to boot into Endless OS again. Unfortunately the problem will reoccur in future if the same conditions are met again, but you could adjust Windows power settings to disable hibernation to avoid this.
Alternatively you can uninstall Endless OS and then reinstall with Endless OS 3.9.4 or newer.
This condition can also occur in other unusual circumstances. If you wish to inspect the system logs once the system reaches this point, you can type
journalctl at the prompt and press Enter.
The logs are shown one page at a time. You can press Page Down or PgDn to view the next page.
In order to share the logs with a technician, the easiest way is to take a photo of the computer screen, then proceed to the next page, take another photo, etc. You may have to take 15-20 photos before the logs are complete. Once done, you can share the photos with the technician.