New install won't boot

English Install/Boot/Login
1

I fresh installed the Leap on drive in bold below. When I (try) to start it i get a message about ‘Please load the kernel first’
In Grub menu selecting the /dev/sdb6 the ‘linux’ line has a kernel that is WAY old.
When I ‘root’ to the /lib/modules/ on that install from another disk it has only the directory for ‘5.3.18-150300.59.43-default’

***I didn’t pay attention to where the boot was located in the installer, and that HDD shows the boot * in the ‘system reserve’.(See Below).
Can I change it to another partition on that HDD and still have Windows boot when I want it?

***If you need anything else, let me know.

fdisk -lDisk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors
Disk model: WDC WD1600AAJB-0
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: 0xfb30b87c


Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048  20973567  20971520   10G 82 Linux swap / Solaris
/dev/sda2  *     20973568 100665343  79691776   38G 83 Linux
/dev/sda3       100665344 312581807 211916464  101G 83 Linux

**Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors**
**Disk model: ST500NM0011     **
**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: 0x00000001**


**Device     Boot     Start       End   Sectors   Size Id Type**
**/dev/sdb1  *           64    204863    204800   100M  7 HPFS/NTFS/exFAT     <<<< Can I MOVE THIS BOOT FLAG and still start windows????**
**/dev/sdb2          208845 167981183 167772339    80G  7 HPFS/NTFS/exFAT <<Windows 10**
**/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT <<Windows7 **
**/dev/sdb4       167981185 531282527 363301343 173.2G  f W95 Ext'd (LBA)**
**/dev/sdb5       167983104 193148927  25165824    12G 82 Linux swap / Solaris**
**/dev/sdb6       193150976 289619967  96468992    46G 83 Linux**
**/dev/sdb7       289622016 531282527 241660512 115.2G 83 Linux**

Partition table entries are not in disk order.

Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors
Disk model: ST3160815AS     
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: 0xd0f4738c

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux
2

Images of grub screen(s) for /dev/sdb6 that has the wrong kernel in it.
Errors May be because boot(*) got put in the Windows system reserve for that drive that has an older install on it at one time.

Grub Screen https://susepaste.org/57567369

After selection has wrong kernel https://susepaste.org/39269943

The resulting error https://susepaste.org/36106318

lib/modules/kernel https://susepaste.org/87629930 has latest kernel.

Sorry for the quality, but I had to take pictures with my iPad.

3

This kind of installation and disk grouping would be easier to deal with if all disks were GPT, and UEFI was in use. Long term I suggest switching either to having Windows on a separate PC, or installed to a VM, along with using GPT and UEFI. Better would be learning how to not need Windows.

Please upload (susepaste) output from bootinfoscript. It might tell you what you need to do.

4

You should be able to dual boot. I got a PC with both Windows and Linux install on their own partitions. I boot off the Linux partition, you might have to go into your BIOS and change the hard drive you boot off. GRUB should be able to find other OS installed and list them.

5

FIRST - I put in bootinfoscript a month ago.
And the Leap Installs on that machine are used for different things.

SECOND - this old HP Compaq is legacy, and I don’t know if GPT on it’s HDD’s is even possible! I KNOW UEFI is not possible without a lot of hardware changes. I have a partitioner (AOMEI) in Windows that has that capabilities of doing that, but I TRULY believe I would end up with a totally inoperable machine!

THIRD - If you can tell me why the ‘bootfnfoscript’ output shows the kernel as ‘5.3.18.-57-default’ instead of ‘5.3.18-150300.59.43-default’ please let me know!
It is also reporting that the file system format is ext2, and that last install on 01/30/2021 that disk IS EXT4(want an image for proof???)

HERE is the ‘/dev/sdb6/’ snippet of the bootinfoscript from this evening, fresh out of the oven!

menuentry 'openSUSE Leap 15.3 (on /dev/sdb6)' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-e19e0350-19b3-4bb1-8416-9d711b63af4b' {    insmod part_msdos
    insmod ext2
    set root='hd1,msdos6'
    if  x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'  e19e0350-19b3-4bb1-8416-9d711b63af4b
    else
      search --no-floppy --fs-uuid --set=root e19e0350-19b3-4bb1-8416-9d711b63af4b
    fi
    linux /boot/vmlinuz-5.3.18-57-default root=UUID=e19e0350-19b3-4bb1-8416-9d711b63af4b showopts fastboot nomodeset mitigations=auto
    initrd /boot/initrd-5.3.18-57-default
}
submenu 'Advanced options for openSUSE Leap 15.3 (on /dev/sdb6)' $menuentry_id_option 'osprober-gnulinux-advanced-e19e0350-19b3-4bb1-8416-9d711b63af4b' {
    menuentry 'openSUSE Leap 15.3 (on /dev/sdb6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.3.18-57-default--e19e0350-19b3-4bb1-8416-9d711b63af4b' {
        insmod part_msdos
        insmod ext2
        set root='hd1,msdos6'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'  e19e0350-19b3-4bb1-8416-9d711b63af4b
        else
          search --no-floppy --fs-uuid --set=root e19e0350-19b3-4bb1-8416-9d711b63af4b
        fi
        linux /boot/vmlinuz-5.3.18-57-default root=UUID=e19e0350-19b3-4bb1-8416-9d711b63af4b showopts fastboot nomodeset mitigations=auto
        initrd /boot/initrd-5.3.18-57-default
    }
    menuentry 'openSUSE Leap 15.3, with Linux 5.3.18-57-default (on /dev/sdb6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.3.18-57-default--e19e0350-19b3-4bb1-8416-9d711b63af4b' {
        insmod part_msdos
        insmod ext2
        set root='hd1,msdos6'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'  e19e0350-19b3-4bb1-8416-9d711b63af4b
        else
          search --no-floppy --fs-uuid --set=root e19e0350-19b3-4bb1-8416-9d711b63af4b
        fi
        linux /boot/vmlinuz-5.3.18-57-default root=UUID=e19e0350-19b3-4bb1-8416-9d711b63af4b showopts fastboot nomodeset mitigations=auto
        initrd /boot/initrd-5.3.18-57-default
    }
    menuentry 'openSUSE Leap 15.3, with Linux 5.3.18-57-default (recovery mode) (on /dev/sdb6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.3.18-57-default--e19e0350-19b3-4bb1-8416-9d711b63af4b' {
        insmod part_msdos
        insmod ext2
        set root='hd1,msdos6'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 --hint-efi=hd1,msdos6 --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'  e19e0350-19b3-4bb1-8416-9d711b63af4b
        else
          search --no-floppy --fs-uuid --set=root e19e0350-19b3-4bb1-8416-9d711b63af4b
        fi
        linux /boot/vmlinuz-5.3.18-57-default root=UUID=e19e0350-19b3-4bb1-8416-9d711b63af4b
        initrd /boot/initrd-5.3.18-57-default
    }
}

FOURTH - Once again you did not respond to my question in the OP!

BTW, the 5.3.18.-57-default kernel disappear when I deleted the original Leap partitions, and SUPPOSEDLY wiped the partition and over wrote it with xero’s.

6

I can dual boot with Windows, I just can’t boot that Leap 15.3 installed on the Windows drive.
I’m just trying to figure out how to boot off the Linux partition, WITHOUT screwing up starting Windows. Go thorough the stuff in my other posts here , IF you are interested.

Thanks for the response.

7

Presumably this is the question referred to. It’s unanswerable without more information, such as the complete current status of the partitioning and bootloaders. Month old bootinfoscript output in an unknown location is no help.

We have our own equipment to manage. We cannot remember all the intricacies of your several computers, disks and installations. Most of us are not Windows experts, or even Windows users, which makes it all the more difficult to try to help you when Windows plays any part in what you are doing or trying to do, or undo.

8

Yes, that was the question I was looking or response to.

AND> What I meant was I got bootinfoscritp a month ago. NOT THAT WHAT I GIVE(GAVE) TODAY IS THAT OLD!! I may be old, but not senile!
AND> the bootinfoscript does not have mention of the 5.3.18-57-default the error kernel in an image in images I submitted, on the windows drive GRUB is looking for! ( I WILL SEND THE COMPLETE BOOTINFOSCRIPT via PM, OR here OR susepaste if it would work???** {has the location of susepaste changed??}
**
current ‘fdisk -l’ output as of 10:00PM 01-31-2022

fdisk -l
**Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors**
Disk model: WDC WD1600AAJB-0
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: 0xfb30b87c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sda1            2048  20973567  20971520   10G 82 Linux swap / Solaris
/dev/sda2  *     20973568 100665343  79691776   38G 83 Linux
/dev/sda3       100665344 312581807 211916464  101G 83 Linux


**Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors**
Disk model: ST500NM0011      
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: 0x00000001

**Device****Boot****    Start****      End****  Sectors****  Size****Id****Type**
/dev/sdb1              64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          208845 167981183 167772339    80G  7 HPFS/NTFS/exFAT  **<<< Windows 10**
/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT  **<<< Windows 7**
/dev/sdb4  *    167981185 531282527 363301343 173.2G  f W95 Ext'd (LBA) **<<<< I changed this to boot after reading a section of the bootinfoscript!**
/dev/sdb5       167983104 193148927  25165824    12G 82 Linux swap / Solaris
/dev/sdb6       193150976 289619967  96468992    46G 83 Linux
/dev/sdb7       289622016 531282527 241660512 115.2G 83 Linux

Partition table entries are not in disk order.


**Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors**
Disk model: ST3160815AS      
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: 0xd0f4738c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux

I changed the boot partition to /dev/sdb4 after seeing this in the bootinfoscript @ 10:.00PM 01-31-2022 TO NO EFFECT! I have the before changing the boot to /dev/sdb4 If you want to see it!

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sdb4


00000000  63 de 8c 68 ee 72 51 d8  83 82 c9 6c 92 35 11 1c  |c..h.rQ....l.5..|
00000010  53 16 94 14 96 7f 13 08  d1 b5 28 3e c0 4b dd d9  |S.........(>.K..|
00000020  a9 ed 96 67 f4 cc 5d d7  32 b0 23 a2 f3 05 e5 d4  |...g..].2.#.....|
00000030  c6 fb 95 16 b7 e1 c9 b1  aa 63 70 4d fc f7 a4 28  |.........cpM...(|
00000040  1f 07 1a d7 2b e3 d7 e5  0d b4 d5 2a 78 e9 c8 fa  |....+......*x...|
00000050  89 4e 19 04 5c 76 7d c2  11 a0 55 6e 18 34 93 dc  |.N..\v}...Un.4..|
00000060  df 66 9a f1 73 0c d3 de  4c 32 27 2f 6f 55 c5 ed  |.f..s...L2'/oU..|
00000070  51 fa 3e e7 bf a7 83 1f  a8 d4 d7 24 99 cf 1b 16  |Q.>........$....|
00000080  a1 1e e8 dc 56 c1 68 36  41 96 09 c2 b4 4f 87 42  |....V.h6A....O.B|
00000090  86 89 6f 73 3c 9a 2d 52  10 45 c6 b1 07 0a b8 27  |..os<.-R.E.....'|
000000a0  ac ba 43 aa b4 68 83 af  75 28 ec 01 e9 76 e5 2b  |..C..h..u(...v.+|
000000b0  d6 ee 28 38 b0 15 58 bb  56 8d a0 7e da 3c 27 90  |..(8..X.V..~.<'.|
000000c0  54 68 a5 e0 3d b5 3c 0a  1e 86 ba fd 61 01 fe 34  |Th..=.<.....a..4|
000000d0  30 cf 36 09 dc be 94 9a  58 e5 af 39 c3 67 f8 20  |0.6.....X..9.g. |
000000e0  6d 7b 00 45 9c 89 20 77  37 41 c3 5f 1c 22 0b 52  |m{.E.. w7A._.".R|
000000f0  39 f7 6f 28 19 a2 29 78  96 14 4a 75 fa 8f ad 8e  |9.o(..)x..Ju....|
00000100  c5 cc 12 87 cf d7 6a 7b  24 8b ab f9 b4 4b 3a b9  |......j{$....K:.|
00000110  47 ed 9f ac 7d ee 24 60  5e 7a 11 0b c5 d3 9e 37  |G...}.$`^z.....7|
00000120  62 95 4f c2 d1 f4 73 59  ed cd 69 91 0c bc 58 8e  |b.O...sY..i...X.|
00000130  c7 f0 8b 9e 44 0b 8c 99  65 eb 33 42 91 3e 32 b8  |....D...e.3B.&gt;2.|
00000140  10 67 96 de 4e a3 de 4a  10 94 25 51 90 ad 95 07  |.g..N..J..%Q....|
00000150  69 44 77 83 54 6f d2 62  64 15 7c 80 26 31 57 a8  |iDw.To.bd.|.&1W.|
00000160  02 10 77 01 73 63 a3 f0  cc d8 ed f7 fe 55 51 8d  |..w.sc.......UQ.|
00000170  36 0b 9c bf 0d 3f 7a 94  c9 dd bc 94 f1 04 fc bc  |6....?z.........|
00000180  7b 0d c3 e0 c9 89 73 cf  17 5d ca 15 01 aa dd f6  |{.....s..]......|
00000190  1c 32 ff 18 e5 ff 31 15  86 74 a7 1f 1f b7 ae 3d  |.2....1..t.....=|
000001a0  c3 ad 5b 23 23 3a 23 fd  81 ba 15 6a 97 6a a9 e0  |..##:#....j.j..|
000001b0  73 b9 c4 f9 20 b8 0b 23  bb cb 84 39 e3 2b 00 0f  |s... ..#...9.+..|
000001c0  ff ff 82 0f ff ff 7f 07  00 00 00 00 80 01 00 0f  |................|
000001d0  ff ff 05 0f ff ff 5f 0f  80 01 20 00 c0 05 00 00  |......_... .....|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200

BTW> this snippet was in the output BEFORE I changed the boot(*) partition! For what good that tells you.

**OK! Susepaste work this time, HERE IS THE FULL OUTPUT from 10.08PM 01-31-2022
https://susepaste.org/90740600
**

9

I am probably going to have to go into Windows and do the ‘fixmbr’ if I can find my Win 7 DVD.

10

Over too many recent hours I spent too much time composing a response and repeatedly being interrupted. On submit, I was redirected to the login page. On completing login, all that work was lost. I’ll try to remember the key points now.

It appears that there are sda and sdb on PATA, and sdc on SATA. That’s a traditional recipe for boot trouble, as BIOS, bootloaders and kernel drivers do not always agree which is which when PATA and SATA are both in use. Avoiding this issue is one reason for Grub2’s dependence on UUIDs.

The UUID of sdb6 appears in only one of three grub.cfgs, that on sdb6. Grub on multiple MBRs is itself another invitation for trouble. The grub.cfg on sda2 contains stanzas pointing to sdb6, but each includes a non-existent UUID rather than the UUID present on sdb6.

It should help would-be helpers, if not OP, to do as Windows has done: apply LABELs to all filesystems. UUIDs were made for robots and scripts, not humans. LABELs, whether actually used during the boot process or not, can be helpful in various circumstances. I have hundreds of filesystems. If they didn’t all have labels, they would be entirely unmanageable, since each PC has 13 or more, usually many more.

11

This happens to me regularly. It’s frightening. However you may click the back button until the input form is displayed again. BTW: On erlangen the form survives a reboot. I don’t rely on that feature. But it happened several times.

It should help would-be helpers, if not OP, to do as Windows has done: apply LABELs to all filesystems. UUIDs were made for robots and scripts, not humans. LABELs, whether actually used during the boot process or not, can be helpful in various circumstances. I have hundreds of filesystems. If they didn’t all have labels, they would be entirely unmanageable, since each PC has 13 or more, usually many more.

I strictly stick to UUIDs.: https://forums.opensuse.org/showthread.php/541321-Upgrading-the-Hardware?p=3086058#post3086058

‘sed -i’ is great for changing UUIDs in /etc/fstab. I use copy and paste in konsole to compose the sed command. Check the output:

sed s/UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344/UUID=2f0030b8-7257-4cba-be3e-b33154cda052/ /etc/fstab

When the output is what it should be rerun with option ‘-i’.

**erlangen:~ #** cat /etc/fstab  
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /                       btrfs  defaults                      0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /var                    btrfs  subvol=/@/var                 0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /usr/local              btrfs  subvol=/@/usr/local           0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /srv                    btrfs  subvol=/@/srv                 0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /root                   btrfs  subvol=/@/root                0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /opt                    btrfs  subvol=/@/opt                 0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /home                   btrfs  subvol=/@/home                0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0 
UUID=19CF-0B54                             /boot/efi               vfat   defaults                      0  0 
UUID=5605f149-34a7-4301-9bf3-f1f177e35ed6  /home-SSD               ext4   data=ordered                  0  0 
UUID=f5177cae-4082-44ed-9471-b99030f06866  /HDD                    ext4   noauto                        0  0 
UUID=6914-84F3                             /GARMIN                 vfat   user,noauto                   0  0 
UUID=0267-906F                             /GARMIN-KART            vfat   user,noauto                   0  0 
UUID=0e58bbe5-eff7-4884-bb5d-a0aac3d8a344  /.snapshots             btrfs  subvol=/@/.snapshots          0  0 
LABEL=FR735                                /FR735                  vfat   user,noauto                   0  0 
UUID=2f0030b8-7257-4cba-be3e-b33154cda052  /WD25                   ext4   noauto                        0  0 
//fritz.box/FRITZ.NAS                      /fritz.box              cifs   noauto,username=ftpuser,vers=1.0  0  0 
**erlangen:~ #**
12

I have been trying to do that, but being a Linux relative new user, I haven’t found a way to do that. I tried in in all the installs editing /etc/default/grub on each install, but only one shows up in Grub2 menu at boot, and in command lines accessing the the partitions (ie> fdisk -l).
Tell me how, and I Will get it done. Thanks.

**The machine is a SATA machine, and the ONLY PATA drive is on a PCI card **


***THIS IS THE PATA HDD <<<<<<<
***
**Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors**
Disk model: WDC WD1600AAJB-0
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: 0xfb30b87c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sda1            2048  20973567  20971520   10G 82 Linux swap / Solaris
/dev/sda2  *     20973568 100665343  79691776   38G 83 Linux
/dev/sda3       100665344 312581807 211916464  101G 83 Linux

***THIS IS A SATA HDD THE LEAP INSTALL that won't boot on. Windows 7 and Windows 10 still boot on it, Leap 15.3 won't<<<<<<
***
**Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors**
Disk model: ST500NM0011      
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: 0x00000001

**Device****Boot****    Start****      End****  Sectors****  Size****Id****Type**
/dev/sdb1              64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          208845 167981183 167772339    80G  7 HPFS/NTFS/exFAT ***<<<< Windows 10***
/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT ***<<<< Windows 7***
/dev/sdb4  *    167981185 531282527 363301343 173.2G  f W95 Ext'd (LBA) 
/dev/sdb5       167983104 193148927  25165824    12G 82 Linux swap / Solaris
/dev/sdb6       193150976 289619967  96468992    46G 83 Linux
/dev/sdb7       289622016 531282527 241660512 115.2G 83 Linux

Partition table entries are not in disk order.

***THIS IS THE SATA HDD
***
**Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors**
Disk model: ST3160815AS      
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: 0xd0f4738c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux
13

It doesn’t matter where the boot flag is when you start Windows via Grub chainloading it. When it really matters where the boot flag is is when you’re booting from Windows bootloader. This includes when it reboots to do certain major updates. When it doesn’t find compatible MBR code, and it doesn’t find the boot flag on its boot partition, after installing updates, and rebooting, it will then decide it can’t complete the update, whereupon it will proceed to uninstall the updates that it just installed.

Grub pays no attention to boot flags.

14

[quote="“Bill_L,post:12,topic:149632”]

I have been trying to do that, but being a Linux relative new user, I haven’t found a way to do that. I tried in in all the installs editing /etc/default/grub on each install, but only one shows up in Grub2 menu at boot, and in command lines accessing the the partitions (ie> fdisk -l).
Tell me how, and I Will get it done. Thanks.[/quote]The best time to apply labels to filesystems is as a component of formatting. If it’s omitted then, EXT partitions can later be assigned labels with either tune2fs -L or e2label. Other filesystems I don’t use, so can’t say how to apply labels to them. I’m in the habit of using tune2fs, as I typically also do -U at the same time as labeling.

Other installations being excluded from the various grub.cfgs happens for various reasons, one of which the openSUSE installer not being told to enable search for other installations to include in boot menu. If os-prober is not disabled, other installations should eventually show up if grub2-mkconfig gets run enough. On my installations, Grub submenus are always disabled, as they can be a real PITA for multiboot PCs.

The machine is a SATA machine, and the ONLY PATA drive is on a PCI card
This could well be the root of the problem. Traditionally at least, PCI cards for HDs contain their own BIOS and are treated as SCSI cards by the PC BIOS. This means BIOS settings matter, and won’t necessarily match Grub or kernel drivers. I’ve not run into this in many years, because I quit mixing PATA add-in controllers and SATA motherboards over a decade ago. I suggest the two easiest ways to resolve this issue are likely to be:

  1. remove the PATA controller from the PC, and install to PATA drive an SATA adapter so it can be connected to an SATA port with an SATA cable.
  2. Dispense with all PATA drives entirely
    In both cases, the remaining grub.cfgs will almost certainly need rebuilding after the change.

If you really need what’s on that PATA disk, think about an upgrade to an SATA SSD for it, or move it to an external case to be attached and powered up only when you really need it.

There’s probably another solution, but ATM I’m burned out and need some sleep.

When you provide lists of so many partitions, it would be helpful not only to see labels, but also if labels are absent, annotation of the output to show the content of the various linux filesystems.

15

I’ll try one more time before I maybe) call it quits installing on the Windows drive. When booting, it runs, then goes black, like it is in some sleep or hibernate mode?
>>>>>>> **I really want to get rid of that PATA drive on the PCI card, but can’t afford new SSD’d or HDD’s to replace it.
**
IF I select the "Advanced’ /dev/sdb6/ in Grub menu and add 'nomodeset to the linix line, I get a grayish screen with three green dots that cycle, before it goes blank again.
It IS there, but won’t boot.
Is it maybe because of the message I get during install that there is not enough room in the first sector/partition/ what ever?

Here are some code of that installation.

**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.18-150300.59.43-default
Found initrd image: /boot/initrd-5.3.18-150300.59.43-default
Found Windows 10 on /dev/sdb1
**Found openSUSE Leap 15.3 on /dev/sdb6**
Found openSUSE Leap 15.3 on /dev/sdc2
done

If I had ran this from another install, it would have shown 'Found openSUSE Leap 15.3 on /dev/sda2

**fdisk -l**Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors
Disk model: WDC WD1600AAJB-0
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: 0xfb30b87c


Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048  20973567  20971520   10G 82 Linux swap / Solaris
/dev/sda2  *     20973568 100665343  79691776   38G 83 Linux
/dev/sda3       100665344 312581807 211916464  101G 83 Linux

Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500NM0011     
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: 0x00000001

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1              64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          204869 214769520 214564652 102.3G  7 HPFS/NTFS/exFAT
/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT
/dev/sdb4       214769521 531282527 316513007 150.9G  f W95 Ext'd (LBA)
**/dev/sdb5       214769664 231546879  16777216     8G 82 Linux swap / Solaris**
**/dev/sdb6  *    231548928 315435007  83886080    40G 83 Linux**
**/dev/sdb7       315437056 531282527 215845472 102.9G 83 Linux**


Partition table entries are not in disk order.

Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors
Disk model: ST3160815AS     
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: 0xd0f4738c


Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux

**lsblk -f**NAME   FSTYPE FSVER LABEL                   UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                             
├─sda1 swap   1                             3cb7ceb0-f1a8-4aa8-921e-0cec9d4f39e1                [SWAP]
├─sda2 ext4   1.0                           34b30e42-2c86-45b9-b27e-cfe1aa7c7868   28.3G    19% /
└─sda3 ext4   1.0                           997de06e-983c-40e0-9297-296e72284acf   93.1G     1% /home
sdb                                                                                             
├─sdb1 ntfs         System Reserved         1A0CB3280CB2FE37                                    
├─sdb2 ntfs         Windows 10 Home Release 0FCB1B290FCB1B29                                    
├─sdb3 ntfs         Windows 7 64 Home       ACB2B4EEB2B4BDE0                                    
├─**sdb4                                                                                          **
**├─sdb5 swap   1                             438294c1-619b-4532-8786-e8ebc6283362                **
**├─sdb6 ext4   1.0   WindowsHDD              efccc6c6-5c0a-4875-8733-2942be05b872                **
**└─sdb7 ext4   1.0   Windows-HDD             828fc63b-35fe-4a90-961f-e9f1adcab5d3                **
sdc                                                                                             
├─sdc1 swap   1                             d0b0f5b7-e063-4cc2-a770-d737673deb29                
├─sdc2 ext4   1.0                           28c84369-7b44-4d67-b063-c33988c1c7bd                
└─sdc3 ext4   1.0                           581f4039-96f9-4267-be88-33b4d1698ba5                
sr0

Snippets of ‘bootinfoscript’, I have the full report. I will post it if you want.

=================== sda2: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


  42.227836609 = 45.341794304   boot/grub2/grub.cfg                            2
  42.169353485 = 45.278998528   boot/grub2/i386-pc/core.img                    1
  10.961910248 = 11.770261504   boot/vmlinuz                                   2
  10.961910248 = 11.770261504   boot/vmlinuz-5.3.18-150300.59.43-default       2
  12.727622986 = 13.666181120   boot/initrd                                    1
  12.727622986 = 13.666181120   boot/initrd-5.3.18-150300.59.43-default        1
  
  
**  =================== sdb6: Location of files loaded by Grub: ====================**

**           GiB - GB             File                                 Fragment(s)**

** 142.557712555 = 153.070178304  boot/grub2/grub.cfg                            2**
** 142.555568695 = 153.067876352  boot/grub2/i386-pc/core.img                    1**
** 110.840816498 = 119.014420480  boot/vmlinuz                                   2**
** 110.840816498 = 119.014420480  boot/vmlinuz-5.3.18-150300.59.43-default       2**
** 112.262794495 = 120.541257728  boot/initrd                                    1**
** 112.262794495 = 120.541257728  boot/initrd-5.3.18-150300.59.43-default        1**
 
 =================== sdc2: Location of files loaded by Grub: ====================


           GiB - GB             File                                 Fragment(s)


  32.341075897 = 34.725965824   boot/grub2/grub.cfg                            3
  32.247303009 = 34.625277952   boot/grub2/i386-pc/core.img                    1
  13.586910248 = 14.588833792   boot/vmlinuz                                   2
  13.586910248 = 14.588833792   boot/vmlinuz-5.3.18-150300.59.43-default       2
  12.907222748 = 13.859024896   boot/vmlinuz-5.3.18-59.40-default              2
  12.743247986 = 13.682958336   boot/initrd                                    1
  12.743247986 = 13.682958336   boot/initrd-5.3.18-150300.59.43-default        1
  12.821372986 = 13.766844416   boot/initrd-5.3.18-59.40-default               1
16

What do you see if instead of nomodeset you remove quiet and splash=silent, and append 3 plymouth=0?

How about booting from the installation on sdc, seeing to it that the sdb Leap installation is added to its Grub menu, then booting sdb6 from the sdc Grub? Same black screen behavior? That should define whether the problem has anything to do with Grub on sdb if successful.

It IS there, but won’t boot.
What exactly does “won’t boot” mean here?

17

Sorry, won’t boot, means it starts gives a few lins of script, then goes black screen, and seemingly puts mu monitor in a ‘standby’ mode, NO NORMAL BOOT!
/dev/sda2/ (PATA) in grub boots normally
/dev/sdc2/ (SATA) in grub boots normally as well
**/dev/sdb2/ (Windows SATA) doesn’t even try to boot into a working environment!
**
I’ll give the append **3 plymouth=0 a try. Can’t hurt, nothing else seems to work. **

18

Will it boot if you remove the PATA card, or disconnect the cables from the PATA HDD? Does the PATA HDD have the jumper set to master or only? If it is using a cable-select cable, is the jumper set to CS?

19

Unless I didn’t get it put in the grub edit linux line correctly, nope, just runs through a LOT of script(I can tell you were it is when it goes to the ‘black mode’,boot script running very fast.

20

The PATA drive has a jumper(likely master position), I don’t actually know if it is master jumper or not! But I have removed the power and ribbon cables before, and still go the black screen on /dev/sdb2/

I the card itself doesn’t have any settings or jumpers that I can see, IIRC, all it is a card with connections for 2 ribbon cables, and the power comes from the 700w power box up top in the case. LOT of trouble to remove the card itself.

BUT, this I can say for sure, the Leap 15.2 Leap install DID WORK on that drive, along with the PATA and the OTHER internal SATA!
15.2 worked, 15.3 doesn’t! Gotta be telling us something right?

SORRY, My BAD! I will remove the power and ribbon cable from the PATA drive to see if it helps, I think I did that last week, and it still went through some boot script, then STOPPED with a black screen.