#Having trouIble getting manjaro boot option back
185 messages · Page 1 of 1 (latest)
fdisk -l whats the output
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: KBG40ZNV256G KIOXIA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0004E77A-C737-43BE-9B24-FC07896E7D29
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p3 239616 162603007 162363392 77.4G Microsoft basic data
/dev/nvme0n1p4 162603008 163839999 1236992 604M Windows recovery environment
/dev/nvme0n1p5 163840000 165478398 1638399 800M EFI System
/dev/nvme0n1p6 172840960 491448318 318607359 151.9G Linux filesystem
/dev/nvme0n1p7 491448320 500117503 8669184 4.1G Linux swap
Disk /dev/sda: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: nal USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x68ce0ec3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 8011359 8011296 3.8G 0 Empty
/dev/sda2 8011360 8019551 8192 4M ef EFI (FAT-12/16/32)
sorry for the late reply
no like what commands
grub-install
thats it?
grub-install --target=x86_64-efi?
yes
grub-install /dev/sda --target=x86_64-efi --efi-directory=/boot this was the command I was supposed to use, but I changed it because my EFI partition is nvme0n1p5
at least that's what I thought
you did it wrong then
oh?
you arent supposed to change /boot to your nvme0n1p5
if you mounted nvme0n1p5 as /boot that would be fine already
probably the reason it couldnt find the partition
but
doing mount /dev/nvme0n1p5 /boot then running the install command would work
also isnt it supposed to be /boot/efi
you mean at the end?
yeah
oh your doing /boot/efi?
the way I tryped the command was like this grub-install /dev/nvme0n1p5
that only works for BIOS
no the command in the video was the one with the /efi at the end
wihtout*
fk my life
I can't type
are you in your install right now?
I am not in the live environment iif that's what you're asking
no i meant your literal install but live enviroment would work fine too
yeah I am in my install
alright do pacman -S efibootmgr as you probably dont have it installed
im guessing though if you dont not really sure
you are right
afterwards do mkdir /boot/efi this makes the directory of /boot/efi
says file exists
thats fine then
now mount your efi partition by doing mount /dev/nvme0n1p5 /boot/efi
done
grub-install --target=x86_64-efi --bootloader-id=GRUB --efi-directory=/boot/efi install grub
nah you can say whatever if something happens
oh yeah
nothing suppsoed to pop up
aight
probably mounted already
after installing grub make the cfg file by running grub-mkconfig -o /boot/grub/grub.cfg
installation finished
also you mentioned you have a dual boot right?
yes
yeah you do
my windows boot manager showed up
actually why am It alking let me copy paste
enerating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
done
oh you are on btrfs
i guess hope that error wont change anything but you now have to do pacman -S os-prober
done
and i think you just run os-prober
dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
yeah i think the tutorial you followed you entered /dev/sda1 somewhere
even though your efi partition is /dev/nvme0n1p5
I replaced dev sda 1 with my efi partition
whenever I ran those commands
I said that above actually, whenver I had to type grub-install instead of /dev/sda
I put /dev/nvme01np5
sorry 0n1*
what that all it said though?
was*
yes
thats your windows boot partition
no man I was too vague
I meant to correct waht I said
oh yeah
I always put partition 5
nvme0n1p5?
cat?
yeah
should I check in bios before booting?
it should show up in your boot options
but it also should automatically set it to boot to grub
yeah then that error means something
in all 10+ years of using pcs I've never seen a BIOS update wreck this much chaos
a UEFI bios update?
what happened was
I needed to do something in Windows yesterday
did my business and shut it down but came back later to look something up
then I woke up with the HP logo and that it's performing a system update
then put it me into bios update screen
I looked it up later and it seems like WIndows Update can also update your bios
I've never even looked up what bios version I'm running or anything
just out of the blue
I am already back in manjaro
but I have to keep my bootable usb at my side so I can manually select it
by going into Detect EFI bootloaders
you sure you typed that command correctly?
says it doesn't exist
5a0e5a7a541ba6942f8ef9cd62e421e4 EFI grub loader 'System Volume Information'
in the tutorial I followed, here I was supposed to get my distro
in his he gets ubuntu
when I cd into that only then I get to the distros
the way I found my grubx64.efi file was like this
yeah?
[hocaydo-hp255g8notebookpc ~]# cd /boot
[hocaydo-hp255g8notebookpc boot]# dir
amd-ucode.img grub initramfs-5.15-x86_64.img memtest86+
efi initramfs-5.15-x86_64-fallback.img linux515-x86_64.kver vmlinuz-5.15-x86_64
[hocaydo-hp255g8notebookpc boot]# cd efi
[hocaydo-hp255g8notebookpc efi]# dir
5a0e5a7a541ba6942f8ef9cd62e421e4 EFI grub loader System\ Volume\ Information
[hocaydo-hp255g8notebookpc efi]# cd EFI
[hocaydo-hp255g8notebookpc EFI]# dir
BOOT GRUB HP Linux Manjaro Pop_OS-cbfd5759-12e8-4688-8e9e-a7c0bc97362d systemd
[hocaydo-hp255g8notebookpc EFI]# ^C
[hocaydo-hp255g8notebookpc EFI]#
welp
let me try that again
why is there popos
I had popos installed at some point
I have no clue why it's there
anyway, when I cd into Manjaro then I get my grubx64.efi file
the last command in the tutorial was like this
no i was wondering if theres a device.map file there
I did it before you came to reply
and at the end it did show up in the terminal as the last boot option
but when I went into bios nothing changed
it adds a entry in uefi boot menu
yeah
oh boot menu
when I typed ls /boot/efi I couldn't cd further into EFI
but that is the content of the EFI folder
BOOT GRUB HP Linux Manjaro Pop_OS-cbfd5759-12e8-4688-8e9e-a7c0bc97362d systemd
lets just sudo rm -rf /boot and reinstall grub
because whatever tutorial you followed doesnt work on arch i guess
device or resource busy
/boot/efi?
wait a sec
sudo rm -rf /boot ✔ 2m 3s
rm: cannot remove '/boot/efi': Device or resource busy
output
well yeah
xD
try sudo rm -rf /boot/efi
same output
lsof +D /boot
should it display nothing?
it still says device or resource busy
should I run this in sudo?
hmm
yeah try
lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc
Output information may be incomplete.
before going any further, would a reinstall by any chance fix this?
it will 100%
I
I'll just back up everything then
a bit annoying that manjaro's infamous system breaking updates didn'[t bother me one bit, but a bios update caused this
crazy
thanks for the help mate
if I didn't need it for work tomorrow, I would have spent the time to try and fix this
yeah unlucky i guess on the device.map
:/
well, I'll just close this and finish backing up my things and reinstall
thanks again and a good night/day to you
u 2