42 seconds boot time. It seems to have taken maybe 10-15 seconds before.
I think I screwed something up. The time difference changed after I enlarged “/” partition and move swap. Swap was against the root partition, so I moved it first then enlarged the root ("/") partition.
easyt50@8300 ~ $ systemd-analyze
Startup finished in 36.485s (kernel) + 5.513s (userspace) = 41.999s
graphical.target reached after 5.509s in userspace
easyt50@8300 ~ $ systemd-analyze blame
Everything below this was less then 100ms.
I had problems enlarging the root partition using gparted but got it done. Did not doc my steps, so I can not answer details about problems.
This getting a bit long, but other info I can add is 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).
‘#’/ was on /dev/sda8 during installation
UUID=da6ec12c-c8bb-4132-8157-bd77d62721d1 / ext4 errors=remount-ro 0 1
‘#’/home was on /dev/sda6 during installation
UUID=0af7ea4c-9721-49b3-afa7-912c27c9d4cc /home ext4 defaults 0 2
'#'swap now on /dev/sda8
UUID=8c42de44-5d68-466e-93e3-9a9b342905b3 none swap sw 0 0
'#'swap was on /dev/sda9 during installation
'#“UUID=455eee28-2ab3-4fc0-895d-4035700b40c4 none swap sw 0 0
Swap was not updated after I did the move, so I updated to the correct /dev/sda. This did seem to help with the boot time. I place ‘’ around '#” b/c it enlarged the print.
I also tried to run fsck. When I got the grub menu, I went into recovery mode and used fsck. I got back.
“fsck from util-linux 2.31.1”
“dev/sda6 is mounted”
“e2fsck: Cannot continue, aborting”
“Finish, please press enter.”
Now the good news - after the boot, everything seems to be running fine.
So I am worry about 3 things.
Why the long boot time?
Why fsck will not run?
Even tho system seems fine, am I sitting on a time bomb? ie: when the system goes to use the expanded area.