Hi, I’ve recently come from Windows after a long period of doing everything I could to stay within WSL.
I’d like to improve my startup time and while looking around this forum I noticed that my userspace startup seems to be an order of magnitude slower than what I’ve seen posted in other threads.
I think the issue is potentially related to mounting my HDD as for the first minute or so when I try to run the analysis I get the following:
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
And then when I go to check which jobs are running as per the hint:
JOB UNIT TYPE STATE
56 mnt-sdb1.mount start waiting
57 dev-sdb1.device start running
lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
└─sda2 8:2 0 232.6G 0 part /
sdb 8:16 0 931.5G 0 disk /mnt/chonky
This might be a red herring but any help with how I could reduce the user space start time would be appreciated.
Startup finished in 11.710s (firmware) + 5.513s (loader) + 2.514s (kernel) + 4.229s (userspace) = 23.968s
graphical.target reached after 4.229s in userspace.
I had mounted my HDD using the gnome-disk-utility, following a guide I found online. Doing it directly in /etc/fstab/ has done the trick. I must have configured it through the disk utility incorrectly as it was matching via label and not by UUID. I’m not sure exactly why that has an affect on user space start up. Ill have to look that up separately.
According to the lsblk output you supplied you don’t have any partitions on sdb. If it’s trying to mount a partition that doesn’t exist, then presumably the default timeout will apply which is 1m30s.
Interesting, it doesn’t have any partitions, do you have any ideas on how it can be mounted now? Because its not hitting the default timeout now but I havent added any partitions
It is mounted, but I haven’t added any partitions:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
└─sda2 8:2 0 232.6G 0 part /
sdb 8:16 0 931.5G 0 disk /mnt/chonky
The mount point is working as expected, I can add/remove/edit files.
My question now, based on your comment about it hitting a default time out because it doesn’t have any partitions, is: why isn’t it hitting that default time out now?
It is not recommended to use a disk without a partition table. Sooner or later you will get into deep trouble if you do things the windows-way in linux.
Some reading-material to read on.
Switch from Windows - how to use GNU/Linux:
Working with Drives
Filesystem, Permissions:
You also can find good information in the arch wiki and in the manjaro wiki