Boot failure/ Grub menu missing rescue option/ False UEFI Password Prompt

yes.

Fairly new to Linux, brand new to Qubes, NOT a programmer, but NOT a novice, either.

Device = LT ASUS Vivobook F1504VAP-WH56

Everything working ok before, but not the first time I’ve had this issue. Thought system had recovered on its own. Guess not.

  1. Un-encryption of SSD screen presents F1/F2/F8 choices in upper left corner, unlike usual.
  2. Successful password entry grants access to Grub menu, but no boot options work, only re-boot. No menu entry for “qubes rescue”.
  3. Unable to access UEFI to adjust boot order to USB-first. Presents Password Screen, though no UEFI pwd ever established!
  4. Default USB controller for mouse will not defeat boot-up in order to re-format SSD.
  5. Latest version(s):
  • qubes (R4.3) w/ xen hypervisor > fails, w/ re-boot to SSD un-encryption screen
  • Grub version = 2.06
  • Xen hypervisor = 4.19.4
  • Qubes OS = R4.3 w/ 4.19.4 and Linux 6.195-1.qubes.fc41.x86_64
  1. Past listed boot options (4), w/ varied Linux versions, none of which work.
  2. Have one USB controller open for mouse, but thumb drive not read there on boot-up; goes straight to OS (Grub) sequence.

How can I fix -OR- defeat the boot-up to access the BIOS to change boot order & simply start over with a low-level format & install of a fresh OS?

Mike C

It sounds like you need to press F2 during the self-test at reboot. (maybe Fn-F2 with the laptop keyboard)
Other systems can use del, sometimes.
The timing is important, but you can press multiple times, until the BIOS is accessible.

If a separate screen is plugged in, you may see nothing on the screen during the initial boot, so you will have to start blind, or unplug it…

Nope. Just brings me straight-in to a UEFI Password screen Ive never seen before or ever set up.

My core problem is the default Qubes policy to deny all USB ports upon installation. The one, USB controller (port) I opened-up for my wired mouse doesnt grant access for any other USB device.

I don’t know what else to do except pull the SSD & either zero-fill it as a subservient drive on another computer or replace it all together.

Ideas Welcome.

MC

After re-reading your first post:

  • is there a decryption password before grub? This cannot come from Qubes-os, I think.
  • Maybe you turned on full disk encryption in the uefi/bios? Or someone else?
    • this could explain why uefi wants a pw to allow changes.
    • pw may be the same as the disk pw.
  • If you really never had a uefi/bios password, then either a hardware problem or someone has been messing with your computer.
  • I think there is no way to remove a setup password. It is stored in the hardware, and probably requires help from ASUS or a hardware hacker.
  • It could be, for F1,F2,F8 :
    • F1 = help
    • F2 = Uefi setup
    • F8 = Boot select (same on my asus)
  • Maybe F8 will allow to boot a USB rescue key, and fix the original problem?
  • (little question) Did you use a machine translator on your post? or an computer to help write it? If you did, if is OK, but it is a good idea to let us know.

RESOLVED by Other Means*

Sought to isolate the source of the problem, is it hardware or software, I asked.

*26 years of computer-building hit me between the eyes with “hardware 101”: BIOS doesnt need an OS; a drive (for that matter).

So I removed the M.2 drive from my ASUS Vivobook LT. I booted straight into the BIOS, verifying it was a software hangup within the OS, probably LUKS. Anyway, I manually ESTABLISHED a UEFI Password, tested on the re-boot. NOTE: boot sequence still showed footprint of Qubes, along with UEFI. Iprobably should have made UEFI the priority, but didnt think to.

Successful, I re-installed the M.2 drive, inserted my Qubes OS install USB & booted-up. I had a full Grub menu again. Unsure, I randomly chose ‘Troubleshoot…’ over ‘Rescue…’.

After whatever analysis it did, it prompted a complete re-install, which I did successfully. I’ll never know if ‘Rescue’ would have been quicker, etc.

I was able to successfully boot-up, login to UEFI/ Encrypt/ Desktop & start from scratch, performing updates on default qubes.

My one issue is not being able to disable ‘Fast Boot’; to change the boot order, as-desired. ‘Qubes’ is my default Option #1.

Suggestions welcomed.

Haha. No machine translator, just me. Never got that one before. Thank you. You may have read my response by now that I resolved the issue & started with a fresh qube install.

Again, thank you for your considerate & thoughtful time & attention.

Shalom

Mike

1 Like