[SOLVED] grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

[SOLVED] grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Post by NoHo Hank »

My dualboot W10 (on UEFI) +LM21.1 (on legacy) Cinn doesn't boot anymore. I changed from legacy to UEFI but W10 didn't boot: it got into a bootloop. Turned back to legacy and since then LM doesn't boot either!

Code: Select all

grub rescue>
is all that shows up.
In liveboot can acces the files from one LM partition as root only. Plus win10 files.

Can't access HOME with the desktop files that seems to be encrypted? It has this READ ME file
THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA.

From the graphical desktop, click on:
"Access Your Private Data"
RESULT: can't execute commands from remote site

or
From the command line, run:
ecryptfs-mount-private
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

RESULT:
mint@mint:~$ ecryptfs-mount-private
ERROR: Encrypted private directory is not setup properly
mint@mint:~$ sudo ecryptfs-mount-private
ERROR: Encrypted private directory is not setup properly
mint@mint:~$
How get grub working???
Last edited by LockBot on Thu Nov 30, 2023 11:00 pm, edited 5 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

Re: It's that time again: grub rescue>

Post by NoHo Hank »

After being recovered from the shock having a unbootable machine i grabbed myself together and:
Image
Tried 1 https://linuxconfig.org/introduction-to ... ely-broken

as ROOT fdisk -l

Code: Select all

mount /dev/nvme0n1 /mnt
root@mint:~# mount /dev/nvme0n1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error.
root@mint:~# 

Tried-2 https://christitus.com/grub-rescue/

Code: Select all

root@mint:~# ls
Desktop
root@mint:~# cd /dev/nvme0n1
bash: cd: /dev/nvme0n1: Not a directory
root@mint:~# cd /dev/nvme0n1p4
bash: cd: /dev/nvme0n1p4: Not a directory
root@mint:
Tried-3

Code: Select all

grub > ls (hd0,msdos1)
filesystem unknown

grub > ls (hd0,msdos1)/grub2
error /grub2 not found

grub > ls (hd0) 
(hd0): filesystem unknown

grub > ls (hd0)/
(hd0): filesystem unknown
Please help...
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

Re: It's that time again: grub rescue>

Post by NoHo Hank »

I have removed the 2nd ssd. Only the one shown in Gparted is installed now.
It is showing:
PXE-MOF exiting PXE ROM
no bootable device insert bootdisk and press any key
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
mikeflan
Level 16
Level 16
Posts: 6985
Joined: Sun Apr 26, 2020 9:28 am
Location: Houston, TX

Re: grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Post by mikeflan »

W10 (on UEFI) +LM21.1 (on legacy) Cinn doesn't boot anymore
As you probably know I am unlikely to solve this for you. But let me ask some questions.
W10 (on UEFI) +LM21.1 (on legacy) Cinn was working fine - for months?
Then what happened that was different?
LM would boot, but win would not?? And what happened instead when you tried to boot into win?
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

Re: grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Post by NoHo Hank »

mikeflan wrote: Wed May 31, 2023 7:40 pm W10 (on UEFI) +LM21.1 (on legacy) Cinn was working fine - for months?
Hi mikeflan, thanks for asking.
Yes the dualboot was working very well for months. And i seldom have to use Win. It's always LM booting.
What happened as i remember: i had just put some 6gb win8.iso's data on a stick. Had changed the bios into uefi and reboot to get into win10.(to make a win8 live usb stick via the Win10 system) At some point during boot i noticed the stick was still attached, i pulled it out quickly.

Then i got into a bootloop win10 couldn't start. Changed back to legacy and LM couldn't boot either: grub rescue.
Later detached the 2nd ssd from the machine and now were in the PXE-MOF.
Not sure if this is the reason of the troubles. But this is what i've done
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

Re: grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Post by NoHo Hank »

I've been watching several utube 100% fixed solved etc bs info.

Changing anything in the BIOS doesn't change a bit.
IN liveboot i can access all windows files and the data on LM except in home/nohohank that is showing a README
From the command line, run:
ecryptfs-mount-private
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Which doesn't work, like i wrote before.
Anyhow the drive is ok.
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
User avatar
NoHo Hank
Level 5
Level 5
Posts: 522
Joined: Wed Jun 29, 2022 6:03 am

Re: grub rescue> became PXE-MOF exiting PXE ROM no bootable device

Post by NoHo Hank »

iT WAS A HELL OF A job to get it right. A combination of securboot and bootrepair via liveboot were some of the measures. Finally it came to a good end.
Demand technology that serves us - https://peoplevsbig.tech/
None of Your Business https://noyb.eu/en
Locked

Return to “Installation & Boot”