Hi, I have AMD desktop with 4 drives, and installation of TW works, but system doesn't boot. I have to press F12 and manually select UEFI opensuse-secureboot or opensuse item. The machine has - 2x 2TB NVMe - used as SW RAID0 for encrypted /home - 1x 1TB SSD for /boot/efi and encrypted LVM with / and swap - 1x 5TB HDD for internal backups (rsync with cron) Interestingly, when I boot install USB drive, I randomly see SSD as sda or sdb, and HDD as sdb or sda. Anyway, regardless I place /boot/efi on beginning of SSD or 1st NVMe, BIOS has troubles to find boot openSUSE. Also, when I press F12 to manually select boot device, I sometimes get info that the firmware was reset (Problem with CMOS battery or so?), but otherwise everything seems correct there. When I install Leap with above setup, it works. I have similar setup (2x NVMe, 1st with /boot/efi and encrypted LVM with /and swap, and 2nd with encrypted / home) on another machine, and I use to use setup with /boot/efi and rest in encrypted LVM for years, so I'm sure this setup works reliably. So I wonder if I do something wrong or I face some issue with motherboard of my desktop...? Yours, V. -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 14.02.2024 18:05, Vojtěch Zeisek wrote:
Hi, I have AMD desktop with 4 drives, and installation of TW works, but system doesn't boot. I have to press F12 and manually select UEFI opensuse-secureboot or opensuse item. The machine has - 2x 2TB NVMe - used as SW RAID0 for encrypted /home - 1x 1TB SSD for /boot/efi and encrypted LVM with / and swap - 1x 5TB HDD for internal backups (rsync with cron) Interestingly, when I boot install USB drive, I randomly see SSD as sda or sdb, and HDD as sdb or sda. Anyway, regardless I place /boot/efi on beginning
https://bugzilla.suse.com/show_bug.cgi?id=1216070
of SSD or 1st NVMe, BIOS has troubles to find boot openSUSE. Also, when I press F12 to manually select boot device, I sometimes get info that the firmware was reset (Problem with CMOS battery or so?), but otherwise everything seems correct there. When I install Leap with above setup, it works. I have similar setup (2x NVMe, 1st with /boot/efi and encrypted LVM with /and swap, and 2nd with encrypted / home) on another machine, and I use to use setup with /boot/efi and rest in encrypted LVM for years, so I'm sure this setup works reliably. So I wonder if I do something wrong or I face some issue with motherboard of my desktop...?
There is nothing wrong. The order of disk enumeration (and actually any other device) was never guaranteed to remain stable across reboots. Except some corner cases when device names were preallocated based on device position (like IDE disks).
Vojtěch Zeisek composed on 2024-02-14 16:05 (UTC+0100):
Interestingly, when I boot install USB drive, I randomly see SSD as sda or sdb, and HDD as sdb or sda....
https://bugzilla.opensuse.org/show_bug.cgi?id=1216070 Assignment of /dev/sd* has altered dramatically "resolved fixed" 3 months ago TW's kernel configuration has some differences from Leap's, beside incorporating new features. These can affect device enumeration, which affects device assignments.
...Anyway, regardless I place /boot/efi on beginning of SSD or 1st NVMe, BIOS has troubles to find boot openSUSE. Also, when I press F12 to manually select boot device, I sometimes get info that the firmware was reset (Problem with CMOS battery or so?), but otherwise everything seems correct there.
UEFI BIOS have a rather wide variety of behaviors that distinguish them from others. They are an art form. :p Be glad yours has an F12 menu that works. :)
When I install Leap with above setup, it works. I have similar setup (2x NVMe, 1st with /boot/efi and encrypted LVM with /and swap, and 2nd with encrypted / home) on another machine, and I use to use setup with /boot/efi and rest in encrypted LVM for years, so I'm sure this setup works reliably. So I wonder if I do something wrong or I face some issue with motherboard of my desktop...?
It's unlikely you are doing anything that is technically "wrong". Most reliable setup I have found is to install only one Gnu/Linux bootloader per PC. This includes having only one ESP filesystem, KISS technology. :) All except one of my UEFI PCs boot using TW's Grub-efi. The other UEFI (from which I type this, which has 5 openSUSE installations), and the older, all boot from openSUSE 13.1's (or older) Legacy Grub, some with upwards of 40 Linux installations, and only about 1 or so with less than 4. I try to avoid fixing what ain't broke. :) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** multibooting for over 3 decades ** a11y rocks! Felix Miata
Thanks for hints. Dne středa 14. února 2024 22:46:40 CET, Felix Miata napsal(a):
Vojtěch Zeisek composed on 2024-02-14 16:05 (UTC+0100):
Interestingly, when I boot install USB drive, I randomly see SSD as sda or sdb, and HDD as sdb or sda....
https://bugzilla.opensuse.org/show_bug.cgi?id=1216070 Assignment of /dev/sd* has altered dramatically "resolved fixed" 3 months ago TW's kernel configuration has some differences from Leap's, beside incorporating new features. These can affect device enumeration, which affects device assignments.
...Anyway, regardless I place /boot/efi on beginning of SSD or 1st NVMe, BIOS has troubles to find boot openSUSE. Also, when I press F12 to manually select boot device, I sometimes get info that the firmware was reset (Problem with CMOS battery or so?), but otherwise everything seems correct there.
UEFI BIOS have a rather wide variety of behaviors that distinguis them from others. They are an art form. :p Be glad yours has an F12 menu that works. :)
When I install Leap with above setup, it works. I have similar setup (2x NVMe, 1st with /boot/efi and encrypted LVM with /and swap, and 2nd with encrypted / home) on another machine, and I use to use setup with /boot/efi and rest in encrypted LVM for years, so I'm sure this setup works reliably. So I wonder if I do something wrong or I face some issue with motherboard of my desktop...?
It's unlikely you are doing anything that is technically "wrong". Most reliable setup I have found is to install only one Gnu/Linux bootloader per PC. This includes having only one ESP filesystem, KISS technology. :) All except one of my UEFI PCs boot using TW's Grub-efi. The other UEFI (from which I type this, which has 5 openSUSE installations), and the older, all boot from openSUSE 13.1's (or older) Legacy Grub, some with upwards of 40 Linux installations, and only about 1 or so with less than 4. I try to avoid fixing what ain't broke. :)
I'm not sure if the problem is directly caused by chaos in SD assignment (due to occasional complain of BIOS). Anyway, I'll play bit with the fixes mentioned in bug #1216070 (so far no success). -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
participants (3)
-
Andrei Borzenkov -
Felix Miata -
Vojtěch Zeisek