arvidjaar:
Yes. And you collected diagnostic information AFTER you unplugged additional HDD. And you never mentioned that you had additional HDD before I hinted at it. How do you expect someone to troubleshoot the problem without complete picture?
As I already told you - replace /dev/sda in /etc/default/grub_installdevice with stable device name. Like /dev/disk/by-id/ata-KINGSTON_SS200S330G_50026B72590E11D9 (according to previous BIS results; verify that it actually points to your correct disk). This makes sure grub is always installed on the correct disk. Then run “update-bootloader --reinit”, reboot and change boot order back in BIOS.
Without this modification grub will continue to be installed on “another HDD” as long as this HDD remains /dev/sda. You can theoretically replace /dev/sda with /dev/sdb, and it will work now , but experience shows that after some time users forget about it, add new disks and disk names change …
…sorry for not providing the HDD info (the hdd is mounted in fstab tbw
The rest you proposed works fine, booting now from the Kingston SSD again!
Many thanks to all for helping out.
suse_rasputin:
sudo inxi -zmF
[sudo] password for root:
System: Kernel: 5.13.1-1-default x86_64 bits: 64 Console: tty pts/0
Distro: openSUSE Tumbleweed 20210715
Machine: Type: Other-vm? Mobo: Gigabyte model: N3150ND3V serial: N/A
UEFI-[Legacy]: American Megatrends v: F5a date: 01/19/2018
Memory: RAM: total: 7.67 GiB used: 628.8 MiB (8.0%)
Array-1: capacity: 8 GiB slots: 2 EC: None
Device-1: A1_DIMM0 size: 4 GiB speed: 1600 MT/s
Device-2: A1_DIMM1 size: 4 GiB speed: spec: 65535 MT/s note: check
actual: 1600 MT/s
CPU: Info: Quad Core model: Intel Celeron N3150 bits: 64 type: MCP cache: L2: 1024 KiB
Speed: 1177 MHz min/max: 480/2080 MHz Core speeds (MHz): 1: 640 2: 640 3: 480
4: 480
Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated
Graphics
driver: i915 v: kernel
Display: server: X.org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa
tty: 96x49
Message: Advanced graphics data unavailable in console for root.
Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High
Definition Audio
driver: snd_hda_intel
Sound Server-1: ALSA v: k5.13.1-1-default running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: enp2s0 state: down mac: <filter>
Drives: Local Storage: total: 959.47 GiB used: 665.86 GiB (69.4%)
ID-1: /dev/sda vendor: Kingston model: SS200S330G size: 27.96 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD10EURX-63C57Y0 size: 931.51 GiB
Partition: ID-1: / size: 27.38 GiB used: 9.36 GiB (34.2%) fs: ext4 dev: /dev/sda2
Swap: ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) dev: /dev/sdb5
Sensors: System Temperatures: cpu: 26.8 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 136 Uptime: 1h 51m Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.03
From: https://www.gigabyte.com/de/Motherboard/GA-N3150N-D3V-rev-10/sp#sp
Use of licensed AMI UEFI BIOS
I don’t see no UEFI option in BIOS, but I’m mostly used to Dell BIOS…
hcvv
July 19, 2021, 1:55pm
#24
Either a system (BIOS) can do UEFI or it can not. If the system can doUEFI assume the system (BIOS) can still do legacy and it offers a setting for this.
When a system can use UEFI, you have the choice. Most will use UEFI, but it is no obligation. One thing is important though. You can only use one of them on your system. Thus when there is already an operating system (e.g. some MS Windows) on it, this is fixed. And you have to boot the openSUSE installation medium in the same mode (which is automatically done most of the time) and the installation of openSUSE (GRUB2) will have to use the same mode (which again is automatic).
Thus you can only change legacy/UEFI by changing all systems on it (most easy by starting all over again with a “wiped” system).
hcvv
July 19, 2021, 2:00pm
#25
As you have never posted your fstab, we can not really comment on that. In any case I will take “the hdd is mounted in fstab” with a pinch of salt.
fstab is in the output of avidjaars script
), thought it was irrelevant. I have no idea of this booting stuff… 