On Wed, Jul 16, 2025 at 11:06 PM Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:
[...]
Something is royally fubared, that prevents the system from coming up, so
it's thrown into emergency mode. Correct diagnosis requires quite a bit of
expertise, and know how, to try to recover, starting with deciphering
systemd's binary logs (instead of old, boring, plain text log files). And if
the binary logs themselves are corrupted, well, you're stuck.
You can run journalctl in a Live Installer USB with the --directory option to
see journal data on the system drive.
The fastest solution might be to just mount a flash drive, or something,
find whatever files are important to you, and copy them to the flash drive,
then reinstall from scratch. Afterwards, if time permits, look into getting
a UPS, then use nut or apcupsd to prevent this from ever happening again.
You certainly want to make getting a backup a priority. Then try to find the
error that sends you to emergency mode. Unsafe shutdowns often result
in corrupted filesystems. You need expert advice based on the errors you find.
George N. White III
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
