LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   A start job is running for /dev/disk/by-uuid (https://www.linuxquestions.org/questions/suse-opensuse-60/a-start-job-is-running-for-dev-disk-by-uuid-4175731554/)

lattimro 12-05-2023 06:20 PM

A start job is running for /dev/disk/by-uuid
 
Hi Folks,

On OpenSUSE after an regular zypper upgrade the system can not boot due to:

"A start job is running for /dev/disk/by-uuid/287a2f71-d2d0-45d8-b300-82a19b18f1aa".

I chrooted into OpenSUSE and check UUID, looks OK to me. What else should I check?

Code:

blkid|grep 287
/dev/sdc4: LABEL="Gecko" UUID="287a2f71-d2d0-45d8-b300-82a19b18f1aa" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="GECKO" PARTUUID="bb235e2c-ac52-4149-b544-f02f39699641"

/etc/fstab:

Code:

grep 287 -r /etc/fstab
UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa /              ext4    defaults,noatime 0 1

check /dev/sdc4 for bad blocks and all clean
I can upgrade from chroot environment.

Thanks!

mrmazda 12-05-2023 11:41 PM

Regular system "upgrade" how? Of what? Leap? Tumbleweed? Slowroll?

If you show us all of /etc/fstab (from installed system) and input/output from lsblk -f and efibootmgr something may become apparent.

ember1205 12-06-2023 05:01 AM

What does your /boot/grub2/grub.cfg look like? Is that identified as your root partition? Do the same grep that you did against /etc/fstab to ensure that it was correctly identified as your root partition post-upgrade. You might need to edit that file and re-install grub if not.

lattimro 12-06-2023 08:32 AM

Quote:

Originally Posted by ember1205 (Post 6468718)
What does your /boot/grub2/grub.cfg look like? Is that identified as your root partition? Do the same grep that you did against /etc/fstab to ensure that it was correctly identified as your root partition post-upgrade. You might need to edit that file and re-install grub if not.

As long as during booting "A start job is running for /dev/disk/by-uuid/287a2f71-d2d0-45d8-b300-82a19b18f1aa" occurred one may thinks that UUID is coming from /boot/grub2/grub.cfg and assume that the /boot/grub2/grub.cfg entries (particularly the root partition) are correct. This was the reason I did not posted it here. If otherwise one may be sure I would have corrected it.

Code:

grep -r 287 /boot/grub2/grub.cfg
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
                  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
menuentry 'openSUSE Tumbleweed'  --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
          search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
        linux  /boot/vmlinuz-6.6.3-1-default root=UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa  security=apparmor
submenu 'Advanced options for openSUSE Tumbleweed' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
        menuentry 'openSUSE Tumbleweed, with Linux 6.6.3-1-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.3-1-default-advanced-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
                  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
                linux  /boot/vmlinuz-6.6.3-1-default root=UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa  security=apparmor
        menuentry 'openSUSE Tumbleweed, with Linux 6.6.3-1-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.3-1-default-recovery-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
                  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
                linux  /boot/vmlinuz-6.6.3-1-default root=UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa single
        menuentry 'openSUSE Tumbleweed, with Linux 6.5.9-1-default'  --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.5.9-1-default-advanced-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
                  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
                linux  /boot/vmlinuz-6.5.9-1-default root=UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa  security=apparmor
        menuentry 'openSUSE Tumbleweed, with Linux 6.5.9-1-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.5.9-1-default-recovery-287a2f71-d2d0-45d8-b300-82a19b18f1aa' {
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  287a2f71-d2d0-45d8-b300-82a19b18f1aa
                  search --no-floppy --fs-uuid --set=root 287a2f71-d2d0-45d8-b300-82a19b18f1aa
                linux  /boot/vmlinuz-6.5.9-1-default root=UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa single


lattimro 12-06-2023 08:40 AM

Quote:

Originally Posted by mrmazda (Post 6468686)
Regular system "upgrade" how? Of what? Leap? Tumbleweed? Slowroll?

If you show us all of /etc/fstab (from installed system) and input/output from lsblk -f and efibootmgr something may become apparent.

This is TW

zypper up is the 'regular update', to Update installed packages with newer versions.
zypper dup or dist-upgrade, Perform a distribution upgrade.

I showed blikd which I thought would be more relevant but I can post lsblk also if you have a reason to think it will help:

Code:

sdc                                           
├─sdc1                                       
├─sdc2                                       
├─sdc3                                       
├─sdc4                            23.7G    32% /
├─sdc5                                       
└─sdc6                                       
sr0


ember1205 12-06-2023 08:47 AM

Quote:

Originally Posted by lattimro (Post 6468753)
As long as during booting "A start job is running for /dev/disk/by-uuid/287a2f71-d2d0-45d8-b300-82a19b18f1aa" occurred one may thinks that UUID is coming from /boot/grub2/grub.cfg and assume that the /boot/grub2/grub.cfg entries (particularly the root partition) are correct. This was the reason I did not posted it here. If otherwise one may be sure I would have corrected it.

Huh. Seems like you know it all, then.

lattimro 12-06-2023 09:18 AM

1 Attachment(s)
Quote:

Originally Posted by ember1205 (Post 6468759)
Huh. Seems like you know it all, then.

not really ... as long have been posted here. At first it looks like UUID is correct but who knows why is complaining. I did what I have done many times before and TW did not complain.

Unfortunatelly the OpenSUSE forums was hacked most likely and redirects the new users to 'univention' portal

mrmazda 12-06-2023 12:05 PM

Quote:

Originally Posted by lattimro (Post 6468755)
I showed blikd which I thought would be more relevant but I can post lsblk also if you have a reason to think it will help:

Code:

sdc                                           
├─sdc1                                       
├─sdc2                                       
├─sdc3                                       
├─sdc4                            23.7G    32% /
├─sdc5                                       
└─sdc6                                       
sr0


I asked for
Quote:

all of /etc/fstab (from installed system) and input/output from lsblk -f and efibootmgr
Input/output means one whole transaction, within one pair of code tags: 1: the prompt with command; 2: the command's output; and 3: the following prompt, exactly as it appeared on your screen. This allows to understand that what was asked for matches what was provided. Blkid doesn't provide all that I asked for, and neither does lsblk without -f. Example (with bulk of UUIDs redacted):
Code:

# inxi -S
System:
  Host: ab250 Kernel: 6.5.9-1-default arch: x86_64 bits: 64 Console: pty pts/0
    Distro: openSUSE Tumbleweed 20231121
# lsblk -f
NAME        FSTYPE FSVER LABEL      UUID        FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1  vfat  FAT32 PT3P01ESP  30A0-3A09    307.9M    4% /boot/efi
├─nvme0n1p2  swap  1    pt3p02swap  33ef...7799
├─nvme0n1p3  ext2  1.0  pt3p03res  c9e9...eab7  184.3M    52% /disks/res
├─nvme0n1p4  ext4  1.0  pt3p04ulcl  d612...d0b5    1.7G    54% /usr/local
├─nvme0n1p5  ext4  1.0  pt3p05home  f5b8...dddc    5.3G    12% /home
├─nvme0n1p6  ext4  1.0  pt3p06pub  c9d4...474c      6G    49% /pub
├─nvme0n1p7  ext4  1.0  pt3p07stw  3128...13f7  781.8M    85% /
├─nvme0n1p8  ext4  1.0  pt3p08s153  0ef8...3eeb    3.6G    48% /disks/s153
├─nvme0n1p9  ext4  1.0  pt3p09s151  a862...c6aa  748.1M    85% /disks/s151
├─nvme0n1p10 ext4  1.0  pt3p10deb12 d91f...224c
├─nvme0n1p11 ext4  1.0  pt3p11s155  ee53...f634    2.6G    62% /disks/s155
├─nvme0n1p12 ext4  1.0  pt3p12ub22  2509...0e81
├─nvme0n1p13 ext4  1.0  pt3p13deb13 2ac9...9299
├─nvme0n1p14 ext4  1.0  pt3p14deb11 889f...31d6
├─nvme0n1p15 ext4  1.0  pt3p15f39  61cb...a708
├─nvme0n1p16 ext4  1.0  pt3p16s154  3d90...ccbb    2.2G    66% /disks/s154
├─nvme0n1p17 ext4  1.0  pt3p17ub20  ab51...3ba3
├─nvme0n1p18 ext4  1.0  pt3p18f38  5cea...d0cd
└─nvme0n1p19 ext4  1.0  pt3p19sslo  c65c...b277    4.1G    42% /disks/sslo
#


lattimro 12-06-2023 12:52 PM

Quote:

Originally Posted by mrmazda (Post 6468795)
I asked for Input/output means one whole transaction, within one pair of code tags: 1: the prompt with command; 2: the command's output; and 3: the following prompt, exactly as it appeared on your screen. This allows to understand that what was asked for matches what was provided. Blkid doesn't provide all that I asked for, and neither does lsblk without -f. Example (with bulk of UUIDs redacted):
Code:

# inxi -S
System:
  Host: ab250 Kernel: 6.5.9-1-default arch: x86_64 bits: 64 Console: pty pts/0
    Distro: openSUSE Tumbleweed 20231121
# lsblk -f
NAME        FSTYPE FSVER LABEL      UUID        FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1  vfat  FAT32 PT3P01ESP  30A0-3A09    307.9M    4% /boot/efi
├─nvme0n1p2  swap  1    pt3p02swap  33ef...7799
├─nvme0n1p3  ext2  1.0  pt3p03res  c9e9...eab7  184.3M    52% /disks/res
├─nvme0n1p4  ext4  1.0  pt3p04ulcl  d612...d0b5    1.7G    54% /usr/local
├─nvme0n1p5  ext4  1.0  pt3p05home  f5b8...dddc    5.3G    12% /home
├─nvme0n1p6  ext4  1.0  pt3p06pub  c9d4...474c      6G    49% /pub
├─nvme0n1p7  ext4  1.0  pt3p07stw  3128...13f7  781.8M    85% /
├─nvme0n1p8  ext4  1.0  pt3p08s153  0ef8...3eeb    3.6G    48% /disks/s153
├─nvme0n1p9  ext4  1.0  pt3p09s151  a862...c6aa  748.1M    85% /disks/s151
├─nvme0n1p10 ext4  1.0  pt3p10deb12 d91f...224c
├─nvme0n1p11 ext4  1.0  pt3p11s155  ee53...f634    2.6G    62% /disks/s155
├─nvme0n1p12 ext4  1.0  pt3p12ub22  2509...0e81
├─nvme0n1p13 ext4  1.0  pt3p13deb13 2ac9...9299
├─nvme0n1p14 ext4  1.0  pt3p14deb11 889f...31d6
├─nvme0n1p15 ext4  1.0  pt3p15f39  61cb...a708
├─nvme0n1p16 ext4  1.0  pt3p16s154  3d90...ccbb    2.2G    66% /disks/s154
├─nvme0n1p17 ext4  1.0  pt3p17ub20  ab51...3ba3
├─nvme0n1p18 ext4  1.0  pt3p18f38  5cea...d0cd
└─nvme0n1p19 ext4  1.0  pt3p19sslo  c65c...b277    4.1G    42% /disks/sslo
#


I did not posted efibootmgr because this TW is MBR.
I do not know if you realized that unlike you, I cannot boot my TW. My outputs are just chroot environment. Thanks for your inputs.

I will re-posting the output directly from ubuntu (not from chroot):
Code:

root@zika:/home/brad# lsblk -f
NAME    FSTYPE  FSVER LABEL      UUID                                FSAVAIL FSUSE% MOUNTPOINTS
loop0                                                                        0  100% /snap/bare/5
loop1                                                                        0  100% /snap/code/145
loop2                                                                        0  100% /snap/code/146
loop3                                                                        0  100% /snap/core/16202
loop4                                                                        0  100% /snap/core/16091
loop5                                                                        0  100% /snap/core18/2796
loop6                                                                        0  100% /snap/core18/2812
loop7                                                                        0  100% /snap/core20/1974
loop8  squashfs 4.0                                                          0  100% /snap/core20/2015
loop9  squashfs 4.0                                                          0  100% /snap/core22/858
loop10  squashfs 4.0                                                          0  100% /snap/core22/864
loop11  squashfs 4.0                                                          0  100% /snap/cups/974
loop12  squashfs 4.0                                                          0  100% /snap/cups/980
loop13  squashfs 4.0                                                          0  100% /snap/firefox/3358
loop14  squashfs 4.0                                                          0  100% /snap/firefox/3416
loop15  squashfs 4.0                                                          0  100% /snap/gnome-3-28-1804/194
loop16  squashfs 4.0                                                          0  100% /snap/gnome-3-28-1804/198
loop17  squashfs 4.0                                                          0  100% /snap/gnome-3-34-1804/90
loop18  squashfs 4.0                                                          0  100% /snap/gnome-3-34-1804/93
loop19  squashfs 4.0                                                          0  100% /snap/gnome-3-38-2004/140
loop20  squashfs 4.0                                                          0  100% /snap/gnome-3-38-2004/143
loop21  squashfs 4.0                                                          0  100% /snap/gnome-42-2204/132
loop22  squashfs 4.0                                                          0  100% /snap/gnome-42-2204/141
loop23  squashfs 4.0                                                          0  100% /snap/gtk-common-themes/1534
loop24  squashfs 4.0                                                          0  100% /snap/gtk-common-themes/1535
loop25  squashfs 4.0                                                          0  100% /snap/pycharm-community/355
loop26  squashfs 4.0                                                          0  100% /snap/pycharm-community/357
loop27  squashfs 4.0                                                          0  100% /snap/snapd/20290
loop28  squashfs 4.0                                                          0  100% /snap/snap-store/638
loop29  squashfs 4.0                                                          0  100% /snap/snap-store/959
loop30  squashfs 4.0                                                          0  100% /snap/snapd-desktop-integration/57
loop31  squashfs 4.0                                                          0  100% /snap/snapd-desktop-integration/83
loop32  squashfs 4.0                                                          0  100% /snap/spotify/70
loop33  squashfs 4.0                                                          0  100% /snap/spotify/73
sda                                                                                   
├─sda1  ext4    1.0              37d6738c-0676-4fac-9bb8-9e2d0094fa47  204.6G    20% /var/snap/firefox/common/host-hunspell
│                                                                                      /
├─sda2  ntfs          Recovery    023871F43871E757                                   
├─sda3  vfat    FAT32            C47B-61F7                              64.7M    33% /boot/efi
├─sda4                                                                               
├─sda5  ntfs          Windows10  B45EABD95EAB92A2                                   
├─sda6  ntfs                      1CB605D5B605AFF6                                   
├─sda7  ext4    1.0  Ubuntu_Data a38b81ea-8929-4863-a582-c5b65ed6738f                /mnt/a38b81ea-8929-4863-a582-c5b65ed6738f
├─sda8  swap    1                044e6eb7-82ef-4199-9cb9-dab0a84ec932                [SWAP]
└─sda10 ext4    1.0  Manjaro    3c887f34-af07-4e01-8c3a-e2b9f8be9399               
sdb                                                                                   
└─sdb1  ext4    1.0              a6a51e19-de41-460f-be90-9d6438859c6f  78.6G    78% /media/brad/a6a51e19-de41-460f-be90-9d6438859c6f
sdc                                                                                   
├─sdc1  ext4    1.0  backuppc    ca701d81-d18f-4181-8b2f-b16c085e44d1                /mnt/usb-Seagate_BUP_BK_NA7PBB19-0:0-part1
├─sdc2  ext4    1.0              8ab0e067-a760-4d94-bebf-113de2f39d4c  477.5G    41% /media/brad/8ab0e067-a760-4d94-bebf-113de2f39d4c
├─sdc3  vfat    FAT32            52A8-414E                                         
├─sdc4  ext4    1.0  Gecko      287a2f71-d2d0-45d8-b300-82a19b18f1aa  23.7G    32% /mnt
├─sdc5  ext4    1.0  GeckoHome  6698c5bc-845b-4917-a290-bbf867e4410a               
└─sdc6  swap    1                ddf24e8d-e906-4300-9d99-b3ecda169f2d               
sr0                                                                                   
root@zika:/home/brad#

and the whole /etc/fstab:

Code:

root@zika:/# more /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>            <mount point>  <type>  <options>  <dump>  <pass>

UUID=287a2f71-d2d0-45d8-b300-82a19b18f1aa /              ext4    defaults,noatime 0 1
UUID=6698c5bc-845b-4917-a290-bbf867e4410a /home          ext4    defaults,noatime 0 2
UUID=52A8-414E  /boot/efi      vfat    defaults      0      1

/dev/disk/by-uuid/044e6eb7-82ef-4199-9cb9-dab0a84ec932 none swap sw 0 0
root@zika:/#


mrmazda 12-06-2023 01:22 PM

Quote:

Originally Posted by lattimro (Post 6468767)
Unfortunatelly the openSUSE forums was hacked most likely and redirects the new users to 'univention' portal

It wasn't hacked. It did have sporadic downtime recently due to migration of servers to a different city. It has been steadily working OK for me since sometime last week.

lattimro 12-06-2023 02:02 PM

Quote:

Originally Posted by mrmazda (Post 6468811)
It wasn't hacked. It did have sporadic downtime recently due to migration of servers to a different city. It has been steadily working OK for me since sometime last week.

Thanks!

mrmazda 12-06-2023 02:52 PM

Quote:

Originally Posted by lattimro (Post 6468808)
I did not posted efibootmgr because this TW is MBR.
Code:

# lsblk -f
...                                 
├─sda3  vfat    FAT32            C47B-61F7                              64.7M    33% /boot/efi
...
├─sdc3  vfat    FAT32            52A8-414E                                         
...
(fstab)
...
UUID=52A8-414E  /boot/efi      vfat    defaults      0      1
...
#


Your sda appears to be MBR partitioned, but your TW fstab says you are UEFI configured. Also you have two ESP partitions, one on sda, the other on sdc. Absent efibootmgr -v output, I don't expect to be of any more help.

lattimro 12-06-2023 04:17 PM

Quote:

Originally Posted by mrmazda (Post 6468829)
Your sda appears to be MBR partitioned, but your TW fstab says you are UEFI configured. Also you have two ESP partitions, one on sda, the other on sdc. Absent efibootmgr -v output, I don't expect to be of any more help.

you are correct, it is bit of predicament due to my machine BIOS. I have this configuration since 2014-2015 maybe and worked OK. As far as I remember TW was UEFI but right now because I can't boot TW, when I chroot from ubuntu (which is MBR/GPT!) the output is not relevant. I do not know if this make sense for you? Thanks!

Code:

root@zika:/home/brad# efibootmgr -v
EFI variables are not supported on this system.

the next output is from ubuntu (booted from /dev/sdc3):
Code:

root@zika:/home/brad# efibootmgr -v
Timeout: 0 seconds
BootOrder: 0003,0002
Boot0002* Network Adapter (IPv4 Legacy) BBS(128,Network Adapter (IPv4 Legacy),0x0).......................................................................
Boot0003* Notebook Hard Drive  BBS(HD,Notebook Hard Drive,0x500)................-...........A.......................................v.......A.........................
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
root@zika:/home/brad#

the next output is from ubuntu:
Code:

root@zika:/home/brad# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Sourcing file `/etc/default/grub.d/oem-flavour.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.2.0-37-generic
Found initrd image: /boot/initrd.img-6.2.0-37-generic
Found linux image: /boot/vmlinuz-6.2.0-36-generic
Found initrd image: /boot/initrd.img-6.2.0-36-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Manjaro Linux (23.1.0) on /dev/sda10
Found Windows Boot Manager on /dev/sda3@/EFI/Microsoft/Boot/bootmgfw.efi
Found openSUSE Tumbleweed on /dev/sdc4
Adding boot menu entry for UEFI Firmware Settings ...
done
root@zika:/home/brad#


mrmazda 12-06-2023 04:38 PM

Any installation media that can be booted in UEFI mode will suffice to collect the UEFI NVRAM state. It might be facilitated by going into BIOS and temporarily disabling CSM so that booting is only possible via UEFI. We need that efibootmgr output!!! Have you tried using the BBS hotkey menu to select TW for booting? How many entries are in it? How many for TW?

When Windows 10/11 is/are present, it's best to only install anything in UEFI mode, especially so if Windows is UEFI installed.

In whatever Linux bootloader you have booting any Linux from sda you should be able to add a boot stanza copied and edited as necessary to try to boot the TW installation. Put the stanza in the same directory as grub.cfg from which you are able to boot any Linux, in a file named custom.cfg. You may need to regenerate its grub.cfg after doing so. All my UEFI booting is configured so that my custom.cfg entries are included at the top of Grub's boot menu. This way I'm normally booting only from stanzas of my own creation. Anyone can do the same by copying /etc/grub.d/41_custom to /etc/grub.d/07_custom.

lattimro 12-06-2023 04:45 PM

Quote:

Originally Posted by mrmazda (Post 6468848)
Any installation media that can be booted in UEFI mode will suffice to collect the UEFI NVRAM state. It might be facilitated by going into BIOS and temporarily disabling CSM so that booting is only possible via UEFI. We need that efibootmgr output!!! Have you tried using the BBS hotkey menu to select TW for booting? How many entries are in it? How many for TW?

When Windows 10/11 is/are present, it's best to only install anything in UEFI mode, especially so if Windows is UEFI installed.

In whatever Linux bootloader you have booting any Linux from sda you should be able to add a boot stanza copied and edited as necessary to try to boot the TW installation. Put the stanza in the same directory as grub.cfg from which you are able to boot any Linux, in a file named custom.cfg. You may need to regenerate its grub.cfg after doing so. All my UEFI booting is configured so that my custom.cfg entries are included at the top of Grub's boot menu. This way I'm normally booting only from stanzas of my own creation. Anyone can do the same by copying /etc/grub.d/41_custom to /etc/grub.d/07_custom.

what is BBS hotkey menu?


All times are GMT -5. The time now is 10:14 PM.