EFI problem or damaged?

Support
1

I’ve a strange problem concerning my EFI.
I deed many installations of Manjaro and Win on two separate NVME disk (Disk0 PCIe 4x4 Disk1 PCIe 3x4) Manjaro being hallways on Disk0 following different mode but the problem persist.
The Manjaro ssd boot as nvme0n1 or nvme1n1 randomly.
Every installation I clean with efibootmgr both the boot manager and the two disk related but I’m not able to solve
Last week I deed install after cleaning with efibootmgr and nuked both disk, removed the disk1 disk and installed Manjaro first on disk0, than I removed the disk and inserted the the disk1 and installed Win 11. After I’ve inserted Manjaro in disk0.
But after a while again the problem with nvme0n1 and nvme1n1 reappear, plus I dont like Win was seeing EFI of Manjaro as disk D:
So yesterday I deed again a reinstall, after cleaning again with efibootmgr and installed Win first on disk1, removed the disk and installed Manjaro on disk0, after that the lenovo logo disappeared from beginning of loading Win and after the same problem of changing nvme0n1 to nvme1n1 start again…
Win correctly see disk0 (Manjaro) and disk1 (Win) on disk management
so, am I doing something wrong? Any way to solve this editing some file?
Hope I was able to explain my problem…

Edit: Notebook Lenovo ThinkPad P1 Gen4i no NVidia on board, only Intel iGPU

2

I suggest reading

https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Troubleshooting

:footprints:

3

You should only need to run sudo update-grub in manjaro, with both drives connected. This should set manjaro as default and give you a menu to start windows.

4

If your machine has more than one drive sharing a naming scheme, the order in which their corresponding device nodes are added is arbitrary. This may result in block device names (e.g. /dev/sda and /dev/sdb, /dev/nvme0n1 and /dev/nvme1n1, /dev/mmcblk0 and /dev/mmcblk1) switching around on each boot, culminating in an unbootable system, kernel panic, or a block device disappearing

https://wiki.archlinux.org/title/persistent_block_device_naming

Block device names will never be consistent. It is meant to be temporary and can change on every boot, depending on which device was caught first.

5

thanks, I will have a look in the evening

6

thanks, does it means that is normal than?

7

well, I deed many times but does not make any change…

8

Yes, in deed. My answer was indicating that it is normal. In the old days it was consistent, hda/sda was always hda/sda, but nowadays it is not. The reason is mainly comming from the server market, where a lot of disks needs to be managed. Windows does it like in the old days, since it used mainly on the desktop.

2 Likes
9

uh, thanks, it was driving me mad from long time… :crazy_face:

10

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.