Dualboot woes tumbleweed/windows

Serpico · November 9, 2024, 4:53pm

Hello, I have spent the past few days trying out different OS, namely linux variants and BSD’s. I have installed openSUSE Tumbleweed as from my testing it has been the one I have liked the most, however I am instantly having an issue with dualboot

My initial approach
Leave my current windows 10 install
Install openSUSE , selecting the “do not modify” for the detected windows
Everything was fine until it was time to reboot, tested out the dualboot by selecting windows, I got the windows logo for a few seconds, then my keyboard connection dropped, pc restarted and it was stuck in a loop, I used the BIOS to put tumbleweed as first boot option

After many hours and countless surely idiotic attempts later no progress, but everything I had on windows was backed up to secondary drives so I decided to take a different approach
Formatted entire drive
Installed tumbleweed first, spent a little while configuring it to my liking
Installed windows second, spent a little while configuring it
But on the very first reboot, exact same problem as above, tumbleweed boots fine, but windows 10 gets stuck in a boot loop

I am new to linux so I am trying to take it slow, when I say configuring I mean things like arranging panels, installing vpn, renaming audio devices, I have not done anything of note but a problem that has cropped up whilst typing this, my konsole/superuserterminal appears to be broke, all I see is a white box in the top left indicating position, but nothing else and I cannot type. Make that, 2 problems that have cropped up while typing this, I made a very simple password, figuring a fast type one would be a good idea until I get a functional system then I can worry about changing it, but I cant even access the snapshots I created in case of more problems arrising because it says 2 simulteaouns errors
1: says my password is wrong, despite only being 2 characters long
2: “The program ‘su’ could not be found. Ensure your PATH is set correctly”

I’m new to linux, but not technology, honestly don’t know why i’m having trouble just getting 2 OS’ to function and boot correctly, i’ve never felt dumber, so if anyone has any suggestions, tips, any thoughts at all what I can try, maybe something i’m overlooking, i’m all ears, thanks

System Info:
CPU: AMD ryzen 5 7600X
GPU: Radeon RX 7800 XT
MOBO : ASrock b65m pro rs wifi
RAM: Kingston 4800 DDR5 32GB
System drive: Kingston KC3000 2TB M.2 NVMe

Software:
KDE Plasma v 6.2.3
KDE Frameworks v 6.7.0
Qt v 6.8.0
Kernel v 6.11.6-2-default(64-bit)
Windows 10 Pro

Boot Mode: UEFI
Partition Layout (courtesy of gparted):
/dev/nvme0n1p1: EFI /boot,esp
/dev/nvme0n1p2 : btrfs (openSUSE root)
/dev/nvme0n1p4: microsoft reserved partition
/dev/nvme0n1p5: ntfs (Windows10)
Bootloader: GRUB 2

arvidjaar · November 9, 2024, 5:15pm

Selecting Windows where exactly?

Serpico · November 9, 2024, 6:04pm

Both places, once both OS’ are installed, both grub and BIOS routes have the same problem in terms of windows, momentary glimpse of a windows loading icon, followed by devices disconnecting/whirring down and reboot

arvidjaar · November 10, 2024, 5:18am

My only guess would be something like boot integrity protection in Windows. But that is something better asked on Windows forums.

Capistro · November 10, 2024, 12:46pm

Do you still have this issue if you disable secure boot?

jedibeeftrix · November 10, 2024, 1:19pm

i always install windows first, then opensuse TW after.

i recall hearing that this logical order may reverse when the new BLS full disk encryption methodology is used…

Serpico · November 10, 2024, 5:21pm

Update time, I could not tell you how if you paid me because I did not consciously do anything different to my previous attempts, but I have reversed the problem

-Installed windows
-Installed SUSE, again choosing “do not modify” for the guided partitioning page
Sorry, forgot to mention this in original post but secure boot is disabled in bios and I make sure to disable the setting for it during SUSE install
-Rebooted, went straight into windows, surpisingly it worked
-Rebooted, tried SUSE

-Rebooted, this time I got neither grub or errors, just a static _ at the top left, had to change the BIOS order to priotize windows for the time being

Serpico · November 11, 2024, 12:38pm

Today’s attempt, windows is fine both via grub or changing orderin BIOS as I have for the time being,spent some time trying to boot into the “rescue system” I get “Login incorrect” even though both my username and password are just 2 characters each so the chances of me somehow consistently getting it wrong are barely measurable

i tried boot repair tool, I know it’s not tailored to openSUSE, but it was one more tool to try

Which gave this
“Enable repo”

I had some ill-fated attempts to fix this from live-boot
Repo trouble

I’m too new to embed or link more media, but I also got “unable to allocate pty: No such devices” a lot, expecting to be human error, so far my experience with OpenSUSE has been 99% troubleshooting and terminal interactions, the latter being entirely new to me every step of the way, but no harm in mentioning it

I did get a log file, if anyone’s willing to skim through that, apologies in advance if it is in fact something very obvious that’s just going over my head

boot-repair-4ppa2081                                              [20241111_1130]

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

 => No boot loader is installed in the MBR of /dev/nvme0n1.
 => Windows is installed in the MBR of /dev/sda.
 => Windows is installed in the MBR of /dev/sdb.
 => No boot loader is installed in the MBR of /dev/sdc.
 => Grub2 (v2.00) is installed in the MBR of /dev/sdd and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (,2)/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    offsetio extcmd macho elf file gettext boot bufio verifiers crypto 
    terminal normal datetime date mmap drivemap blocklist archelp newc 
    vga_text relocator video chain ntldr search_label search_fs_file 
    search_fs_uuid search keylayouts at_keyboard pci usb usb_keyboard gcry_md5 
    hashsum gcry_crc gzio xzio lzopio lspci fshelp ext2 xfs acpi reboot 
    iso9660 gcry_sha1 div udf exfat font diskfilter raid6rec zstd btrfs ventoy 
    read halt video_fb vbe linux linux16 test true sleep echo bitmap gfxterm 
    bitmap_scale trig video_colors gfxmenu videotest videoinfo functional_test 
    videotest_checksum video_cirrus video_bochs vga minicmd help configfile tr 
    biosdisk disk ls tar zfs squash4 pbkdf2 gcry_sha512 password_pbkdf2 
    all_video png jpeg part_gpt part_msdos fat ntfs loopback 
    gfxterm_background procfs gfxterm_menu smbios
    ---------------------------------------------------------------------------

nvme0n1p1: _____________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

nvme0n1p2: _____________________________________________________________________

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

nvme0n1p3: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 10 or 11
    Boot files:        

nvme0n1p4: _____________________________________________________________________

    File system:       crypto_LUKS
    Boot sector type:  Unknown
    Boot sector info: 

sda1: __________________________________________________________________________

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

sdb1: __________________________________________________________________________

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

sdb2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  According to the info in the boot sector, sdb2 has 
                       3131074559 sectors, but according to the info from 
                       fdisk, it has 11721009151 sectors.
    Operating System:  
    Boot files:        

sdc1: __________________________________________________________________________

    File system:       
    Boot sector type:  Unknown
    Boot sector info: 

sdc2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  According to the info in the boot sector, sdc2 has 
                       3518803967 sectors, but according to the info from 
                       fdisk, it has 7813771263 sectors.
    Operating System:  
    Boot files:        

sdd1: __________________________________________________________________________

    File system:       exfat
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /mnt/BootInfo/sdd1: /dev/sdd1 already mounted or mount point busy.

sdd2: __________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Operating System:  
    Boot files:        


================================ 2 OS detected =================================

OS#1 (linux):   openSUSE Tumbleweed on mapper/system-root
OS#2 (windows):   Windows 10 or 11 on nvme0n1p3

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Advanced Micro Devices, Inc. [AMD/ATI] Advanced Micro Devices, Inc. [AMD/ATI] EFI VGA from Advanced Micro Devices, Inc. [AMD/ATI] Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 1.29.AS01(5.26) from American Megatrends International, LLC.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0002,0000,0003
Boot0000* Windows Boot Manager	HD(1,GPT,f38dff69-12b5-4493-b842-7274b23909e5,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...I................
Boot0002* opensuse	HD(1,GPT,f38dff69-12b5-4493-b842-7274b23909e5,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)
Boot0003* UEFI: USB3.2, Partition 2	PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0xc,0x0)/Pci(0x0,0x0)/USB(2,0)/HD(2,MBR,0x6fb262b0,0xe7c6000,0x10000)..BO


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

Disks info: ____________________________________________________________________

nvme0n1	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	has-win,	2048 sectors * 512 bytes
sdb	: is-GPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, no-os,	no-wind,	34 sectors * 512 bytes
sdc	: is-GPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, no-os,	no-wind,	2048 sectors * 512 bytes
sda	: notGPT,	no-BIOSboot,	has-noESP, 	not-usb,	not-mmc, has-os,	no-wind,	2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p3	: is-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
nvme0n1p1	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far
sdb2	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
sdc2	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	end-after-100GB
sda2	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far
mapper/system-root	: is-os,	64, zypper --non-interactive,	no-docgrub,	grub2,	grub2-install,	no-grubenv,	grub2-mkconfig -o /boot/grub,	not-far

Partitions info (2/3): _________________________________________________________

nvme0n1p3	: isnotESP,	part-has-no-fstab,	no-nt,	haswinload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
nvme0n1p1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, vfat
sdb2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
sdc2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
sda2	: isnotESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ntfs
mapper/system-root	: isnotESP,	fstab-has-goodEFI,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, btrfs

Partitions info (3/3): _________________________________________________________

nvme0n1p3	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
nvme0n1p1	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
sdb2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	sdb
sdc2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	sdc
sda2	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	sda
mapper/system-root	: not--sepboot,	with-boot,	fstab-without-boot,	not-sep-usr,	with--usr,	fstab-without-usr,	std-grub.d,	sda

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk identifier: 3E429C67-61B8-45E9-A466-FF4623D5F5F3
             Start        End    Sectors   Size Type
nvme0n1p1      2048     206847     204800   100M EFI System
nvme0n1p2    206848     239615      32768    16M Microsoft reserved
nvme0n1p3    239616  716802047  716562432 341.7G Microsoft basic data
nvme0n1p4 716802048 4000797326 3283995279   1.5T Linux LVM
Disk sda: 978.09 GiB, 1050214588416 bytes, 2051200368 sectors
Disk identifier: 0x05e874c3
     Boot Start        End    Sectors   Size Id Type
sda1          63 2051198319 2051198257 978.1G 42 SFS
Disk sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk identifier: 2728D45C-00B4-4774-92E9-8496D25A1968
     Start         End     Sectors  Size Type
sdb1     34       32767       32734   16M Microsoft reserved
sdb2  32768 11721041919 11721009152  5.5T Microsoft basic data
Disk sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk identifier: 1E168934-9DF4-4E0F-9EBB-4701DA53F4EA
      Start        End    Sectors  Size Type
sdc1    2082     262177     260096  127M Microsoft reserved
sdc2  264192 7814035455 7813771264  3.6T Microsoft basic data
Disk sdd: 115.92 GiB, 124465971200 bytes, 243097600 sectors
Disk identifier: 0x6fb262b0
     Boot     Start       End   Sectors   Size Id Type
sdd1  *         2048 243032063 243030016 115.9G  7 HPFS/NTFS/exFAT
sdd2       243032064 243097599     65536    32M ef EFI (FAT-12/16/32)
Disk mapper/ventoy: 2.45 GiB, 2630877184 bytes, 5138432 sectors
Disk identifier: 0x14eb2669
                   Boot Start     End Sectors  Size Id Type
mapper/ventoy-part1 *        0 5138431 5138432  2.5G  0 Empty
mapper/ventoy-part2        572    9067    8496  4.1M ef EFI (FAT-12/16/32)
Disk mapper/cryptroot: 1.53 TiB, 1681388805632 bytes, 3283962511 sectors
Disk mapper/system-swap: 30.47 GiB, 32719765504 bytes, 63905792 sectors
Disk mapper/system-root: 1.5 TiB, 1648667656192 bytes, 3220054016 sectors

parted -lm (filtered): _________________________________________________________

sda:1050GB:scsi:512:512:msdos:ATA Crucial_CT1050MX:;
1:32.3kB:1050GB:1050GB:::;
sdb:6001GB:scsi:512:4096:gpt:ATA WDC WD60EZAZ-00S:;
1:17.4kB:16.8MB:16.8MB::Microsoft reserved partition:msftres;
2:16.8MB:6001GB:6001GB:ntfs:Basic data partition:msftdata;
sdc:4001GB:scsi:512:4096:gpt:ATA WDC WD40EZRX-00S:;
1:1066kB:134MB:133MB:::msftres;
2:135MB:4001GB:4001GB:ntfs::msftdata;
sdd:124GB:scsi:512:512:msdos:USB3.2 FLASH DRIVE:;
1:1049kB:124GB:124GB:::boot;
2:124GB:124GB:33.6MB:fat16::esp;
mapper/system-root:1649GB:dm:512:512:loop:Linux device-mapper (linear):;
1:0.00B:1649GB:1649GB:btrfs::;
mapper/system-swap:32.7GB:dm:512:512:loop:Linux device-mapper (linear):;
1:0.00B:32.7GB:32.7GB:linux-swap(v1)::;
mapper/cryptroot:1681GB:dm:512:512:unknown:Linux device-mapper (crypt):;
mapper/ventoy:2631MB:dm:512:512:msdos:Linux device-mapper (linear):;
2:293kB:4643kB:4350kB:::esp;
nvme0n1:2048GB:nvme:512:512:gpt:KINGSTON SKC3000D2048G:;
1:1049kB:106MB:105MB:fat32:EFI system partition:boot, esp;
2:106MB:123MB:16.8MB::Microsoft reserved partition:msftres;
3:123MB:367GB:367GB:ntfs:Basic data partition:msftdata;
4:367GB:2048GB:1681GB:::lvm;

blkid (filtered): ______________________________________________________________

NAME              FSTYPE      UUID                                   PARTUUID                             LABEL                  PARTLABEL
sda                                                                                                                              
├─sda1                                                                                                                           
└─sda2            ntfs        98A020CFA020B622                                                            SSD (Games)            
sdb                                                                                                                              
├─sdb1                                                               8f218abf-cff7-4a5d-a399-ca697c4a13e5                        Microsoft reserved partition
└─sdb2            ntfs        9016854A168531F0                       9c66e9ad-1fce-4e27-a83a-b53c75489b5d WD blue                Basic data partition
sdc                                                                                                                              
├─sdc1                                                               05bc2c8b-7a17-11e4-a6e6-902b3459001f                        
└─sdc2            ntfs        987400EF7400D244                       55633813-917b-11ea-8497-7085c257bf72 WD Green (Media)       
sdd                                                                                                                              
├─sdd1            exfat       4E21-0000                              6fb262b0-01                          Ventoy                 
│ └─ventoy                                                                                                                       
└─sdd2            iso9660     2023-12-23-05-05-55-00                                                      Boot-Repair-Disk 64bit 
nvme0n1                                                                                                                          
├─nvme0n1p1       vfat        7CF7-E0E8                              f38dff69-12b5-4493-b842-7274b23909e5                        EFI system partition
├─nvme0n1p2                                                          20f19d62-6d22-48df-9d48-548682894369                        Microsoft reserved partition
├─nvme0n1p3       ntfs        282A00EC2A00B938                       ca2bfd6e-d953-4d40-b366-d5629696229c                        Basic data partition
└─nvme0n1p4       crypto_LUKS 1899b5a5-deaf-47c5-8621-093815f140f6   98e3d16c-221a-4791-9d60-c1001bc0fde7                        
  └─cryptroot     LVM2_member hhpYGj-SpFe-2F4Z-KTCB-oVDT-BrsO-dbMiCO                                                             
    ├─system-swap swap        53cf0f37-f698-40e4-b593-033a5f77cf72                                                               
    └─system-root btrfs       ecb6d7f3-993f-49a0-9d29-f01ef4810405                                                               

Mount points (filtered): _______________________________________________________

                                                   Avail Use% Mounted on
/dev/mapper/system-root[/@/.snapshots/1/snapshot]   1.5T   0% /mnt
/dev/mapper/ventoy                                     0 100% /cdrom
/dev/sda2                                         104.2G  89% /mnt/boot-sav/sda2
/dev/sdb2                                          29.9G  99% /mnt/boot-sav/sdb2
/dev/sdc2                                         100.3G  97% /mnt/boot-sav/sdc2

Mount options (filtered): ______________________________________________________

/dev/mapper/ventoy                                iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8
/dev/sda2                                         fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sdb2                                         fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sdc2                                         fuseblk         rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096

============================== ls -R /dev/mapper/ ==============================

/dev/mapper:
control
cryptroot
system-root
system-swap
ventoy

================================= User choice ==================================

Is there RAID on this computer? yes


==================== blkid (filtered) before lvm activation ====================

/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="282A00EC2A00B938" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ca2bfd6e-d953-4d40-b366-d5629696229c"
/dev/nvme0n1p1: UUID="7CF7-E0E8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f38dff69-12b5-4493-b842-7274b23909e5"
/dev/nvme0n1p4: UUID="1899b5a5-deaf-47c5-8621-093815f140f6" TYPE="crypto_LUKS" PARTUUID="98e3d16c-221a-4791-9d60-c1001bc0fde7"
/dev/sdd1: LABEL="Ventoy" UUID="4E21-0000" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTUUID="6fb262b0-01"
/dev/sdb2: LABEL="WD blue" BLOCK_SIZE="512" UUID="9016854A168531F0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9c66e9ad-1fce-4e27-a83a-b53c75489b5d"
/dev/mapper/ventoy: BLOCK_SIZE="2048" UUID="2023-12-23-05-05-55-00" LABEL="Boot-Repair-Disk 64bit" TYPE="iso9660" PTUUID="14eb2669" PTTYPE="dos"
/dev/sdc2: LABEL="WD Green (Media)" BLOCK_SIZE="512" UUID="987400EF7400D244" TYPE="ntfs" PARTUUID="55633813-917b-11ea-8497-7085c257bf72"
/dev/sda2: LABEL="SSD (Games)" BLOCK_SIZE="512" UUID="98A020CFA020B622" TYPE="ntfs"
/dev/sdd2: BLOCK_SIZE="2048" UUID="2023-12-23-05-05-55-00" LABEL="Boot-Repair-Disk 64bit" TYPE="iso9660" PTUUID="14eb2669" PTTYPE="dos"
/dev/mapper/cryptroot: UUID="hhpYGj-SpFe-2F4Z-KTCB-oVDT-BrsO-dbMiCO" TYPE="LVM2_member"
/dev/mapper/system-swap: UUID="53cf0f37-f698-40e4-b593-033a5f77cf72" TYPE="swap"
/dev/mapper/system-root: UUID="ecb6d7f3-993f-49a0-9d29-f01ef4810405" UUID_SUB="92ff29f4-5b10-412b-944f-b856026ad9b5" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="20f19d62-6d22-48df-9d48-548682894369"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="8f218abf-cff7-4a5d-a399-ca697c4a13e5"
/dev/sdc1: PARTUUID="05bc2c8b-7a17-11e4-a6e6-902b3459001f"


================================ LVM activation ================================

modprobe dm-mod  
vgscan --mknodes
  Found volume group "system" using metadata type lvm2
vgchange -ay
  2 logical volume(s) in volume group "system" now active
lvscan
  ACTIVE            '/dev/system/swap' [30.47 GiB] inherit
  ACTIVE            '/dev/system/root' [<1.50 TiB] inherit
blkid -g

Unusual RAID (no raid in blkid).

=================== blkid (filtered) before raid activation ====================

/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="282A00EC2A00B938" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ca2bfd6e-d953-4d40-b366-d5629696229c"
/dev/nvme0n1p1: UUID="7CF7-E0E8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f38dff69-12b5-4493-b842-7274b23909e5"
/dev/nvme0n1p4: UUID="1899b5a5-deaf-47c5-8621-093815f140f6" TYPE="crypto_LUKS" PARTUUID="98e3d16c-221a-4791-9d60-c1001bc0fde7"
/dev/sdd1: LABEL="Ventoy" UUID="4E21-0000" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTUUID="6fb262b0-01"
/dev/sdb2: LABEL="WD blue" BLOCK_SIZE="512" UUID="9016854A168531F0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9c66e9ad-1fce-4e27-a83a-b53c75489b5d"
/dev/mapper/ventoy: BLOCK_SIZE="2048" UUID="2023-12-23-05-05-55-00" LABEL="Boot-Repair-Disk 64bit" TYPE="iso9660" PTUUID="14eb2669" PTTYPE="dos"
/dev/sdc2: LABEL="WD Green (Media)" BLOCK_SIZE="512" UUID="987400EF7400D244" TYPE="ntfs" PARTUUID="55633813-917b-11ea-8497-7085c257bf72"
/dev/sda2: LABEL="SSD (Games)" BLOCK_SIZE="512" UUID="98A020CFA020B622" TYPE="ntfs"
/dev/sdd2: BLOCK_SIZE="2048" UUID="2023-12-23-05-05-55-00" LABEL="Boot-Repair-Disk 64bit" TYPE="iso9660" PTUUID="14eb2669" PTTYPE="dos"
/dev/mapper/cryptroot: UUID="hhpYGj-SpFe-2F4Z-KTCB-oVDT-BrsO-dbMiCO" TYPE="LVM2_member"
/dev/mapper/system-swap: UUID="53cf0f37-f698-40e4-b593-033a5f77cf72" TYPE="swap"
/dev/mapper/system-root: UUID="ecb6d7f3-993f-49a0-9d29-f01ef4810405" UUID_SUB="92ff29f4-5b10-412b-944f-b856026ad9b5" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="20f19d62-6d22-48df-9d48-548682894369"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="8f218abf-cff7-4a5d-a399-ca697c4a13e5"
/dev/sdc1: PARTUUID="05bc2c8b-7a17-11e4-a6e6-902b3459001f"


==================================== mdadm =====================================
mdadm --assemble --scan

mdadm --detail --scan

RAID detected. You may want to retry after installing the [dmraid] packages.
Warning: no active raid (DMRAID nor MD_ARRAY).


Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility will purge (in order to fix packages) and reinstall the grub-efi of
mapper/system-root,
using the following options:  nvme0n1p1/boot/efi
Additional repair will be performed: unhide-bootmenu-10s use-standard-efi-file



Confirmation request before suggested repair: __________________________________

SFS detected. You may want to retry after converting Windows dynamic partitioning (SFS partitions) to a basic disk. This can be performed via tools such as TestDisk or EASEUS-Partition-Master / MiniTool-Partition-Wizard.
You may want to retry after mounting your encrypted partitions so that the tool can verify their contents. (cryptsetup open)
Are you sure you want to continue anyway?SFS detected. You may want to retry after converting Windows dynamic partitioning (SFS partitions) to a basic disk. This can be performed via tools such as TestDisk or EASEUS-Partition-Master / MiniTool-Partition-Wizard.
You may want to retry after mounting your encrypted partitions so that the tool can verify their contents. (cryptsetup open)
Are you sure you want to continue anyway?

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the openSUSE Tumbleweed entry (nvme0n1p1/efi/****/grub****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\grub****.efi (**** will be updated in the final message)

sprunge.us ko ()

Capistro · November 11, 2024, 6:41pm

So grub an windows are working, but openSUSE is not? Just want to make sure I am reading this right.
If so, flash the openSUSE iso directly to the flashdrive with something like BalenaEtcher. OpenSUSE really does not like ventoy, and that could be the root of your issues.

Serpico · November 11, 2024, 11:57pm

Thats the current situation yeah, Originally it was openSUSE booting and not windows.

I have tried again, using balenaetcher, unfortunately same situation.

Formatted the SUSE partitions again
Installed openSUSE from an etcher created drive
Booted into SUSE fine, didn’t touch anything, let it download updates and when the icon appeared in the taskbar saying it needed to restart, I restarted.
Grub worked fine, selecting SUSE option gave a message, too quick to read it all , but something like “cannot find TOCBLOCK, database may be corrupt”, then I get a static _ again
rebooted, tried the rescue mode option ^ exact same thing
rebooted to see if windows was still working and yes, from both bios or grub, windows is fine

For whatever reason windows is now stable and linux remains inaccessible on my system, since making a choice on which variation to go with past testing live boots, I have not yet been able to access a linux desktop environment more than once per install

arvidjaar · November 12, 2024, 4:20am

This comes from Linux LDM driver which reads Windows volume manager (dynamic disks) database. Are you using dynamic disks in your Windows installation?

LDM database is located at the end of the disk. You may consider wiping out the disk completely (at least, overwriting the last several megabytes with zeroes).

clive · November 12, 2024, 5:03pm

Hi
Hope this helps …

The boot partition needs to be circa 250 MB, and if you have a separate MBR partition for booting it is a tiny amount of space, just a MB.

So can you clarify whether you have just an EFI boot area, only MBR, both or something else?

NB: I mount my BOOT partition using Paragon CE and allocate it as A:, then I can view what boot loaders are present, and delete those I don’t like.

Serpico · November 12, 2024, 5:16pm

dynamic disk

My system drive wasn’t, but one of my storage drives was dynamic, would never have occured to me that a storage drives state would be the singular reason for not being able to even boot into a rescue mode, but since changing it to a basic disk I have done a fresh install of tumbleweed, spent the day working away between windows/tumbleweed and so far everything appears to be fine.
Thank you very much

system · November 19, 2024, 5:16pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.