Long boot time involves start jobs

English Install/Boot/Login
1

When I boot my desktop this comes on the screen:

*     ] A start job is running for dev-disk-by\x2duuid-8e11c9fa\x2d8aa8\x2d45ce\x2da3eb\x2dfe9ec5574c73.device (7s / 1min 30s)

This runs for the full 1 min and 30s.

further down

  OK  ] Reached target Basic System.
         Starting File System Check on /dev/disk/by-uuid/47fb4eec-2898-496c-b294-4b281005a4cd...

the above uuid refers to /dev/sda9 where Tumbleweed is installed.

even further down

  OK  ] Reached target Initrd Default Target.
         Starting Cleaning Up and Shutting Down Daemons...
         Starting Plymouth switch root service...

and further down

*     ] A start job is running for wicked managed network interfaces (16s / no limit)

and at the end before the gui

  OK  ] Reached target Timers.

I ran blkid from konsole

linux-h65n:/home/hw-suse # blkid
/dev/sda1: UUID="70b34116-c50c-483b-b327-072e53ecfbe5" TYPE="swap" PARTUUID="4773ed51-01"
/dev/sda2: UUID="447f2936-8a0d-4a2b-9a83-13cc42152856" TYPE="ext4" PARTUUID="4773ed51-02"
/dev/sda5: UUID="58bcc840-a1e6-488b-8964-c043104ee687" TYPE="ext4" PARTUUID="4773ed51-05"
/dev/sda6: UUID="99c1df3b-6831-4cdc-83de-d00506835f57" TYPE="ext4" PTTYPE="dos" PARTUUID="4773ed51-06"
/dev/sda7: LABEL="pclos_mate" UUID="f467dda3-5707-45ba-bd8e-31e2f60f45be" TYPE="ext4" PARTUUID="4773ed51-07"
/dev/sda8: UUID="eeff1b13-0388-4112-aa99-665e1a1d29b4" TYPE="ext4" PARTUUID="4773ed51-08"
/dev/sda9: LABEL="64_bit_pclos_kde" UUID="47fb4eec-2898-496c-b294-4b281005a4cd" TYPE="ext4" PARTUUID="4773ed51-09"
/dev/sda10: LABEL="Home64bit" UUID="f0273316-2213-4753-93a4-602fdd9adf80" TYPE="ext4" PARTUUID="4773ed51-0a"
/dev/sda11: UUID="703eb6bb-c51e-418a-ba49-aefd1b1665ca" TYPE="ext4" PARTUUID="4773ed51-0b"
/dev/sda12: UUID="9d66c6b2-6c5f-40f0-88c7-290b66673c79" TYPE="ext4" PARTUUID="4773ed51-0c"
/dev/sdb1: LABEL="Home" UUID="5881fe2d-7f0e-433b-a40c-498ab203b5c4" TYPE="ext4" PARTUUID="14c814c8-01"

This is my fstab file:

UUID=47fb4eec-2898-496c-b294-4b281005a4cd /                    ext4       acl,user_xattr        1 1
UUID=70b34116-c50c-483b-b327-072e53ecfbe5 swap                 swap       defaults              0 0
UUID=5881fe2d-7f0e-433b-a40c-498ab203b5c4 /home                ext4       defaults              1 2

Any ideas as to what is causing those start jobs?

2

Hi
Still looking for your install media perhaps? This should be disabled after install.

Not a clean shutdown so it’s checking disks/partitions on boot…

Wicked can sometimes be slow…

3

I have been wondering about the install media. I just deleted it.

How do I insure a clean shutdown?

Wicked doesn’t seem to take very long. It is the other start job that lasts 1 min and 30 secs.

4

Hi
From a Desktop environment there should be a poweroff button?

From the command line as root user;


systemctl poweroff
5

Then I have been getting a clean shutdown because I have been using the shut down icon showing on the menu.

I have just noticed that before the start job begins there is a quick message that says “ushib (not sure of the spelling) can’t find an input interrupt point”. Could this be part of my problem or separate?

6

Just had a similar problem on Leap 42.3 and I tracked it down to hibernation files left on swap. As your swap partition has a different UUID from 8e11c9fa … I am guessing - because my problem was quite different from yours except that I encountered similar symptons - that a UUID has changed.

7

One more thought: in YaST>Bootloader>Kernel parameters, check that the UUID for resume matches your swap UUID. That was one of the changes I had to make to resolve the problem.

8

What does the output of the terminal command

systemd-analyze blame

look like it may give you a clue.