Results 1 to 2 of 2

Thread: Longer Boot Time Because of plymouth-quit-wait.service and fstrim.service.

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    2023-Mar
    Posts
    1

    Question Longer Boot Time Because of plymouth-quit-wait.service and fstrim.service.

    Hello. I have a triple-boot of Kali linux Windows and Ubuntu. I did move my partitions including EFI, SWAP, home, and root partition to another ssd. I also exand my partition from 100gb to 400gb. I always had this issue but after doing those it appears to be increased. Maybe it is a coincidence. For the details I will add couple outputs.
    Code:
    grep VERSION /etc/os-release
    VERSION_ID="2023.3"VERSION="2023.3"
    VERSION_CODENAME=kali-rolling
    
    
    sudo fdisk -l 
    
    Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
    Disk model: INTEL SSDPEKNU512GZ                     
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 32B76904-C88E-4A75-9F3B-23D3BC8875CD
    
    
    Device             Start       End   Sectors   Size Type
    /dev/nvme1n1p1      2048    206847    204800   100M EFI System
    /dev/nvme1n1p2    206848    239615     32768    16M Microsoft reserved
    /dev/nvme1n1p3    239616 781490175 781250560 372.5G Microsoft basic data
    /dev/nvme1n1p4 781490176 783443967   1953792   954M EFI System
    /dev/nvme1n1p5 799068160 801021951   1953792   954M EFI System
    
    
    
    
    Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
    Disk model: Samsung SSD 970 EVO Plus 1TB            
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 84D79523-B4A0-433F-8BC9-7556C9BE1808
    
    
    Device             Start        End   Sectors   Size Type
    /dev/nvme0n1p1        34      32767     32734    16M Microsoft reserved
    /dev/nvme0n1p2     32768   58626047  58593280  27.9G Linux filesystem
    /dev/nvme0n1p3  58626048   60626943   2000896   977M Linux swap
    /dev/nvme0n1p4  60626944  974823423 914196480 435.9G Microsoft basic data
    /dev/nvme0n1p5 974823424  976777215   1953792   954M EFI System
    /dev/nvme0n1p6 976777216  978978815   2201600     1G EFI System
    /dev/nvme0n1p7 978978816 1953521663 974542848 464.7G Linux filesystem
    
    
    
    
    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 @1min 35.876s
    └─multi-user.target @1min 35.876s
      └─plymouth-quit-wait.service @1min 31.513s +4.361s
        └─systemd-user-sessions.service @1min 31.507s +3ms
          └─network.target @1min 31.504s
            └─wpa_supplicant.service @1min 31.496s +7ms
              └─dbus.service @1min 30.444s +19ms
                └─basic.target @1min 30.437s
                  └─sockets.target @1min 30.437s
                    └─snapd.socket @1min 30.417s +19ms
                      └─sysinit.target @1min 30.412s
                        └─snapd.apparmor.service @656ms +115ms
                          └─apparmor.service @619ms +34ms
                            └─local-fs.target @618ms
                              └─run-snapd-ns-lxd.mnt.mount @1min 32.020s
                                └─run-snapd-ns.mount @1min 31.840s
                                  └─local-fs-pre.target @238ms
                                    └─systemd-tmpfiles-setup-dev.service @232ms +5ms
                                      └─systemd-tmpfiles-setup-dev-early.service @220ms +11ms
                                        └─kmod-static-nodes.service @207ms +9ms
                                          └─systemd-journald.socket @203ms
                                            └─-.mount @173ms
                                              └─-.slice @173ms
    
    
    
    
    
    
    systemd-analyze time 
    Startup finished in 5.228s (firmware) + 3.966s (loader) + 35.604s (kernel) + 1min 35.910s (userspace) = 2min 20.708s 
    graphical.target reached after 1min 35.876s in userspace.
    
    
    
    systemd-analyze blame   
    56.766s fstrim.service
     4.361s plymouth-quit-wait.service
     1.192s fwupd.service
     1.011s NetworkManager.service
      713ms snap.lxd.activate.service
      632ms snapd.service
      437ms systemd-modules-load.service
      225ms dev-nvme0n1p4.device
      194ms [email protected]
      159ms udisks2.service
      139ms networking.service
      115ms snapd.apparmor.service
      104ms systemd-udev-trigger.service
       97ms upower.service
       86ms systemd-journald.service
       83ms systemd-journal-flush.service
       77ms dev-loop18.device
    If I missed any important outputs do not hesitate to ask.

  2. #2
    Join Date
    2021-May
    Location
    UK
    Posts
    780
    so 3 operating systems, but 5 EFI partitions... Have you tried simply rebuilding GRUB, your system is hanging whilst its trying to make sense of your start up config

Similar Threads

  1. Replies: 2
    Last Post: 2022-10-11, 11:24
  2. haveged.service failing to start on boot
    By krogstad in forum ARM Archive
    Replies: 0
    Last Post: 2020-12-31, 15:14
  3. Replies: 2
    Last Post: 2016-10-09, 21:20
  4. Replies: 1
    Last Post: 2014-03-29, 20:32

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •