#[Solved] I used `bootctl remove` i'm not able to boot
271 messages · Page 1 of 1 (latest)
Of course because bootctl deletes the boot entry from the firmware
Do you want to reinstall grub?
Yes
I tried following one article but it fails to generate the fstab saying it’s not a mount point
You'll need a usb with an iso on it
I’m on one right now
Alright what's the output of efibootmgr
[liveuser@eos-2023.05.28 ~]$ efibootmgr
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0005,0006,0007
Boot0005* Windows Boot Manager HD(6,GPT,5adb5b4a-3b2e-43e6-84ad-3e20887d88a9,0x3a286000,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000069000100000010000000040000007fff0400
Boot0006* UEFI: JetFlashTranscend 4GB 1100, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,GPT,ab770dcd-f83f-4aaa-bc7a-3ba63b510818,0x800,0x789fdf)0000424f
Boot0007* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(1,GPT,394dbe81-ab4b-4190-a0f7-c004b70dd377,0x800,0xe5377df)0000424f
[liveuser@eos-2023.05.28 ~]$
Mounting the partitions & doing that right?
Okay
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.7G 1 loop /run/archiso/airootfs
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 16M 0 part
├─sda2 8:2 0 465.7G 0 part
└─sda3 8:3 0 465.7G 0 part
sdb 8:16 1 3.8G 0 disk
└─sdb1 8:17 1 3.8G 0 part
sdc 8:32 1 114.6G 0 disk
└─sdc1 8:33 1 114.6G 0 part /run/archiso/bootmnt
nvme0n1 259:0 0 465.8G 0 disk
├─nvme0n1p1 259:1 0 16M 0 part
├─nvme0n1p2 259:2 0 360G 0 part
├─nvme0n1p3 259:3 0 100.1G 0 part
├─nvme0n1p4 259:4 0 4G 0 part
├─nvme0n1p5 259:5 0 1.1G 0 part
└─nvme0n1p6 259:6 0 512M 0 part
nvme0n1p5 -> /boot
nvme0n1p3 -> root
Yep
done
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=432fceab-dd7e-4a9d-9449-e79e7d21e3d7 / ext4 defaults,noatime 0 1
UUID=df7acc0a-8cfd-425a-bd0e-bddb64473c46 swap swap defaults 0 0
UUID=DC78-DF3C /boot/efi fat32 defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
yes, Sorry
Added the 3rd entry manually off memory
Why did you add it manually
https://medium.com/@correspond.shashank/broke-my-arch-linux-again-heres-how-i-fixed-it-5db2db040b14
Was following this article, He asked to remove the entry. But then when adding it back using:
genfstab -U -p /mnt >> /mnt/etc
It said "/mnt is not a mountpoint"
Today my Arch Linux broke again. But this was different from past times. Previously, I have broke my Arch Linux while updating (that’s a…
efi grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img syslinux vmlinuz-linux
arch-chroot /mnt
done
Btw did you uninstall the grub package?
Nope
grub-install --target=x86_64-efi --efi-directory=/boot/efi
done
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
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.
ERROR: mkdir /var/lock/dmraid
Adding boot menu entry for UEFI Firmware Settings ...
done
Just a minute
okay
Is p2 your windows partition?
yes
Run lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
sda
├─sda1
├─sda2
└─sda3
sdb
└─sdb1
sdc
└─sdc1
nvme0n1
├─nvme0n1p1
├─nvme0n1p2
├─nvme0n1p3 52.9G 41% /
├─nvme0n1p4
├─nvme0n1p5 887.6M 24% /boot/efi
└─nvme0n1p6
Output of fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
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: gpt
Disk identifier: 027BE95B-B95B-4720-8D87-7306FE72E738
Device Start End Sectors Size Type
/dev/sda1 34 32767 32734 16M Microsoft reserved
/dev/sda2 32768 976775167 976742400 465.7G Microsoft basic data
/dev/sda3 976777216 1953521663 976744448 465.7G Microsoft basic data
Partition 1 does not start on physical sector boundary.
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: KINGSTON SNVS500G
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: 9C9E4A0F-5866-4EBF-9BFF-29811EA8C2E6
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 34815 32768 16M Microsoft reserved
/dev/nvme0n1p2 34816 754960383 754925568 360G Microsoft basic data
/dev/nvme0n1p3 754960384 964941823 209981440 100.1G Linux filesystem
/dev/nvme0n1p4 964941824 973326335 8384512 4G Linux swap
/dev/nvme0n1p5 973326336 975724543 2398208 1.1G EFI System
/dev/nvme0n1p6 975724544 976773119 1048576 512M EFI System
Disk /dev/sdb: 3.77 GiB, 4048551936 bytes, 7907328 sectors
Disk model: Transcend 4GB
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: DDF98356-A8EF-4BD5-8DC8-AAF9EBE9B58D
Device Start End Sectors Size Type
/dev/sdb1 2048 7907294 7905247 3.8G Microsoft basic data
Disk /dev/sdc: 114.61 GiB, 123060879360 bytes, 240353280 sectors
Disk model: Ultra
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: E2901035-5E4B-4BCD-B9D5-A3CFFCB3D6E7
Device Start End Sectors Size Type
/dev/sdc1 2048 240353246 240351199 114.6G Microsoft basic data
Disk /dev/loop0: 1.69 GiB, 1815875584 bytes, 3546632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@EndeavourOS /]#
mount /dev/nvme0n1p1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
EFI grub initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux
Esp?
efi system partition
I messed a lot of things up recently, I had to even fix the boot for windows
ls /boot/efi/EFI
Inception
ls /boot/efi/EFI/EFI
Grub
Idk is it?
Yeah, it seems so
hmm
from bios?
yeah
Everything was working fine, Until I decided to install systemdboot
and then uninstall it
Alright, let's fix this temporarily but this is cursed why is windows installed in legacy mode xD
.aw dual boot
Let me share the events
- I have windows & arch running all good. Can boot into both using Bios. Linux is installed with Systemd-boot
- I decide to install reviOs. Gaming version of windows from some third party. Windows works, Can't find linux in boot menu.
- I reinstall linux but this time with grub. Now Windows is nowhere to be found in Bootmenu.
- I download normal windows 11 iso, copy the bootfiles to the last EFI partition which i created from that ISO.
- Now both of them work.
But i decide to switch to SystemD boot, and uk what happened next
what do I follow
Do you have any files you need on the linux installation
I mean I can always have them back, but problem is I dont wanna spend time getting the nvidia drivers & hyprland working properly again
Alright let's just fix the arch install for now then we'll discuss xD
lol okay
So do rm -rf /boot/efi
done
Do I have to mount and chroot it first?
because I just did it directly 🙂
have I removed the boot from USB as well 🙂
I closed that terminal
Oh, so you chrooted again before running rm ?
Nope

I'm honestly unsure as I haven't run into this scenario before, but the iso might be borked xD
lol. I can get the ISo setup again, But I guess we could fix the main issue whilst i'm booted up
Should this be /mnt/boot
else it would be like
efi/efi/efi
Keep it at /boot/efi
We need to install ntfs-3g to mount the windows system partition
So do pacman -Syu ntfs-3g
Try mount /dev/nvme0n1p1 /mnt this time
mount.nilfs2: Error while mounting /dev/nvme0n1p1 on /mnt: Invalid argument
hmm
Can you exit from chroot for a sec
type exit
and do lsblk -f and post the output
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda
├─sda1
├─sda2 ntfs New Volume 5EAE44BAAE448C89
└─sda3 ntfs New Volume 32EA5905EA58C6AF
sdb
└─sdb1 vfat FAT32 TGFJGFJ 8A55-40D5
sdc
└─sdc1 vfat FAT32 EOS_202305 190E-0774 112.8G 2% /run/archiso/bootmnt
nvme0n1
├─nvme0n1p1
├─nvme0n1p2 ntfs 6A7AE0D17AE09B59
├─nvme0n1p3 ext4 1.0 432fceab-dd7e-4a9d-9449-e79e7d21e3d7 52.9G 41% /mnt
│ /mnt
├─nvme0n1p4 swap 1 Swap df7acc0a-8cfd-425a-bd0e-bddb64473c46
├─nvme0n1p5 vfat FAT32 BOOT DC78-DF3C 1.1G 0% /mnt/boot/efi
│ /mnt/boot/efi
└─nvme0n1p6 vfat FAT32 A6A6-B4F2
Hmm, weird why are they mounted twice?
Do umount -R /mnt
Then mount them again as before
mount: /mnt/boot/efi: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.05.28 ~]$
done
run grub-install --target=x86_64-efi --efi-directory=/boot/efi
Then do grub-mkconfig -o /boot/grub/grub.cfg
Show any errors
[root@EndeavourOS /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi
Installing for x86_64-efi platform.
Installation finished. No error reported.
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
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.
ERROR: mkdir /var/lock/dmraid
Adding boot menu entry for UEFI Firmware Settings ...
done
ls /boot/efi again
EFI
EndeavourOs
No Grub
[root@EndeavourOS /]# ls /boot/efi
EFI
[root@EndeavourOS /]# ls /boot/efi/EFI/
endeavouros
[root@EndeavourOS /]#
Alright, guess it's pre-configured
okay
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0000,0005,0006,0007
Boot0000* endeavouros HD(5,GPT,5e2a7f22-cdbc-4917-8bf2-04574e3b8a9c,0x3a03c800,0x249800)/File(\EFI\endeavouros\grubx64.efi)
Boot0005* Windows Boot Manager HD(6,GPT,5adb5b4a-3b2e-43e6-84ad-3e20887d88a9,0x3a286000,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000069000100000010000000040000007fff0400
Boot0006* UEFI: JetFlashTranscend 4GB 1100, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,GPT,ab770dcd-f83f-4aaa-bc7a-3ba63b510818,0x800,0x789fdf)0000424f
Boot0007* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(1,GPT,394dbe81-ab4b-4190-a0f7-c004b70dd377,0x800,0xe5377df)0000424f
[root@EndeavourOS /]#
Alright, for now ignore the error and try to boot into endeavour
It's listed here tho 🤨
Maybe it resets or something i'm not sure how isos work exactly
What does efibootmgr output again
Do we have to do something with fstabv
from the iso
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0005,0006,0007
Boot0005* Windows Boot Manager HD(6,GPT,5adb5b4a-3b2e-43e6-84ad-3e20887d88a9,0x3a286000,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000069000100000010000000040000007fff0400
Boot0006* UEFI: JetFlashTranscend 4GB 1100, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,GPT,ab770dcd-f83f-4aaa-bc7a-3ba63b510818,0x800,0x789fdf)0000424f
Boot0007* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(1,GPT,394dbe81-ab4b-4190-a0f7-c004b70dd377,0x800,0xe5377df)0000424f
HMMM
No Endeavour
Okay
grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable
chroot first obv
okay
then grub-mkconfig -o /boot/grub/grub,cfg
output of efibootmgr?
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0005,0006,0007
Boot0005* Windows Boot Manager HD(6,GPT,5adb5b4a-3b2e-43e6-84ad-3e20887d88a9,0x3a286000,0x100000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000069000100000010000000040000007fff0400
Boot0006* UEFI: JetFlashTranscend 4GB 1100, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,GPT,ab770dcd-f83f-4aaa-bc7a-3ba63b510818,0x800,0x789fdf)0000424f
Boot0007* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(1,GPT,394dbe81-ab4b-4190-a0f7-c004b70dd377,0x800,0xe5377df)0000424f
ls /boot/efi/EFI
BOOT endeavouros
Alright, try to reboot and see if there's an entry
Oklay
Okay there is
But
Should I just exit as it says to boot into default mode?
There's probably an error in your fstab
Ugh
Back into the iso
:P
Mount root and boot but don't chroot
Do genfstab -U /mnt > /mnt/etc/fstab
Wait actually just one
To overwrite 🙂
Okay on it
permisision denied
Yes
Can you show me the exact command you did
Did you mount first
[liveuser@eos-2023.05.28 ~]$ genfstab -U /mnt > /mnt/etc/fstab
bash: /mnt/etc/fstab: Permission denied
yes
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/nvme0n1p3 /mnt
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/nvme0n1p5 /mnt/boot/efi
Same thing 🙂
[liveuser@eos-2023.05.28 ~]$ sudo genfstab -U /mnt | sudo tee /mnt/etc/fstab
# /dev/nvme0n1p3
UUID=432fceab-dd7e-4a9d-9449-e79e7d21e3d7 / ext4 rw,relatime 0 1
# /dev/nvme0n1p5 LABEL=BOOT
UUID=DC78-DF3C /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
[liveuser@eos-2023.05.28 ~]$
seems to have worked
Then run this again
[liveuser@eos-2023.05.28 ~]$ sudo genfstab -U /mnt | sudo tee /mnt/etc/fstab
# /dev/nvme0n1p3
UUID=432fceab-dd7e-4a9d-9449-e79e7d21e3d7 / ext4 rw,relatime 0 1
# /dev/nvme0n1p5 LABEL=BOOT
UUID=DC78-DF3C /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/nvme0n1p4 LABEL=Swap
UUID=df7acc0a-8cfd-425a-bd0e-bddb64473c46 none swap defaults 0 0
[liveuser@eos-2023.05.28 ~]$
Alright cool
Reboot?
Now try booting into endeavour
About the grub error, not sure what it is. But also for some reason can't mount the windows system reserved partition
So that grub can detect it
It shows windows?
➜ ~ sudo os-prober
[sudo] password for parthj:
/dev/nvme0n1p6@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
➜ ~ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
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.
Found Windows Boot Manager on /dev/nvme0n1p6@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Let me check
Yeah it does
Anddf the first partition in the ssd is not the efi for windows
It’s actually the last partiyion
Oh shit
I didn't even notice the last partition
LMAO
Sorry for the bad support, not my day ig xD
But still
Yeah lol
the layout is mega weird
hey man, that was insane. Thanks for taking out time.
0fficerk received a thank you cookie!
yeah true
Np, be sure to add [SOLVED] at the start of this thread's title
Okay, I want to do something in return for ur time. But I don't have international payment method. Can you dm me your email so I can atleast give u 100% off coupon to one of my paid apps?
Don't worry about it, I don't take payments for providing support, I like to do it for fun/learning/giving back to the community. Besides, I wouldn't be deserving of any payment for this one :)
But thanks for offering. Good luck!
That's really nice of you!! Thanks a lot
You're thanking too much ó_ò
@versed ocean could you please mark this as solved so people don't think this is still ongoing
Yes, Sorry. I forgot
