Never mind, I had aI have read older threads here that implies that what I see on the boot screen is a red herring. I had it hang for two minutes on systemd-rfkill.service, but after purging rfkill and disabling and deleting the service and socket files, it now hangs on systemd-timesyncd.service for about as long. Can somebody point me in the direction I need to look to find out what really holds it up?
I have an USB dongle (Asus with an 8814au) with a bigger antenna on it (I have this in my boat under the wheelhouse, with the Asus on the roof to connect to my cabin), and this is the main network connection. But taking it into the cabin plugging it into my LAN does not change anything, and the USB network driver is loaded after this long wait anyway, I think. So I doubt that it has anything to do with that. I have docker with five images, but I don't think they are loaded until after this pause either. Can I see in any logs what helds it up?
moment. It was an SSD that used to be connected to it that had entries in fstab. Removing those entries fixed it. 
Statistics: Posted by Mastiff — Sun Nov 17, 2024 10:35 am