Here denotes my attempts to speedup booting as R4.1 on newer hardware is not stable enough and reboot may be required to reset the hardware into known good states.
After inputed the correct hard disk encryption password on boot, press F1 to see the actual booting log in real time. Here one can see which step is taking the most of the time along with how much time has been spent on booting.
systemd-analyzeis useful to spot the slowest process and to spot the paths of services, however please take your risk when you want to modify the services by hand.
systemd-analyze blamecan tell directly the slowest step;
systemd-analyze unit-filescan lead you to the config files of corresponding services. If you want to add tracer to them, you may choose to edit the config files. For example
Avoid booting up
sys-firewallVMs on boot, if you are facing boot time problems - booting such VMs can have unpredictable results, as their booting may fail or take too much time.
sudo systemctl enable debug-shell.serviceprovide you a root shell at /dev/tty9 early at boot. Notice that this will introduce a security hole so disable it after you have done your debugging.
If you found that
lvm2related process takes the majority of your booting time and with step 4 you find out that
thin_checkis the culprit, then this can be referred. Since I have installed qubes os on a 2T hdd, the booting time for
thin_checktakes as long as 10-20 minutes. (I am still testing this setup out)