You are not logged in.
Pages: 1
I did a fresh install and formatted my drive to be completely empty with no Windows install.
I made 3 partitions:
/dev/nvme0n1p1 as EFI File System 1 GB
/dev/nvme0n1p2 as Linux(xroot86_64) 600GB
/dev/nvme0n1p3 as linux swap
I did mount /dev/nvme0n1p2 /mnt
mount --mkdir /dev/nvme0n1p1 /mnt/boot
swapon /dev/nvme0n1p3
I generated an fstab file and then arch-chroot /mnt
For bootloader, I chose grub and did grub-install --target=x86_64-efi --efi-directory=/mnt/boot/efi --bootloader-id=GRUB --removable
and then grub-mkconfig -o /boot/grub/grub.cfg
And I have tried it without removable.
efibootmgr -v shows 0000 grub, 0001 windows boot manager, 0002 rEFIND Boot Manager (i tried this after messing with grub and still didnt work), 0004 USB Drive UEFI, with boot order being 0000,0004,0001,0002
There's no customized boot path option in settings.
Last edited by smileBrandon (2024-03-09 06:10:50)
Offline
That efi-directory is wrong once you're inside the chroot at /mnt. Even outside the chroot that wouldn't be right, as you're pointing at a dir inside the filesystem instead of the mount point.
Last edited by Scimmia (2024-03-09 10:52:48)
Offline
I've also done /boot/efi without /mnt and still had the same issue.
Offline
Your EFI partition is mounted at /boot, not /boot/efi
Offline
/mnt/boot becomes /boot when arch-chrooted into your install. Your grub-install command should specify efi-directory=/boot.
oops. I didn't see Fuxino's comment before pressing submit.
Last edited by kermit63 (2024-03-09 14:05:24)
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
Alright, I did another installation just to make sure everything was set right, not installing refind this time, and doing the grub install as grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB and the same issue persists.
Offline
If you install GRUB and reboot (not power cycle) does it work then?
Last edited by AaAaAAaaAAaARCH (2024-03-09 20:13:19)
Offline
I did the grub-install with --removable and I am still getting "No bootable device found" and when I select "Boot from EFI File" under Boot Options (F9) it says "No Valid File System Available."
Offline
Are there old EFI files from previous attempts you have not deleted?
What is the efi file named, maybe omit bootloader-id when using removable? "grub-install --target=x86_64-efi --efi-directory=/boot --removable"
Also show us the fstab so we can be sure it was generated from the right path
Last edited by AaAaAAaaAAaARCH (2024-03-09 20:17:21)
Offline
Do I have to write the output by hand or is there a way to copy the output to the USB?
I've formatted the entire drive each install, so there shouldn't be any EFI files.
And no bootloader id didn't resolve the issue either.
Last edited by smileBrandon (2024-03-09 20:51:02)
Offline
# /dev/nvme0n1p1
UUID=6140-C852 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepade=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/nvme0n1p2
UUID = 7bd5d89f-ab86-4305-8412-981d0d34be4e / ext4 rw,relatime 0 1
# /dev/nvme0n1p3
UUID=c4de447c-dd06-4178-97ac-38ccaf5af63f none swap defaults 0 0 Offline
1. check using "fdisk -l" that your EFI partition actually has an EFI Type and not "Microsoft basic data"
2. check bios settings, make sure that booting from EFI harddrives is enabled.
There is no need to re-install the os every time. Just do the following;
mount /dev/nvme0n1p2 /mnt
mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mnt
rm -rf /boot/EFI
grub-install --target=x86_64-efi --efi-directory=/boot --removable
grub-mkconfig -o /boot/grub/grub.cfg
exit
reboot (dont power cycle)
Last edited by AaAaAAaaAAaARCH (2024-03-09 21:18:34)
Offline
My EFI Partition has a disklabel type of dos and disk identifier is 0x00000000, and there is no such option as you listed in #2. It just gives me my UEFI Boot Order with USB Flash Drive, OS Boot Manager, USB CD/ROM and that's it.
Offline
"fdisk -l" should say something like
Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ########
Units: sectors of 1 * #### = ### bytes
Sector size (logical/physical): ###
I/O size (minimum/optimal): ###
Disklabel type: gpt
Disk identifier: ####
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 3370760191 3369709568 1.6T Linux filesystemFollow formatting instructions on.
https://wiki.archlinux.org/title/EFI_system_partition
IF you are using DOS, which is not recommended, then it might be called something other than EFI (like EF)
Last edited by AaAaAAaaAAaARCH (2024-03-09 21:52:25)
Offline
DISK /dev/nvme0n1: 953.87 GiB, 1024209543168, 250051158 sectors
Disk model: WDC PC SN730 SDBPNTY-1T00-1006
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Diskidentifier: 90619E96-FA2F-4AA2-8E5C-86A63D143F28
Device Start End Sectors Size Type
/dev/nvme0n1p1 256 262399 262144 1G EFI System
/dev/nvme0n1p2 262400 118227199 117964800 450G Linux root (x86-64)
/dev/nvme0n1p3 118227200 122421503 4194304 16G Linux SwapLast edited by smileBrandon (2024-03-09 22:01:38)
Offline
I took pictures of my fdisk -l /etc/fstab efibootmgr -v and lsblk -f:
https://postimg.cc/gallery/srYypHy
Offline
Did you verify your boot mode? https://wiki.archlinux.org/title/Installation_guide
cat /sys/firmware/efi/fw_platform_size
if you have done everything correctly and its still not working, you could try to partition similarly to your usb drive (DOS and 16 or 32 FAT)
Offline
So I had given up and tried to do an EndeavourOS install and that didn't work, then tried Windows only for me to not find my hard drive. So I did F2 for System Diagnostics and "No Hard Drive Detected" so I've gotta get that figured out.
Offline
Yeah, hard drive died and it must've been when I updated my BIOS. Having to buy a new one.
Offline
The optimal logical sector size was what caused my nvme to be unrecognizable so no matter what I did with the install, it was never going to work. I got a new hard drive and the same thing happened and so I reset it back to default (512) and it recognized my new hard drive, so I'm going to disassemble my laptop again and see if it fixes the old nvme.
Yep: changing the size to 4096 (best) was what caused my nvme to not be recognized so I am going to try to reinstall.
Last edited by smileBrandon (2024-03-11 19:00:15)
Offline
Pages: 1