Really slow boot time - 10 minutes

[NeonRed]

I'm going to throw a wild guess here:
1. Partition issue / disk issue, need a full disk wipe + error checking
2. Configuration issue i.e., fstab does not any or the correct UUIDs, correct ones can be found somewhere in /dev/
    One time I forgot both the admin and root password, and had to be creative to get access to my system, and during the process fstab became empty and much slower boot resulted.
3. Incompatibility between OS or Kernel and hardware.  Try the 32 bit version of LL2.8 as a baseline.

It's probably a configuration issue since it's a laptop and until recent years I couldn't get a successful boot off the laptop, PClinuxOS was the first success, I had tried dozens.
It's likely there is also a kernel better suited for your hardware/laptop.  Google your laptop and kernel.

Good luck,

Eric

[trinidad]

I think KE series is the amd cpu. I'd guess you should be running 64 bit then. Try hitting the F1 key after writeable ram read. If you were running a readable boot you would see the timeout after the 1024 and the F1 prompt. There are bios floppies available for this lap.

TC

[Jerry]

I don't know how you're producing a 52 page system report, it should be 1 small text file - https://www.linuxliteos.com/manual/hardware.html#sysreport Cheers.

[Iestynrl]

Hello - Thx for the top Jerry, I didn't realise I'd posted it incorrectly - Thx for the tip.

So, here goes:

Hi, I've slowly moved up from 2.6 on 2 notebooks and 2.8 on this Presario 2100 with 1gb Ram. 2.8 had what I consider a normal boot time - LL3 on the Presario takes aprox 15 minutes. It only has USB 1, which I used Kplop to boot up from - I can't get my USB2 PCAMIA slots to boot even with plop for that. I've got LL3 on a 32gb stick & 8gb stick to trial it on the notebooks and it's fine on those.

Here's my system report: (I've also carried out a full system report - showing the innards of this machine, but that's 52 pages long!

Any ideas?

Thx for your time. Iestyn
dads@dads-Presario-2100-KE-Mx-xx:~$ systemd-analyze blame
    10min 5.644s dev-sda1.device
    9min 47.677s systemd-udev-trigger.service
    3min 45.122s ntp.service
    1min 14.577s apt-daily.service
         25.069s nmbd.service
         21.814s samba-ad-dc.service
         14.320s NetworkManager-wait-online.service
         10.457s smbd.service
          9.050s NetworkManager.service
          7.753s lightdm.service
          7.591s apparmor.service
          7.109s ufw.service
          6.310s ModemManager.service
          6.270s accounts-daemon.service
          5.436s systemd-udevd.service
          5.267s thermald.service
          3.845s lvm2-monitor.service
          3.587s systemd-tmpfiles-setup-dev.service
          2.691s upower.service
          2.526s gpu-manager.service
          2.405s grub-common.service
          2.176s systemd-journald.service
          2.104s virtualbox-guest-utils.service
lines 1-23