Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: A start job is running... & Secure Boot / MOK

  1. #1

    Default A start job is running... & Secure Boot / MOK

    Hi,

    1.

    upon boot I get a
    Code:
    A start job is running for dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device
    I've already checked fstab, but there is no mentioning of any of these numbers.
    this has problably something to do with this: https://forums.opensuse.org/showthre...l-SSD-what-now, since it's happening since I created a BTRFS partition on an external drive. This drive does appears in fstab, but is set to noauto and the UUID does not resemble any of the above mentioned numbers.

    2.

    After every Kernel update I get a "blue screen" upon boot "SHIM Uefi key management" - I have enabled secure boot. I can just continue booting normally by pressing enter, but there are some options I can chose from "Press any key to perform MOK management" but I don't want to mess up my system.
    What do to? Simply disable secure boot?

    Thanks.

  2. #2
    Join Date
    Feb 2018
    Location
    Romania
    Posts
    484

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    After every Kernel update I get a "blue screen" upon boot "SHIM Uefi key management" - I have enabled secure boot. I can just continue booting normally by pressing enter, but there are some options I can chose from "Press any key to perform MOK management" but I don't want to mess up my system.
    What do to? Simply disable secure boot?.
    Hello,

    Simply enter your root password. (thank you Malcolm ).

    https://forums.opensuse.org/showthre...00#post2864300

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,681
    Blog Entries
    3

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    1. upon boot I get a
    Code:
    A start job is running for dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device
    I've already checked fstab, but there is no mentioning of any of these numbers.
    I suggest you check "/etc/default/grub" to see if those numbers show up.

    I had a similar situation with a recently installed Leap 15.0 Beta. Booting took a long time, with a 90 second pause with nothing appearing to happen. I managed to find that message. And I found the disk it was trying to access in "/etc/default/grub" (the "resume=" parameter on the default boot command). It had configured for "resume=" a swap partition that happened to be available during install, but is not available during normal running. Once I fixed that, and then regenerated the grub boot menu, it has been booting a lot faster.

    2. After every Kernel update I get a "blue screen" upon boot "SHIM Uefi key management" - I have enabled secure boot. I can just continue booting normally by pressing enter, but there are some options I can chose from "Press any key to perform MOK management" but I don't want to mess up my system.
    What do to? Simply disable secure boot?
    Select "Enroll key" (or is it "enroll MoK"), then enter root password when asked for a password. This will cause a new openSUSE key to be enrolled (for checking signatures on kernels). And you won't see this prompt again unless they decide to enroll another key. Yes, it is a bit confusing.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  4. #4

    Default Re: A start job is running... & Secure Boot / MOK

    Thanks, successfully enrolled the MOK key.

    However the start job problem still persists. I can't find any entry in fstab or grub that resembles
    Code:
    dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,681
    Blog Entries
    3

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    Thanks, successfully enrolled the MOK key.

    However the start job problem still persists. I can't find any entry in fstab or grub that resembles
    Code:
    dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device
    The start job is unrelated to secure-boot.

    I would suggest you grep for just the string "9ca59c23" to see if you can identify that disk.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  6. #6
    Join Date
    Sep 2014
    Location
    Germany
    Posts
    915

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    ...upon boot I get a
    Code:
    A start job is running for dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device
    I've already checked fstab, but there is no mentioning of any of these numbers.
    If you do (as root in a console)
    Code:
    # dracut --print-cmdline
    will the result contain the above mentioned UUID (9ca59c23...)?

    If so, rebuilding your initrd-file with
    Code:
    # dracut -f
    might help.

    Regards

    susejunky

  7. #7
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,303

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    Thanks, successfully enrolled the MOK key.

    However the start job problem still persists. I can't find any entry in fstab or grub that resembles
    Code:
    dev-disk-by\x2duuid-9ca59c23\x2d4cd7\x2d592f\x2d50cb09a2669c.device
    Had this issue too. Fixed it by running "dracut -f".
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #8

    Default Re: A start job is running... & Secure Boot / MOK

    Unfortunately dracut -f did not help :-(

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,303

    Default Re: A start job is running... & Secure Boot / MOK

    Quote Originally Posted by SF6 View Post
    Unfortunately dracut -f did not help :-(
    It's easy to miss one step. That happened when I cleaned up the HDD by removing all system partitions and expanding the remaining one. Make sure to switch off secure boot and run all off the following:

    - grep UUID /etc/default/grub
    - grep UUID /boot/grub2/grub.cfg
    - dracut -f
    - grub2-install --target=x86_64-efi
    - grub2-mkconfig -o /boot/grub2/grub.cfg

    Then shut down the machine and boot from 'opensuse'
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  10. #10
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: A start job is running... & Secure Boot / MOK

    Start out by giving me the output of:
    Code:
    fdisk -l -o +uuid
    Please post the above command and the resulting output here between code tags (the # icon/symbol in the menu above the forum editor window).

    Also, (or?) in Yast->Boot Loader under Kernel Parameters make certain that "mysterious" UUID is not the one listed in the "resume=" line
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •