USB Persistence for LL v6.0

[Francois]

Thank you for you reply. It does not seem like one specific service is the problem:

Code:

linux  ~  systemd-analyze blame
6min 20.360s networking.service
3min 20.178s rc-local.service
1min 55.957s gpu-manager.service
1min 35.868s nmbd.service
1min 33.907s blueman-mechanism.service
1min 30.049s smbd.service
1min 28.598s networkd-dispatcher.service
1min 16.578s systemd-resolved.service
1min 10.434s NetworkManager.service
     53.107s rsyslog.service
     47.916s packagekit.service
     45.693s update-notifier-download.service
     35.826s bluetooth.service
     32.628s secureboot-db.service
     32.242s systemd-udev-settle.service
     31.989s dev-sda4.device
     31.712s cups.service
     31.026s dev-loop0.device
     29.983s systemd-journal-flush.service
     29.139s NetworkManager-wait-online.service
     28.943s WolfLandBuilder-firstboot.service
     28.567s alsa-restore.service
     28.560s casper-md5check.service

Code:

 linux  ~  systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @10min 16.217s
└─multi-user.target @10min 16.217s
  └─plymouth-quit-wait.service @10min 16.216s +1ms
    └─rc-local.service @6min 56.037s +3min 20.178s
      └─network-online.target @6min 56.031s
        └─network.target @6min 56.031s
          └─wpa_supplicant.service @4min 5.645s +2ms
            └─dbus.service @1min 10.133s
              └─basic.target @1min 7.212s
                └─sockets.target @1min 7.212s
                  └─uuidd.socket @1min 7.212s
                    └─sysinit.target @1min 5.702s
                      └─systemd-journald.service @9min 53.578s +16.198s
                        └─systemd-journald.socket @1.309s
                          └─-.mount @1.298s
                            └─-.slice @1.298s

And this is a benchmark of the usb-data partition:



I'm not sure what that bottom spike at the beginning is, perhaps the boot process wasn't totally over when I launched the benchmark.