I went to turn off my computer (AMD Framework Laptop) and it said it would install pending updates and turn off. I clicked yes. I went to the store, came back, and turned on my laptop to find it will no longer boot past the fedora logo.
I can still get into the UEFI and all that, and can even boot into a flash drive environment, but it wont even let me reinstall fedora without completely wiping the ssd.
Is there any solution to this? Or at least a way to salvage my data?
Unless the system drive has failed, you should be able to mount the system drive using a Live USB installer. With Workstation, Gnome disks will let you check the “health” of the drive and mount it so you can copy essential data to another drive.
I have gnome disks pulled up, first time using this so bear with my unfamiliarity, and I don’t see any ability to copy data from the ssd. Is there a particular way to initiate that option?
I assume you found the SMART Data and Self-Tests in the button with 3 vertical dots and the drive shows as “Healthy”. The same menu allows you to create an image of the disk, which will give you an “image” file that contains everything on the disk, but will be very large. If your system disk has lots of data, that may be your best option, but if you only need to save a small amount of data, you can mount the system partition using the small triangle at the bottom right after selecting the system disk. Once the system is mounted, you can use the command-line or Files GUI to copy selected data to another drive (such as a USB stick big enough to hold the data).
Still trying to figure out which update caused the total boot failure, but this saved me SO much time and work. Thank you so much!
Sometimes Linux goes into a long processing step when booting updates that leads to people interrupting the running process. Pressing the Escape key at boot should let you see what is running.
Boot failures can also be caused by running out of space on the filesystem, interrupted update due to power failure, bits flipped (more likely during periods of high solar activity), etc. Troubleshooting steps:
<space>3 to end of kernel command line to boot to a text consolejournalctl —directory … to view the journal entries on the system drive.(post deleted by author)