Why is it every time I another Samsung 860 EVO, it seems to add a few more seconds to the boot time? It could be a hardware thing since the Mobo is a few years old. As in pre-UEFI.
-
Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntu -
Pre-uefi has nothing to do with it IMO. Are you mounting these drives at boot time?
What's the output of
sudo systemd-analyze blame -
Pardon the interruption... but systemd-analyze blame here (neon 5.18) returns exactly the same with or without sudo.
Is it supposed to do something else with sudo?
Just curious.Comment
-
Probably just me defaulting to sudo for any system command. Very long time Linux user here.
Comment
-
Maybe my other problem which took about two days to solve might give a clue. The one where I discovered I had to increase the space on my BTRFS / drive to allow more sectors for a larger than default Grub II RMB. Maybe that also affects boot time however that is just a guess. Yes the drives are all mounted at boot time.Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
OK, did you run the systemd command? Every drive mounted at boot time takes, well, time. But you're not going to know unless you look at the output of the above command. If your goal is a fast boot, remove things going on at boot, like mounting a ton of partitions. I have mine set to only mount the ones I need every day and leave the others unmounted until I plan on using them. There's other solutions as well.
As far as your other comment, I have no idea what a "Grub II RMB" is. Never heard that term nor has the internet apparently. Did you mean MBR as in Master boot record? There is a condition where, if you're using GPT partitioning, that GRUB needs additional space so you must create a "BIOS boot partition" so grub can install. I wrote about that extensively on this forum. The GPT partition table takes up more room than the older MBR (aka DOS) partition table. However if that's the case, that wouldn't effect your boot time and GRUB isn't technically part of the MBR. It uses part of the MBR to direct the computer to the boot loader.Comment
-
I have 3 drives on my laptop. I only mount /dev/sda1 at boot. It is the only drive listed in /etc/fstab."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
There was so much ouput that I decided to user my pastbin account. https://pastebin.com/Q3UdMznNOriginally posted by oshunluvr View Post
Maybe because I am using newer SSD's on an Old mobo and I had to double the size of the space for MBR that might be part of it.Last edited by steve7233; Apr 30, 2020, 07:50 PM.Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
-
Here I have: alias blm='systemd-analyze blame | head -n 20' ;·)
(which only gives the first 20 lines).
Still, there doesn't seem to be anything there to indicate that any disk mounts are taking a few seconds, does it?Comment
-
Looks like you ran it 20 times or something. You really only need it once for this sort of cursory quest. Here's yours:
Only 70 lines isn't that long. Mine is 119.Code:5.185s NetworkManager-wait-online.service 2.143s e2scrub_reap.service 2.060s Steam3.mount 901ms Not_Steam.mount 802ms systemd-journal-flush.service 757ms dev-sdc1.device 742ms mpd.service 729ms networkd-dispatcher.service 629ms systemd-logind.service 575ms upower.service 495ms udisks2.service 481ms ModemManager.service 463ms accounts-daemon.service 437ms snapd.service 405ms NetworkManager.service 365ms thermald.service 362ms apport.service 361ms rsyslog.service 349ms grub-initrd-fallback.service 346ms avahi-daemon.service 345ms systemd-journald.service 335ms pppd-dns.service 316ms gpu-manager.service 316ms grub-common.service 308ms nvidia-persistenced.service 307ms wpa_supplicant.service 288ms systemd-resolved.service 205ms systemd-timesyncd.service 107ms Steam1.mount 81ms systemd-udev-trigger.service 67ms systemd-udevd.service 67ms keyboard-setup.service 58ms user@1000.service 44ms apparmor.service 37ms systemd-modules-load.service 33ms systemd-fsck@dev-disk-by\x2duuid-52e79567\x2db78a\x2d4dd6\x2daf3a\x2d0cb611a4ac92.service 29ms systemd-fsck@dev-disk-by\x2duuid-f7a96f19\x2d7c3c\x2d4afe\x2d99fe\x2d825a4c2df2b2.service 25ms plymouth-quit.service 23ms polkit.service 22ms kerneloops.service 21ms systemd-fsck@dev-disk-by\x2duuid-f588358e\x2d7acb\x2d4a25\x2db119\x2d8e2c0d6aa8dc.service 18ms systemd-tmpfiles-clean.service 16ms systemd-tmpfiles-setup.service 15ms snapd.seeded.service 14ms systemd-sysusers.service 14ms plymouth-read-write.service 14ms plymouth-start.service 12ms systemd-sysctl.service 11ms systemd-update-utmp.service 11ms sys-kernel-debug.mount 11ms kmod-static-nodes.service 11ms user-runtime-dir@1000.service 11ms setvtrgb.service 11ms systemd-remount-fs.service 11ms dev-mqueue.mount 10ms systemd-fsck@dev-disk-by\x2duuid-79351a07\x2d32f7\x2d4095\x2d8208\x2dd2a4b7917ec6.service 10ms systemd-tmpfiles-setup-dev.service 9ms home.mount 8ms snapd.socket 8ms dev-hugepages.mount 7ms systemd-update-utmp-runlevel.service 7ms systemd-user-sessions.service 6ms console-setup.service 6ms systemd-random-seed.service 5ms rtkit-daemon.service 5ms ufw.service 3ms sddm.service 2ms sys-fs-fuse-connections.mount 2ms sys-kernel-config.mount 1ms swapfile.swap
OK, so steam is taking a long time as is network manager. The "e2scrub reap.service" is an EXT file system LVM cleaning service. You probably don't need it, but I'd research that. Also if you're not actually using NetworkManager you can turn if off and use systemd-networkd instead. It's faster. SDC1 is taking a while to mount. Probably at least part of your perception of a slow boot time. I'm curious as to why steam is part of your boot. I guess that's an option I'm not using. I use steam once in awhile, but it doesn't load like that at boot.Comment
-
SDC1 is root so definitely needed. Steam starts at boot time is an option in Staem system settings.Originally posted by oshunluvr View PostJust to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.
http://www.kubuntu.org/getkubuntuComment
Comment