1

Let me first say that, while I would like to say I'm an experienced computer user, this was an absolute stroke of idiocy on my part.

I have a Dell G15 that has a 1 TB NVME. I wanted initially to resize the EFI partition to from 100 MiB 2 GiB (Windows default), as I was trying to install arch, and it failed to boot (I assumed that the reason for this, due to the fact that grub couldn't write to the partition, was that it was full). The existing EFI partition was bordering a Windows install, and I didn't want to disturb that in hopes of recovering it in the future (at the time, neither arch nor windows could boot). I read that the EFI partition doesn't actually have to be the first partition on disk, however, so I just created a new EFI partition alongside my arch root partition (which I resized) and life was good. And then I deleted the original EFI partition.

What I thought would happen is that the system would give me an error saying that it couldn't find any bootable media and redirect me to a firmware menu.

Instead, what happens is that the firmware happily does it's thing until it reaches the dell splash screen. Then nothing happens. I have pressed all the usual keys (F2/F12, tried delete as well), and the menus do not pop up. I suppose the menus were actually EFI executables that were in that first partition which get ran after the firmware startup, but since I deleted it, it can no longer access them.

There is a way I can theoretically recover from this, which is to open my laptop up, take the NVME out (assuming it's accessible), put it in my desktop, and use the arch install medium I have to try to rebuild it. The data / file system is still there, so hypothetically I can just recreate the partition.

My question is that, bar opening up my laptop and desktop (which is my last functional computer), is there any way to get some sort of response out of my laptop that can let it boot to my recovery medium?

Responses to comments: I have not tried to open up of the laptop yet and ideally want to avoid doing this, but resetting the firmware is a logical next step, and this avoids me having to open up my desktop, so thanks.

Pressing (or holding) the usual F2/F12 keys as well as other common ones (esc/del) doesn't work at all.

I figured that the EFI partition doesn't have to be 2 GiB, but I did see that if a user wants to install multiple kernels, 2 GiB is recommended, and I wanted to give myself the room just in case.

I don't think legacy/BIOS compatible mode was enabled on my machine when I had UEFI access, and all my partitions were UEFI capable, but I cannot say for certain now.

5
  • 2
    Have you tried to open your laptop up and go through the steps to reset its firmware settings (NVRAM/"CMOS"), just in case it's hitting some bugs while trying to find a nonexistent boot entry? What happens if you hold the usual keys while powering on the system (which will often bypass EFI "fast boot")? Commented Aug 27, 2023 at 14:45
  • 1
    You could use TestDisk to recover the EFI partition.
    – harrymc
    Commented Aug 27, 2023 at 15:11
  • 3
    EFI partition doesn't need to be 2GB, just the max size required for a distro plus 100MB for Windows. 512MB is what Arch recommends to cover all UEFI firmware implementations, so 627MB RAW would be the max required (the most I've seen a distro require is 768MB). Do you have CSM [Legacy] Mode enabled, as if no EFI boot options are detected, usually either UEFI firmware error screen shows or the EFI CLI shell appears (CSM Mode should never be enabled, as it' sole purpose was to support distros circa <2017 that didn't yet support EFI boot)
    – JW0914
    Commented Aug 27, 2023 at 15:42
  • It is vastly easier and safer to use virtual machines. These problems do not occur,
    – anon
    Commented Aug 27, 2023 at 15:49
  • “I suppose the menus were actually EFI executables that were in that first partition which get ran after the firmware startup, but since I deleted it, it can no longer access them.” - No, the EFI partition didn’t have executables. You absolutely should be able to reach the UEFI menus. Your idea of taking an IC out of your laptop and putting it I. Your desktop absolutely will not work
    – Ramhound
    Commented Aug 27, 2023 at 16:09

1 Answer 1

1

I stand corrected--it seems like perhaps the UEFI not showing a menu was due to a bug where the bios menu is inaccessible when fast boot fails. It wasn't, as I initially suspected, due to the UEFI having executables in the boot sector, which doesn't make a lot of sense in the first place.

I took apart the laptop and reset the CMOS, as some comments suggested, but I also took out the M.2 NVME entirely and booted just to see what would happen. And it does indeed show me an error message after it checks the media. Now, apparently, I can press F2/F12 as normal.

Thanks to all those who commented.

Edit: To all those who visit this looking for a solution--unplugging the NVME does work, but if you shut down and plug it back in, it will resume it's previous behavior (of freezing at the dell screen). This particular laptop also does not seem to have a CMOS battery, and Dell does not seem to have proper documentation on how to properly reset the CMOS. I did reset the UEFI via firmware settings with the NVME unplugged, but it still had the same issue. I also couldn't insert the NVME live in the laptop when it was booted. So I ended up doing the solution I mentioned initially in the question and used my desktop to recover the partition.

Another edit (2 months in the future): After I wiped the NVME, I then decided to just install windows again, completely vanilla, as a simple measure. Two months later, THE SAME ISSUE HAS HAPPENED. This time, I was not fooling around with it at all, the issue just happened naturally. I think this may have been because I never shut down my computer, and it ran into a weird perpetual-sleep glitch or something, but WHEN I SHUT IT DOWN, THE FAST BOOT (or whatever) BOOTS IT UP TO A BLACK SCREEN AGAIN (no EFI menus, no boot, no access). This is the stupidest issue I have ever encountered with a computer! Now I have to open up my desktop AGAIN and, I suppose, nuke the EFI partition so that I can install Arch (you bet I'm not running Windows anymore).

I'll just ask the community: Does anyone know of a BIOS version that me or others (I've seen similar weird sleep/boot issues with other Dell G15 laptops, namely this one, this one, these, and this poor person) can use to not have issues related to the computer not powering on? Or is this just a feature integral to Windows and all compatible BIOSes? Thanks.

1
  • 2
    Suggestion for future: before changing disk partitions, make an image. It's standard practice. Commented Aug 27, 2023 at 18:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .