I installed openSUSE Tumbleweed, and it doesn’t boot to openSUSE. The Plymouth splash is still displaying the previous OS (Fedora) with spinning progress icon but stalls, which I don’t understand. The only way I can actually boot to the OS if I interrupt the startup and select the boot device where the OS is installed, which is odd since I only have one HDD and I still see the previous OS (Fedora) as a selection.
These are the select boot device(s):
SATA 2: WDC
After selecting openSUSE it boots fine, and I can sign in as normal.
The machine is a Lenovo Ideacenter 200.
This is from a KVM virtual machine, using GPT partitioning:
# fdisk -l /dev/sda
Disk /dev/sda: 50 GiB, 53687091200 bytes, 104857600 sectors
Disk model: QEMU HARDDISK
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 89282E03-D56D-473E-AE85-1D120BF9D351
Device Start End Sectors Size Type
/dev/sda1 2048 616447 614400 300M EFI System
/dev/sda2 616448 1640447 1024000 500M Linux filesystem
/dev/sda3 1640448 2664447 1024000 500M Linux filesystem
/dev/sda4 2664448 104857566 102193119 48.7G Linux LVM
That’s actually setup for legacy booting, with partition 2 as the “active” partition. But GPT partitioning (which you are using) is different, and there isn’t an actual “active” flag for a partition. As you can see, “fdisk” does not show an active partition.
I can, instead, use “parted”:
# parted /dev/sda print
Model: ATA QEMU HARDDISK (scsi)
Disk /dev/sda: 53.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 316MB 315MB fat32 boot, esp
2 316MB 840MB 524MB ext2 legacy_boot
3 840MB 1364MB 524MB ext2
4 1364MB 53.7GB 52.3GB lvm
That shows a “legacy_boot” flag for partition 2, which is supposed to emulate the active flag. But “fdisk” does not show it, as you could see in the earlier output.