After upgrading from 17.10, I've experienced longer boot times. At first it took more than 5 minutes.
dmesg revealed the culprit was a non-existent floppy drive, that kernel tried to find.
Promptly removing that, the 5 minutes went down to about 40 seconds, which I feel is still more than it took before the update. Running
dmesg again shows it takes 30 seconds to mount a filesystem (full output), with the following message:
[ 36.362834] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
I'm booting from an SSD, with two other hard drives plugged in, one of which is formatted in ext4, but holds no system data. I presume this is the SSD. During these 30 seconds, no text is displayed, nor is splash, just a blank screen.
Now, I said that it feels slower than before update, because I don't have exact times from before, so my first question is, is it normal to take 30 seconds to mount a filesystem, and if no, how to find out more about what could be causing the delay?
Turning swap on or off has no effect whatosever
Meanwhile I've also installed another hard drive into my computer. It seems to have further prolonged my boot time by some 10 seconds, with another line appearing in
dmesg output, right before the aforementioned 30-second delay:
[ 3.312351] hid-generic 0003:09DA:F613.0005: input,hiddev0,hidraw4: USB HID v1.11 Keyboard [COMPANY USB Device] on usb-0000:00:12.1-1/input2 [ 17.169519] random: crng init done [ 51.611617] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
systemd-analyze blame results are here
meanwhile after several restarts, the
dmesg lines I blamed above changed their times thusly:
[ 3.348384] hid-generic 0003:09DA:F613.0005: input,hiddev0,hidraw4: USB HID v1.11 Keyboard [COMPANY USB Device] on usb-0000:00:12.1-1/input2 [ 34.091886] random: crng init done [ 36.488321] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
I'll do a couple of restarts to find out whether this changes randomly, or stays the same (the code block in the first edit is from the first boot after inserting the extra HDD).
EDIT 2.5: the
random: crng init done usually appears in times as shown in edit 1, rarely as in edit 2. It seems to be... random.
systemd-analyze blameand edit your question to include the output of this command?