I don’t know why they are downvoting you, it’s true. I’m dealing with this kind of problem currently… sometimes the boot lasts forever to the point that I have to use AltGr+SysRq commands to force kill everything… other times it simply boots as normal. It’s not consistent at all.
At least before with the old init it was relatively simple to dig into the scripts and make changes to them… I feel now with systemd it’s a lot more opaque and harder to deal with. I wouldn’t even know how to approach the problem, systemd-analyze blame does not help, since the times I actually get to boot look normal. But I do believe it must have to do with the mountpoints because often they are what takes the longest.
Any advice on what should I do would be welcome.
Also, I have a separate Bazzite install in my living room TV, and while that one does not get locked, sometimes NetworkManager simply is not running after boot… I got fed up to the point that I wrote a workaround by creating a rc.local script to have it run, so I can have it available reliably when the system starts (that fixed it… though some cifs mountpoints often do not get mounted… so I’m considering adding the mount command to the same rc.local script too…).
You can play around with the mount option nofail, if that’s set, systemd will not wait for the mount point to be ready and continue booting normally. Can be useful with HDDs that take a while to spin up and aren’t needed for the boot process (e.g. backup drives, etc.).
Another thing to look out for: SDCards or USB flash drives that might randomly fail to “spin up” and hang, unplugging those helps.
I don’t know why they are downvoting you, it’s true. I’m dealing with this kind of problem currently… sometimes the boot lasts forever to the point that I have to use AltGr+SysRq commands to force kill everything… other times it simply boots as normal. It’s not consistent at all.
At least before with the old init it was relatively simple to dig into the scripts and make changes to them… I feel now with systemd it’s a lot more opaque and harder to deal with. I wouldn’t even know how to approach the problem,
systemd-analyze blame
does not help, since the times I actually get to boot look normal. But I do believe it must have to do with the mountpoints because often they are what takes the longest. Any advice on what should I do would be welcome.Also, I have a separate Bazzite install in my living room TV, and while that one does not get locked, sometimes NetworkManager simply is not running after boot… I got fed up to the point that I wrote a workaround by creating a rc.local script to have it run, so I can have it available reliably when the system starts (that fixed it… though some cifs mountpoints often do not get mounted… so I’m considering adding the mount command to the same rc.local script too…).
You can play around with the mount option
nofail
, if that’s set, systemd will not wait for the mount point to be ready and continue booting normally. Can be useful with HDDs that take a while to spin up and aren’t needed for the boot process (e.g. backup drives, etc.).Another thing to look out for: SDCards or USB flash drives that might randomly fail to “spin up” and hang, unplugging those helps.