Running PureOS byzantium and have a quite long boot sequence, which I’m trying to fix.
I have two warnings, which are probably a hint for the relatively long boot time:
From cryptsetup: couldn't determine device type, assuming default (plain).
I get this warning about 12 times at each boot.
A search on the internet doesn’t really show me any useful solutions about this…
The second one is: Gave up waiting for suspend/resume device
I just got rid of this by adding plain to the options for the swap partition (not the root partition!) in /etc/crypttab and running update-initramfs -u. It’s “plain” (as in no luks header) so the assumption makes sense.
That’s what I did. I put it as first option. “plain” here doesn’t mean unencrypted, it means that there is no header to identify the encryption algorithm and such, which would be fairly pointless when using a random key every boot. Explicitly specifying it avoids an auto-detection step.
(Though I haven’t noticed an improvement in boot speed)
I assume you know this but for others here you can enable / disable the various services being run with systemd. It is quite an elegant system. Nothing in your list pops out at me except for lm-sensors service as being something that can easily be disabled, but you likely want that running on boot anyway.
OK, but I am sure something is wrong. It takes more than 45 seconds from hitting Enter after writing the disk-decryption password to the login screen with i7 on L13 and the SSD disk it has. This is not normal. ArchLinux on lenovo X61, a machine of the year 2000 originally with WinXP, now with an SSD installed but with those old processors, takes less than 20 seconds to boot up. Manjaro on i5 on an HPtouchSmart takes a few seconds to bootup to the login screen.
I do not want to say that PureOS is worse. I want to say that something is wrong. There must be a bug somewhere. Unless all this time has to do with the encrypted disk. If this is the case, then OK.
This is a wild shot in the dark and spoken from a bit of ignorance on the startup procedure, but since network manager-wait-online.service is taking so long, perhaps its having trouble either connecting or verifying its connected to the internet? Perhaps if you changed to a different DNS server it would speed up?
It may or may not be relevant, but it’s an easy check.
Me? I am, but I’m speaking from a time when my internet was taking forever to load web pages, turned out the DNS server (is that like saying ATM machine?) I was using was having issues. I switched to a different one and the issue went away.