Oops - installed TW and lost Win7 - probably because of EUFI/legacy mixup

English Install/Boot/Login
1

Hi there,

Did an dual-boot install of the latest TW (20191101) and it all went well… except that grub cannot see my Win7 install on restart.
Hardware is Haswell-E era (X99+5820k).
No real idea whether Win7 was installed as EUFI or legacy, and can’t really recall what I installed TW as (which i suspect is the core of the problem).

So looking to see how I can recover the situation…?

Password:
linux-xxxx:~ # # os-prober
linux-xxxx:~ # # grub2-mkconfig -o /boot/grub2/grub.cfg
linux-xxxx:~ #

No useful response from these commands.

Options selected during install.
Selected two drives (of four) for the partitioner, with a separate root / home folders:
nvme drive for root (using the remaining 60GB - with no changes to existing partitions selected)
sandisk sata for home (using the remaining 192GB - with no changes to existing partitions selected)

I’ve been using TW for years, but always as a single boot on my laptop - this is the push to use it on my desktop (but wanting to keep Win7 for various reasons).

Is this situation recoverable for a non-expert?

Many thanks. Jbt

2

Hi
So no output from os-prober command (not sure why you have an extra #)?

Can you show the output from;


efibootmgr -v
fdisk -l
3

Thanks.
Probably a mistake my end in trying other commands i’d seen on the forum from searching.

linux-xxxx:~ # os-prober
linux-xxxx:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file …
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.3.7-1-default
Found initrd image: /boot/initrd-5.3.7-1-default
done
linux-xxxx:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file …
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.3.7-1-default
Found initrd image: /boot/initrd-5.3.7-1-default
done
linux-xxxx:~ # efibootmgr -v
If ‘efibootmgr’ is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf efibootmgr
linux-xxxx:~ # fdisk -l
Disk /dev/nvme0n1: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 960 EVO 250GB
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: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 468991 262144 128M Microsoft reserved
/dev/nvme0n1p3 468992 354174975 353705984 168.7G Microsoft basic data
/dev/nvme0n1p4 354174976 354191359 16384 8M BIOS boot
/dev/nvme0n1p5 354191360 488397134 134205775 64G Linux filesystem

Disk /dev/sda: 894.26 GiB, 960197124096 bytes, 1875385008 sectors
Disk model: SanDisk Ultra II
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: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Device Start End Sectors Size Type
/dev/sda1 34 262177 262144 128M Microsoft reserved
/dev/sda2 264192 1472724991 1472460800 702.1G Microsoft basic data
/dev/sda3 1472724992 1871190015 398465024 190G Linux filesystem
/dev/sda4 1871190016 1875384974 4194959 2G Linux swap

linux-xxxx:~ #

4

Hi
So it looks like windows is installed in UEFI and openSUSE installed in legacy (mbr) boot since you have;


/dev/nvme0n1p4 354174976 354191359     16384     8M BIOS boot

Also since efibootmgr isn’t installed… :wink:

So, if this is a fresh install of Tumbleweed, suggest a re-install. You need to ensure you boot in UEFI mode with the BIOS boot menu and then proceed with a re-install.

5

thanks, will give it a try now.

6

Up and running, thank you very much. Jbt