Upgrade / Installed on 12-2-2023
Are you using remote file systems such as Samba of NFS? If not then you may want to try disabling them, and while you’re at it you might want to disable the NetworkManager-wait-online.service.
You sure are running with a lot of drives. I would start by disconnecting any USB drives. Are your drives listed in fstab? If so, do you use the nofail flag in fstab? Do you use the discard=async flag on your btrfs drives in fstab? Perhaps it would be best if you could post your fstab in its entirety.
I would also make sure the firmwares are all up to date in your drives and also scan your drives for errors/pending failures. It seems to me that all these drives are negatively impacting your boot times. Check your logs for errors related to your drives.
Is your VPN set to run at startup? if so disable it.
As your computer is fairly recent with decent specs, you could probably get by without preload entirely. IMO you could probably uninstall it and it wound not negatively affect your performance.
1 Like
-
Drives are not listed in FSTAB other then the main one per say. I do not automount any.
-
VPN is not set to start at start-up, they all set to prompt for username and pass when needed. No creds are saved.
-
I have tried disconnect all but the 6 internal SSD’s made no diff. Tried to boot PC with only keyboard and mouse. Still the same. Roll back snapshot and its almost instant on. I can check firmwares, all my samsung SSDs are up to date and the WD’s as well as of a month ago. Again though no issue if I restore the snapshot.
-
I do use samba, but do not have anything mapped with it, I only use it when I need to put a movie onto my NAS server. Not set to map automaticly.
-
I disabled preload.state, no differnece really.
I will try disabling network manager and see what happens. I will give this a shot, then I am going to restore the snapshot I think, at least before monday. so I can get back to normal boot / reboot times during work hours.
ill try disabling network manager here in an hour or so and see what happens.
Trying to think of way to compare whats starting now, that was not prior to updating. Or compare startup times between now and once I restore the snapshot. I will try compare some of the logs I have posted and see if anything stands out as well.
I did try the LTS kernel, made no difference.
FSTAB Contents:
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=A89B-F5E9 /boot/efi vfat defaults,noatime 0 2
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e / btrfs subvol=/@,defaults,noatime,compress=zstd 0 0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /home btrfs subvol=/@home,defaults,noatime,compress=zstd
0 0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /root btrfs subvol=/@root,defaults,noatime,compress=zstd
0 0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /srv btrfs subvol=/@srv,defaults,noatime,compress=zstd 0
0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /var/cache btrfs subvol=/@cache,defaults,noatime,compress=zstd
0 0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /var/log btrfs subvol=/@log,defaults,noatime,compress=zstd 0
0
UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zstd 0
0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Please reread my prior post, as I made some last second edits just before you posted.
It is NetworkManager-wait-online.service that you want to disable not network manager itself.
1 Like
Won’t network-online.target feel sorry?
1 Like
Disabled, might have helped some.
I noticed it sits about 22 seconds at /boot/efi
& then proceeds thru page and sits another 42 seconds at
Target Graphical Interface
very strange, I removed my second video card to see if that helped as well, but no change. I will revert the snap for now, fingers crossed and try updating again in a few days.
I’m thinking you’re asking if it’s going to be missed. It isn’t really required unless you’re mounting network drives at boot.
1 Like
Played my snap back, boots in 15 seconds less ;-). Guess Ill wait a few weeks and try again and see what happens.
Thank you for all of you that tried to help, very odd.
Have you tried booting without the PCI passthrough kernel parameters?
Did you find significant errors in your logs. Please post unedited outputs from dmesg and journalctl from your last startup with a long delay.
3 posts were split to a new topic: Slow boot II
The other topic that was split has resulted in a workaround that may help your situation.
So, if you can tolerate using the free Nvidia driver for a while this should hold you over until things are properly corrected.
1 Like
No I didnt try it without the PassThru on, I will try that when I brave the update again here in a few days. I use the GPU pass thru dialy for work for its own GPU though. But happy to try on a weekend.
For now the snap but everything back and life is good.
I could try this, I saw that post about NVIDIA on another forum. Made me wonder. I may just not update for a month then try and see if there is a fix first. Thank you for responses, apprecaite it. Glad to know I may not be the only one.
Tried it, with no KVM IOMMU items. No go, made no differnece.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.