[SOLVED] d

Vastoren · 2026-05-31 17:34:21

d

Last edited by Vastoren (Today 20:14:32)

StarWolf3000 · 2026-06-01 05:30:09

https://wiki.archlinux.org/title/GRUB#W … I/GPT_mode

cryptearth · 2026-06-01 12:30:41

several points:
- /boot/efi - this should be avoided in your case because /boot is also its own partition
today it should either be /efi or /esp - or /boot - but not nested /boot/efi
- your /boot/efi says 0% FSUSE - given grub is about 35mb it should show as at least 1% - confirm that grub really is installed where you think it should
- /etc/grub/grub.cfg? i hope this is a typo as grub.cfg is supposed to be in /boot/grub/grub.cfg - or where you define --boot-directory= to at grub-install (which defaults to /boot when not given)
- booting across devices: your efi loads grub from sda - but you try to access nvme1 - you try to cross device boundaries - this was and still is always a problem as it requires grub to see other drives - check your bios for stuff like AHCI / AMD-RAID/ Intel-RST - it's likely grub misses a driver required to even find the nvme
- given nvme1 there's also a nvme0 - what's on it?
- multiple ESP - the uefi spec doesn't specify how to handle multiple ESP - could be your bios gets confused - try ONE esp and put all boot loaders and kernels+initrd on it so you have one central partition - should be preferable on the windows drive

Vastoren · 2026-06-01 16:20:18

d

Last edited by Vastoren (Today 20:13:10)

V1del · 2026-06-01 16:27:07

One ESP per drive should be fine, but drive detection caveats depending on what your UEFI will expose during early boot can be quite prevalent which is somewhat likely to be your current issue , if you actually want that kind of modularity then most UEFI implementations are going to break when you swap devices unless you populate the UEFI fallback path, which you can do if you install GRUB with the "--removable" flag.

You mentioned you can cd to the windows drive, can you cd there from the GRUB shell or is this after a successful boot?

Generally speaking the problem with UEFI issues is that you're very much at the mercy of whatever your vendor is doing, and since their modus operandi is to do the minimal work to ensure windows boots, it's somewhat likely that they only expose the drive the ESP was used from initially.

Last edited by V1del (2026-06-01 16:29:51)

Vastoren · 2026-06-01 16:35:58

d

Last edited by Vastoren (Today 20:13:17)

cryptearth · 2026-06-01 18:49:52

well - going "one ESP per drive" is what uefi is designed for: uefi scans the drives during POST and determines which it can read and load bootable code from
but the uefi spec doesn'T specify if or how the firmware will give along all drives to the loaded bootloader - or if and how an uefi complaint bootloader interacts with other drives within the same system
the most basic idea would be for a bootloader to load (or include) additional drivers to access other drives than the one it was loaded from - but i don't know if or how grub can do this
that's where my "one esp for the entire system - including kernels and initrd" comes from: i don't know exactly how windows boot works - but from what i understand and have read across multiple forums: windows uefi bootloader seems to be able to boot across multiple drives (there're several topics about "dual-boot windows install overwrote my linux bootloader on another driver" - this is where the general advice comes from: "when install windows disconnect all other drives" - to avoid exactly that) - but I'm not sure if or how this is limited to stuff like AHCI, NVMe, amd-fakeraid/intel-rst or even add-in cards with or even without OpRoms
point is: at your very setup grub seem to not be able to see the nvme where windows lives - for whatever reason - BUT: pushing grub + kernel + initrd all together on the same esp as windows gives you this: grub can load both linux and chain windows - and linux should be able in initrd phase to discover its own drive, mount it and switch_root to boot linux

as you seem to have 2x 500gb drives and use another drive as shared anyway: how about install both os on the same drive (no matter if the sata ssd or the nvme) but use the other drive as for /home or an exfat shared space

here's my setup:
one about 500gb-ish nvme (fdisk lists 465gib) with 32gb swap, 100gb arch, 250gb /home (actually stupidly big - could reduce to 100gb, too), 80gb for windows
8 3tb drives in a 24tb zfs pool (only for linux as windows zfs implementation isn't ready yet
i only use about 30gb of my /home (currently plus another 30gb for a zfs test suite) - so giving windows about 100gb more could be beneficial for one large game

anyway - back to topic
point is: your issue is: grub can't see the other drive - for whatever reason
possible idea: install grub in the same esp as the windows loader along the kernel and initrd (otherwise you will end up in the problem in reverse: grub can see windows but not /boot on the other drive holding the kernel and initrd)
OR
don't chain windows from grub but use uefi how it's intented: use the uefi os selector

Vastoren · 2026-06-01 21:15:25

d

Last edited by Vastoren (Today 20:13:23)

Vastoren · 2026-06-01 22:22:52

d

Last edited by Vastoren (Today 20:14:08)

cryptearth · 2026-06-01 22:33:18

hm - another idea: how and where do you install grub to EXACTLY?
i smell that the one shot after install grub is a different instance than what gets booted after windows was booted
check with efibootmgr
- before you reinstall grub
- after you reinstalled grub
- after you chained windows
also: clean everything from grub: /boot/grub, /boot/efi/grub and also mount and check the windows esp

your command has

--bootloader-id=GRUB

but you say you have

/boot/efi/EFI/Arch/...

this doesn't add up

it really smells you boot two different grub versions

Last edited by cryptearth (2026-06-01 22:38:58)

Vastoren · 2026-06-01 23:06:20

d

Last edited by Vastoren (Today 20:13:30)

cryptearth · 2026-06-02 05:24:50

hmm ...
do you use reboot or shutdown after windows start? reboot should cleanly shutdown windows and release and reset all hardware - when "shutdown" you could still run in some fast-boot remnants which keeps the nvme and the controller in a state which grub maybe can't handle correctly on your system?
also: your previous LS showed that not just the windows os nvme vanished but both nvme - this could hint towards some issue with how your system handles nvme after cold/warm reboot - which in turn again hints towards intel-rst or amd's equivalent

another "try the crowbar" idea: no matter if yiu already on the latest bios: just flash the latest version again - we once had a topic about a laptop whos owner reported some boot issues and reflashing the already installed bios somehow fixed it

Vastoren · 2026-06-02 21:33:53

d

Last edited by Vastoren (Today 20:13:52)

Vastoren · 2026-06-02 21:52:16

d

Last edited by Vastoren (Today 20:13:46)

cryptearth · 2026-06-03 01:20:31

well - if you actually did reclashed your bios this could explain why this option came back enabled if you had it disabled previously: because it's likely the default - sorry, that's my bad: i assumed that you already checked your bios for such option and had it disabled *lessons learned: next time ask the user to thoroughly recheck all settings deeply

as for why it worked first time after grub reinstall: on uefi grub usually calls efibootmgr to update the nvram if the bios - a possible idea could be that by doing so some flag gets triggered in the specific implementation of your boards uefi which causes a full slow-boot with full device discovery even when the fast start option is enabled - but this could only be answered by its dev - from who you likely will only get: "officialy we don't support linux anyway"

small friendly advice: please avoid full-quotes and reply to yourself when noone has replied yet - the mods appreciate the bbs to be kept somewhat clean

Vastoren · 2026-06-03 02:16:07

d

Last edited by Vastoren (Today 20:13:59)

Arch Linux

#1 2026-05-31 17:34:21

[SOLVED] d

#2 2026-06-01 05:30:09

Re: [SOLVED] d

#3 2026-06-01 12:30:41

Re: [SOLVED] d

#4 2026-06-01 16:20:18

Re: [SOLVED] d

#5 2026-06-01 16:27:07

Re: [SOLVED] d

#6 2026-06-01 16:35:58

Re: [SOLVED] d

#7 2026-06-01 18:49:52

Re: [SOLVED] d

#8 2026-06-01 21:15:25

Re: [SOLVED] d

#9 2026-06-01 22:22:52

Re: [SOLVED] d

#10 2026-06-01 22:33:18

Re: [SOLVED] d

#11 2026-06-01 23:06:20

Re: [SOLVED] d

#12 2026-06-02 05:24:50

Re: [SOLVED] d

#13 2026-06-02 21:33:53

Re: [SOLVED] d

#14 2026-06-02 21:52:16

Re: [SOLVED] d

#15 2026-06-03 01:20:31

Re: [SOLVED] d

#16 2026-06-03 02:16:07

Re: [SOLVED] d

Board footer