LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 07-14-2021, 02:20 AM   #1
jan42
LQ Newbie
 
Registered: Jul 2021
Posts: 4

Rep: Reputation: Disabled
OpenSuse LEAP - boot menu - dual boot mit win10


Hi,


on partition sda2 is a win10 System. This should be in boot menu / bootloader grub2. Down you find output to understand the problem. Maybe someone can tell me what to do.


Is something with UEFI / gpt wrong - got to change that? How can I do this from openSuse bash?

DESKTOP-39MBRPL:~ # parted -s /dev/sda print
Model: ATA SATA SSD (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 577MB 576MB primary ntfs boot, type=07
2 577MB 119GB 118GB primary ntfs type=07
4 119GB 119GB 524MB primary fat16 esp, type=ef
3 119GB 120GB 564MB primary ntfs diag, type=27

DESKTOP-39MBRPL:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 549M 0 part
├─sda2 8:2 0 110.2G 0 part
├─sda3 8:3 0 538M 0 part
└─sda4 8:4 0 500M 0 part /boot/efi
sdb 8:16 0 298.1G 0 disk
└─sdb1 8:17 0 298.1G 0 part
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 1.8T 0 part
├─sdc2 8:34 0 500M 0 part
└─sdc3 8:35 0 77G 0 part
├─system-swap 254:0 0 2G 0 lvm [SWAP]
├─system-root 254:1 0 35G 0 lvm /
└─system-home 254:2 0 40G 0 lvm /home
DESKTOP-39MBRPL:~ #

DESKTOP-39MBRPL:~ # bootctl status
File system "/boot/efi" is not on a GPT partition table.
System:
Firmware: n/a (n/a)
Secure Boot: disabled
Setup Mode: user

Current Loader:
Product: n/a
ESP: n/a
File: └─n/a

Boot Loader Binaries:
ESP: Cannot find or access mount point of ESP.

Boot Loader Entries in EFI Variables:


Hier habe ich schon einmal ein paar custom entries hinzugefügt. Funktionieren aber alle nicht (no filesystem).

DESKTOP-39MBRPL:~ # cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry "hd1,0 Windows 10" {
set root='(hd1,0)'
chainloader /EFI/microsoft/BOOT/Windows.efi
}
menuentry "hd1,1 Windows 10" {
set root='(hd1,1)'
chainloader /EFI/microsoft/BOOT/Windows.efi
}
menuentry "hd1,2 Windows 10" {
set root='(hd1,2)'
chainloader /EFI/microsoft/BOOT/Windows.efi
}
menuentry "hd1,3 Windows 10" {
set root='(hd1,3)'
chainloader /EFI/microsoft/BOOT/Windows.efi
}
 
Old 07-14-2021, 09:06 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,311
Blog Entries: 28

Rep: Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137Reputation: 6137
Welcome to LQ.

Please surround any terminal output with "code" tags which become available when you click the "Advanced" button beneath the compose/edit post window. It makes terminal output much easier to read.

If I understand your question correctly, the Windows side is not visible in GRUB. Have you tried running update-grub?

Also, what is the output this command when in OpenSUSE?

Code:
fdisk -l
 
Old 07-15-2021, 03:35 AM   #3
petelq
Member
 
Registered: Aug 2008
Location: Yorkshire
Distribution: openSUSE(Leap and Tumbleweed) and a (not so) regularly changing third and fourth
Posts: 627

Rep: Reputation: Disabled
You should also make sure that os-prober is active. Check it in yast2>bootloader.
 
Old 07-15-2021, 03:38 AM   #4
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,799
Blog Entries: 1

Rep: Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066
Please execute bootinfoscript, susepaste its output, and paste the resulting URL here.
 
Old 07-15-2021, 03:40 AM   #5
jan42
LQ Newbie
 
Registered: Jul 2021
Posts: 4

Original Poster
Rep: Reputation: Disabled
This command I've send already several times. But it did not help.
grub-mkconfig -o /boot/grub/grub.cfg

os probe ist active, yes, but I think it just does not detect the win10 partition as bootable for some reason. That's the problem I guess
 
Old 07-15-2021, 03:42 AM   #6
jan42
LQ Newbie
 
Registered: Jul 2021
Posts: 4

Original Poster
Rep: Reputation: Disabled
RESULT.txt

Quote:
Originally Posted by mrmazda View Post
Please execute bootinfoscript, susepaste its output, and paste the resulting URL here.

Boot Info Script 0.78 [09 October 2019]


============================= Boot Info Summary: ===============================

=> Windows 7/8/2012 is installed in the MBR of /dev/sda.
=> Windows 7/8/2012 is installed in the MBR of /dev/sdb.
=> libparted MBR boot code is installed in the MBR of /dev/sdc.

sda1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD

sda2: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /Windows/System32/winload.exe

sda3: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sda4: __________________________________________________________________________

File system: vfat
Boot sector type: FAT16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/boot/MokManager.efi /efi/boot/bootx64.efi
/efi/boot/fallback.efi /efi/opensuse/MokManager.efi
/efi/opensuse/grub.efi /efi/opensuse/grubx64.efi
/efi/opensuse/shim.efi /efi/opensuse/grub.cfg

sdb1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdc1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdc2: __________________________________________________________________________

File system: vfat
Boot sector type: FAT16
Boot sector info: According to the info in the boot sector, sdc2 starts
at sector -550445056. But according to the info from
fdisk, sdc2 starts at sector 3744522240.
Operating System:
Boot files: /efi/boot/MokManager.efi /efi/boot/bootx64.efi
/efi/boot/fallback.efi /efi/opensuse/MokManager.efi
/efi/opensuse/grub.efi /efi/opensuse/grubx64.efi
/efi/opensuse/shim.efi /efi/opensuse/grub.cfg

sdc3: __________________________________________________________________________

File system: LVM2_member
Boot sector type: -
Boot sector info:

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: SATA SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 1,126,399 1,124,352 7 NTFS / exFAT / HPFS
/dev/sda2 1,126,400 232,310,783 231,184,384 7 NTFS / exFAT / HPFS
/dev/sda3 233,336,832 234,438,655 1,101,824 27 Hidden NTFS (Recovery Environment)
/dev/sda4 232,310,784 233,334,783 1,024,000 ef EFI (FAT-12/16/32)


Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: WDC WD3200AVVS-5
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 2,048 625,139,711 625,137,664 7 NTFS / exFAT / HPFS


Drive: sdc _____________________________________________________________________
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS5C302
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 2,048 3,744,522,239 3,744,520,192 7 NTFS / exFAT / HPFS
/dev/sdc2 3,744,522,240 3,745,546,239 1,024,000 ef EFI (FAT-12/16/32)
/dev/sdc3 3,745,546,240 3,907,029,167 161,482,928 8e Linux LVM


"blkid" output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/mapper/system-home 295d9f46-99f9-4fb3-9c52-2aa6db3b90f3 xfs
/dev/mapper/system-root 19ef440e-cc85-4711-856c-fd6e05df5651 btrfs
/dev/mapper/system-swap 51926bea-700c-4eeb-9335-df6d119789c2 swap
/dev/sda1 90224B58224B4288 ntfs System-reserviert
/dev/sda2 BEFA4E35FA4DE9EB ntfs Win 10
/dev/sda3 966EA74A6EA721CB ntfs
/dev/sda4 2871-3666 vfat
/dev/sdb1 4CE20C32E20C2336 ntfs Volume
/dev/sdc1 12C2892BC289145F ntfs Backup
/dev/sdc2 777C-0D78 vfat
/dev/sdc3 nz3TX3-Y69y-kG0w-xPnL-pnTH-4aI3-8kWojN LVM2_member

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root 9 Jul 15 08:31 ata-Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 ata-SATA_SSD_5111904253321059 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-SATA_SSD_5111904253321059-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-SATA_SSD_5111904253321059-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-SATA_SSD_5111904253321059-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-SATA_SSD_5111904253321059-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 Jul 15 08:31 ata-WDC_WD3200AVVS-56L2B0_WD-WCAV16862008 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 ata-WDC_WD3200AVVS-56L2B0_WD-WCAV16862008-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-name-system-home -> ../../dm-2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-name-system-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-name-system-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-uuid-LVM-3S4BKXzlOX4leOBWJUfNIZopSyYHmZ4rGJ6XN6GBAenmAsWN5m2mENLvrxC8KefB -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-uuid-LVM-3S4BKXzlOX4leOBWJUfNIZopSyYHmZ4rvEG4lQopEcM7ldru3j7wZkAni6tJwbbj -> ../../dm-2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 dm-uuid-LVM-3S4BKXzlOX4leOBWJUfNIZopSyYHmZ4rwWn0lXFhCbL98BVRGWrPqUJqpiv0mebK -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 lvm-pv-uuid-nz3TX3-Y69y-kG0w-xPnL-pnTH-4aI3-8kWojN -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-0ATA_Hitachi_HDS5C302_ML4230F33Y9H3K -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-0ATA_SATA_SSD_5111904253321059 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_SATA_SSD_5111904253321059-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_SATA_SSD_5111904253321059-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_SATA_SSD_5111904253321059-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_SATA_SSD_5111904253321059-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-0ATA_WDC_WD3200AVVS-5_WD-WCAV16862008 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-0ATA_WDC_WD3200AVVS-5_WD-WCAV16862008-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-1ATA_Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_Hitachi_HDS5C3020ALA632_ML4230F33Y9H3K-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-1ATA_SATA_SSD_5111904253321059 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_SATA_SSD_5111904253321059-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_SATA_SSD_5111904253321059-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_SATA_SSD_5111904253321059-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_SATA_SSD_5111904253321059-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-1ATA_WDC_WD3200AVVS-56L2B0_WD-WCAV16862008 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-1ATA_WDC_WD3200AVVS-56L2B0_WD-WCAV16862008-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-35000cca369f798e3 -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-35000cca369f798e3-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-35000cca369f798e3-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-35000cca369f798e3-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-350014ee15889e186 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-350014ee15889e186-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-SATA_Hitachi_HDS5C302_ML4230F33Y9H3K -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_Hitachi_HDS5C302_ML4230F33Y9H3K-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-SATA_SATA_SSD_5111904253321059 -> ../../sda
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_SATA_SSD_5111904253321059-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_SATA_SSD_5111904253321059-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_SATA_SSD_5111904253321059-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_SATA_SSD_5111904253321059-part4 -> ../../sda4
lrwxrwxrwx 1 root root 9 Jul 15 08:31 scsi-SATA_WDC_WD3200AVVS-5_WD-WCAV16862008 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 scsi-SATA_WDC_WD3200AVVS-5_WD-WCAV16862008-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Jul 15 08:31 wwn-0x5000cca369f798e3 -> ../../sdc
lrwxrwxrwx 1 root root 10 Jul 15 08:31 wwn-0x5000cca369f798e3-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jul 15 08:31 wwn-0x5000cca369f798e3-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 15 08:31 wwn-0x5000cca369f798e3-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 9 Jul 15 08:31 wwn-0x50014ee15889e186 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jul 15 08:31 wwn-0x50014ee15889e186-part1 -> ../../sdb1

========================= "ls -R /dev/mapper/" output: =========================

/dev/mapper:
control
system-home
system-root
system-swap

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/mapper/system-home /home xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
/dev/mapper/system-root / btrfs (rw,relatime,space_cache,subvolid=267,subvol=/@/.snapshots/1/snapshot)
/dev/mapper/system-root /.snapshots btrfs (rw,relatime,space_cache,subvolid=266,subvol=/@/.snapshots)
/dev/mapper/system-root /boot/grub2/i386-pc btrfs (rw,relatime,space_cache,subvolid=265,subvol=/@/boot/grub2/i386-pc)
/dev/mapper/system-root /boot/grub2/x86_64-efi btrfs (rw,relatime,space_cache,subvolid=264,subvol=/@/boot/grub2/x86_64-efi)
/dev/mapper/system-root /opt btrfs (rw,relatime,space_cache,subvolid=263,subvol=/@/opt)
/dev/mapper/system-root /root btrfs (rw,relatime,space_cache,subvolid=262,subvol=/@/root)
/dev/mapper/system-root /srv btrfs (rw,relatime,space_cache,subvolid=261,subvol=/@/srv)
/dev/mapper/system-root /tmp btrfs (rw,relatime,space_cache,subvolid=260,subvol=/@/tmp)
/dev/mapper/system-root /usr/local btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/usr/local)
/dev/mapper/system-root /var btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@/var)
/dev/sda4 /boot/efi vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)


========================= sda4/efi/opensuse/grub.cfg: ==========================

--------------------------------------------------------------------------------
set btrfs_relative_path="yes"
search --fs-uuid --set=root 19ef440e-cc85-4711-856c-fd6e05df5651
set prefix=(${root})/boot/grub2
source "${prefix}/grub.cfg"
--------------------------------------------------------------------------------

========================= sdc2/efi/opensuse/grub.cfg: ==========================

--------------------------------------------------------------------------------
set btrfs_relative_path="yes"
search --fs-uuid --set=root 548335c1-6ab7-4ab3-91dc-456f4196902e
set prefix=(${root})/boot/grub2
source "${prefix}/grub.cfg"
--------------------------------------------------------------------------------

=============================== StdErr Messages: ===============================

./bootscript: line 2553: 83886080S: value too great for base (error token is "83886080S")
mdadm: No arrays found in config file or automatically
 
Old 07-15-2021, 04:33 AM   #7
jan42
LQ Newbie
 
Registered: Jul 2021
Posts: 4

Original Poster
Rep: Reputation: Disabled
output fdisk -l

Quote:
Originally Posted by frankbell View Post
Welcome to LQ.

Please surround any terminal output with "code" tags which become available when you click the "Advanced" button beneath the compose/edit post window. It makes terminal output much easier to read.

If I understand your question correctly, the Windows side is not visible in GRUB. Have you tried running update-grub?

Also, what is the output this command when in OpenSUSE?

Code:
fdisk -l

DESKTOP-39MBRPL:~ # fdisk -l
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: SATA SSD
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: dos
Disk identifier: 0x0bbb2e03

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT
/dev/sda2 1126400 232310783 231184384 110.2G 7 HPFS/NTFS/exFAT
/dev/sda3 233336832 234438655 1101824 538M 27 Hidden NTFS WinRE
/dev/sda4 232310784 233334783 1024000 500M ef EFI (FAT-12/16/32)

Partition table entries are not in disk order.


Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: WDC WD3200AVVS-5
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: dos
Disk identifier: 0x1df62ed8

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 625139711 625137664 298.1G 7 HPFS/NTFS/exFAT


Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Hitachi HDS5C302
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: dos
Disk identifier: 0x0001bf7a

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 3744522239 3744520192 1.8T 7 HPFS/NTFS/exFAT
/dev/sdc2 3744522240 3745546239 1024000 500M ef EFI (FAT-12/16/32)
/dev/sdc3 3745546240 3907029167 161482928 77G 8e Linux LVM


Disk /dev/mapper/system-root: 35 GiB, 37580963840 bytes, 73400320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/system-swap: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/system-home: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Old 07-16-2021, 12:07 AM   #8
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,799
Blog Entries: 1

Rep: Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066Reputation: 2066
The combination of LVM, encryption and BTRFS makes this too complicated for me to be of much help in understanding what is happening, or not. It may be that all that is necessary to fix this is to open YaST -> Bootloader to make sure probe foreign OS is selected, then save. To force a save, some change in Bootloader is necessary. If probe is already selected, then try changing just the timeout by one second up or down to cause a save on exit.
 
Old 07-20-2021, 08:15 AM   #9
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,492

Rep: Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488Reputation: 2488
Your bootinfoscript output shows windows boot code in the MBR of sda and sdb indicating it is a Legacy install.
The output also shows Disklabel type: dos. For windows to boot in EFI mode it needs to be on a GPT partition so given that you have Opensuse installed EFI, a Grub EFI install will not boot a windows Legacy install. Even though you have apparently created an EFI partition on sda (windows install?) it is not on a GPT drive. Why this is necessary is something you will need to ask microsoft about.

If you look at the EFI partition output, there are no EFI files for windows so even if you had a correct entry in grub.cfg, it would not boot windows. THe correct EFI file in the Grub chainloader line is: chainloader /EFI/Microsoft/Boot/bootmgfw.efi

The set root line for an EFI install of windows is generally the UUID of the EFI partition rather than something like the Grub entry:
hd0,1

Since you have windows code in the MBR of sda, you should be able to access the BIOS firmware and set that drive to first boot in the BOOT OPTIONS to boot windows, and then change it to sdc to boot Opensuse. The reason for this is the error in your installation, mixing a Legacy install with an EFI install.

I don't usee LVM or btrfs so I don't know what impact that would have.
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: openSUSE Leap 15.0 Reached End of Life, Upgrade to openSUSE Leap 15.1 Now LXer Syndicated Linux News 0 12-01-2019 09:21 AM
LXer: openSUSE Leap 42.3 Linux OS Reached End of Life, Upgrade to openSUSE Leap 15.1 LXer Syndicated Linux News 0 06-30-2019 01:54 AM
LXer: openSUSE Leap 42.2 is out, how to upgrade safely from openSUSE Leap 42.1 LXer Syndicated Linux News 0 11-17-2016 07:18 AM
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 when trying x11 forwarding Sean1988 Linux - Newbie 2 05-12-2014 05:35 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 03:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration