So my problem is that I have an Acer Aspire 5 (A515-56-56DJ) laptop that had windows preinstalled- never booted into windows as I preceded to run a Manjaro 20.2.1 liveusb installation on. I have a dell xps of my own that I have successfully installed Manjaro onto numerous times without issue (so I’m not stranger to the interface) - the laptop into in question is for my Nephew.
I have never done a UEFI install as this Laptop in devoid of the ability to use a legacy boot.
I went and disabled fast boot and secure boot in the bios.
I did the GUI installation and everything seemed to go well. Restarted the computer and BAM! slapped with an emergency shell with the message:
ERROR: resume: hibernation device 'UUID=00c29a38-0fbf-4bc3-b57e-0ebd706b2519' not found mount: /new_root: can't find UUID=907b1aaf-e75d-444d-ae4b-bd667abfa344. You are now being dropped into an emergency shell. sh: can't access tty: job control turned off [rootfs ]#
Also I am not dual booting. Many the similar issues I found had a dual booting scenario- I do not.
Things that I have tried since:
- Reinstalling - choose the erase disk option and found that the new install yeilded EFI partion but the partitions being replaced did not show an EFI partition- that also happened the next time re-installation was tried, so as far as I can tell the GUI installer is claiming that it will make as EFI partion but does not.
- Creating a new liveusb
- reinstalling the grub (more on this in a few moments) - I did this because I found that the install DID NOT place any files into /boot/efi. But the laptop did not want the go to the bios after the grub was reinstalled, so does this mean that the computer saw, preventing access to the bios, but it but didn’t know what to do with it?
- Manually partitioning the drive (it is an nvme) - the graphical manual installation DOES NOT have and ‘esp’ flag option.
- even tried changing trusted bootloaders in the bios.
- probably did a ton of other things I can remember trying.
I have looked at a number of other topic under support on the forum with similar symptoms but have not found a cause.
My best guess is that the drive needs to be partioned manually and the efi partition needs to be created using an ‘esp’ flag.