Long Booting Time

Support
1

My system is taking a lot of time to boot
here is output for systemd-analyze blame:

[kunals97@Kunal-LINUX ~]$ systemd-analyze blame
13.627s systemd-journal-flush.service                                            
10.288s lvm2-monitor.service                                                     
 9.725s dev-sda3.device                                                          
 9.039s snapd.service                                                            
 5.537s polkit.service                                                           
 3.729s systemd-udevd.service                                                    
 3.305s bluetooth.service                                                        
 3.282s NetworkManager.service                                                   
 3.223s systemd-logind.service                                                   
 2.475s apparmor.service                                                         
 2.443s systemd-fsck@dev-disk-by\x2duuid-C773\x2d6771.service                    
 1.850s ldconfig.service                                                         
 1.502s ModemManager.service                                                     
 1.389s var-lib-snapd-snap-amass-851.mount                                       
 1.319s var-lib-snapd-snap-chromium-1421.mount                                   
 1.312s snapd.apparmor.service                                                   
 1.310s var-lib-snapd-snap-chromium-1424.mount                                   
 1.302s var-lib-snapd-snap-core-10444.mount                                      
 1.272s gdm.service                                                              
 1.260s upower.service                                                           
 1.244s var-lib-snapd-snap-core18-1932.mount                                     
 1.166s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount                    
 1.148s systemd-sysusers.service                                                 
 1.135s udisks2.service                                                          
 1.076s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount                    
  915ms var-lib-snapd-snap-nmap-2044.mount                                       
  892ms var-lib-snapd-snap-nmap-2061.mount                                       
  890ms systemd-tmpfiles-setup-dev.service                                       
  841ms dev-loop12.device                                                        
  745ms accounts-daemon.service                                                  
  703ms dev-loop11.device                                                        
  693ms systemd-journald.service                                                 
  670ms systemd-random-seed.service                                              
  635ms dev-loop2.device                                                         
  597ms tlp.service                                                              
  593ms wpa_supplicant.service                                                   
  535ms colord.service                                                           
  534ms boot-efi.mount                                                           
  516ms dev-loop9.device                                                         
  469ms systemd-journal-catalog-update.service                                   
  425ms ufw.service                                                              
  421ms dev-hugepages.mount                                                      
  418ms modprobe@drm.service                                                     
  417ms dev-mqueue.mount                                                         
  416ms sys-kernel-debug.mount                                                   
  415ms sys-kernel-tracing.mount                                                 
lines 1-46...skipping...
13.627s systemd-journal-flush.service                                            
10.288s lvm2-monitor.service                                                     
 9.725s dev-sda3.device                                                          
 9.039s snapd.service                                                            
 5.537s polkit.service                                                           
 3.729s systemd-udevd.service                                                    
 3.305s bluetooth.service                                                        
 3.282s NetworkManager.service                                                   
 3.223s systemd-logind.service                                                   
 2.475s apparmor.service                                                         
 2.443s systemd-fsck@dev-disk-by\x2duuid-C773\x2d6771.service                    
 1.850s ldconfig.service                                                         
 1.502s ModemManager.service                                                     
 1.389s var-lib-snapd-snap-amass-851.mount                                       
 1.319s var-lib-snapd-snap-chromium-1421.mount                                   
 1.312s snapd.apparmor.service                                                   
 1.310s var-lib-snapd-snap-chromium-1424.mount                                   
 1.302s var-lib-snapd-snap-core-10444.mount                                      
 1.272s gdm.service                                                              
 1.260s upower.service                                                           
 1.244s var-lib-snapd-snap-core18-1932.mount                                     
 1.166s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount                    
 1.148s systemd-sysusers.service                                                 
 1.135s udisks2.service                                                          
 1.076s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount                    
  915ms var-lib-snapd-snap-nmap-2044.mount                                       
  892ms var-lib-snapd-snap-nmap-2061.mount                                       
  890ms systemd-tmpfiles-setup-dev.service                                       
13.627s systemd-journal-flush.service                                            
10.288s lvm2-monitor.service                                                     
 9.725s dev-sda3.device                                                          
 9.039s snapd.service                                                            
 5.537s polkit.service                                                           
 3.729s systemd-udevd.service                                                    
 3.305s bluetooth.service                                                        
 3.282s NetworkManager.service                                                   
 3.223s systemd-logind.service                                                   
 2.475s apparmor.service                                                         
 2.443s systemd-fsck@dev-disk-by\x2duuid-C773\x2d6771.service                    
 1.850s ldconfig.service                                                         
 1.502s ModemManager.service                                                     
 1.389s var-lib-snapd-snap-amass-851.mount                                       
 1.319s var-lib-snapd-snap-chromium-1421.mount                                   
 1.312s snapd.apparmor.service                                                   
 1.310s var-lib-snapd-snap-chromium-1424.mount                                   
 1.302s var-lib-snapd-snap-core-10444.mount                                      
 1.272s gdm.service                                                              
 1.260s upower.service                                                           
 1.244s var-lib-snapd-snap-core18-1932.mount                                     
 1.166s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount                    
 1.148s systemd-sysusers.service                                                 
 1.135s udisks2.service                                                          
 1.076s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount                    
  915ms var-lib-snapd-snap-nmap-2044.mount                                       
  892ms var-lib-snapd-snap-nmap-2061.mount                                       
  890ms systemd-tmpfiles-setup-dev.service                                       
13.627s systemd-journal-flush.service                                            
10.288s lvm2-monitor.service                                                     
 9.725s dev-sda3.device                                                          
 9.039s snapd.service                                                            
13.627s systemd-journal-flush.service                                            
10.288s lvm2-monitor.service                                                     
 9.725s dev-sda3.device                                                          
 9.039s snapd.service                                                            
 5.537s polkit.service                                                           
 3.729s systemd-udevd.service                                                    
 3.305s bluetooth.service                                                        
 3.282s NetworkManager.service                                                   
 3.223s systemd-logind.service                                                   
 2.475s apparmor.service                                                         
 2.443s systemd-fsck@dev-disk-by\x2duuid-C773\x2d6771.service                    
 1.850s ldconfig.service                                                         
 1.502s ModemManager.service                                                     
 1.389s var-lib-snapd-snap-amass-851.mount                                       
 1.319s var-lib-snapd-snap-chromium-1421.mount                                   
 1.312s snapd.apparmor.service                                                   
 1.310s var-lib-snapd-snap-chromium-1424.mount                                   
 1.302s var-lib-snapd-snap-core-10444.mount                                      
 1.272s gdm.service                                                              
 1.260s upower.service                                                           
 1.244s var-lib-snapd-snap-core18-1932.mount                                     
 1.166s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount                    
 1.148s systemd-sysusers.service                                                 
 1.135s udisks2.service                                                          
 1.076s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount                    
  915ms var-lib-snapd-snap-nmap-2044.mount                                       
  892ms var-lib-snapd-snap-nmap-2061.mount                                       
  890ms systemd-tmpfiles-setup-dev.service                                       
  841ms dev-loop12.device                                                        
  745ms accounts-daemon.service                                                  
  703ms dev-loop11.device                                                        
  693ms systemd-journald.service                                                 
  670ms systemd-random-seed.service                                              
  635ms dev-loop2.device                                                         
  597ms tlp.service                                                              
  593ms wpa_supplicant.service                                                   
  535ms colord.service                                                           
  534ms boot-efi.mount                                                           
  516ms dev-loop9.device                                                         
  469ms systemd-journal-catalog-update.service                                   
  425ms ufw.service                                                              
  421ms dev-hugepages.mount                                                      
  418ms modprobe@drm.service                                                     
  417ms dev-mqueue.mount                                                         
  416ms sys-kernel-debug.mount                                                   
  415ms sys-kernel-tracing.mount                                                 
  411ms kmod-static-nodes.service                                                
  410ms var-lib-snapd-snap-snapd-10492.mount

also,
[kunals97@Kunal-LINUX ~]$ sudo bootctl
[sudo] password for kunals97:
Couldn’t find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
System:
Firmware: n/a (n/a)
Secure Boot: disabled
Setup Mode: user
Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Boot loader sets ESP partition information
          ESP: n/a
         File: └─n/a

Random Seed:
 Passed to OS: no
 System Token: not set

Boot Loaders Listed in EFI Variables:
        Title: Manjaro
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/87ca5283-67e4-5845-afd7-8ef416fc59d2
         File: └─/EFI/Manjaro/grubx64.efi
2

That error clearly shows what is wrong and how to fix it…
eg. you either don’t have an ESP or there is something wrong with your setup.

For the time spend of those 2 top services people who would like to help you, would need more info on your setup also…

So lets start by providing:

  • Output of sudo fdisk -x
  • Bootloader you use
  • Kernel parameters you use.
  • Your /etc/mkinitcpio.conf
  • Mentioning if you use disk encryption or not, and when yes: Explain how it is setup in terms of layers used wrt hard-disk usage.
    (eg. full-disk or inside an lvm etc.)

PS:
Why did you flag it with the gnome tag, bootup has little to nothing to do with your DE…

1 Like
3

thanks for replying :slight_smile:
1.here is output of sudo fdisk -x

Summary 
    [sudo] password for kunals97: 
    Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
    Disk model: HGST HTS541010A9
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 477B5504-BC0B-E448-9D63-2E3F70F1C238
    First LBA: 2048
    Last LBA: 1953525134
    Alternative LBA: 1953525167
    Partition entries LBA: 2
    Allocated partition entries: 128

    Device        Start        End    Sectors Type-UUID                            UUID                                 Name Attrs
    /dev/sda1      2048    1050623    1048576 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 87CA5283-67E4-5845-AFD7-8EF416FC59D2      
    /dev/sda2   1050624   17827839   16777216 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F 1357574E-1D44-8348-AD9C-105EA1E19086      
    /dev/sda3  17827840 1953520031 1935692192 0FC63DAF-8483-4772-8E79-3D69D8477DE4 C69805DD-8777-E24A-9557-B2CC6D8DF0E1      


    Disk /dev/loop0: 118.38 MiB, 124125184 bytes, 242432 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop1: 55.36 MiB, 58052608 bytes, 113384 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop2: 162.87 MiB, 170778624 bytes, 333552 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop3: 14.5 MiB, 15204352 bytes, 29696 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop4: 97.86 MiB, 102612992 bytes, 200416 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop5: 242.63 MiB, 254418944 bytes, 496912 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop6: 64.77 MiB, 67915776 bytes, 132648 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop7: 8.61 MiB, 9027584 bytes, 17632 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop8: 8.61 MiB, 9027584 bytes, 17632 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop9: 31.07 MiB, 32579584 bytes, 63632 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop10: 31.06 MiB, 32571392 bytes, 63616 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop11: 172.96 MiB, 181366784 bytes, 354232 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    Disk /dev/loop12: 185.39 MiB, 194400256 bytes, 379688 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes```

2.Bootloader: GRUB

3.mkinitcpio.conf :-

Summary 
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

4.No Encryption

I don’t know kernel parameters since i’m noob at linux

I used bootinfo script and thought this might be useful

Summary 
        Boot Info Script 0.61      [1 April 2012]

============================= Boot Info Summary: ===============================

=> No boot loader is installed in the MBR of /dev/sda.

sda1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/boot/bootx64.efi /efi/Manjaro/grubx64.efi

sda2: __________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

sda3: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Manjaro Linux () ()
Boot files: /boot/grub/grub.cfg /etc/fstab

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HGST HTS541010A9
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT

GUID Partition Table detected.

Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 1,050,623 1,048,576 Data partition (Windows/Linux)
/dev/sda2 1,050,624 17,827,839 16,777,216 Swap partition (Linux)
/dev/sda3 17,827,840 1,953,520,031 1,935,692,192 Data partition (Linux)

“blkid” output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/loop1 squashfs
/dev/loop10 squashfs
/dev/loop11 squashfs
/dev/loop12 squashfs
/dev/loop2 squashfs
/dev/loop3 squashfs
/dev/loop4 squashfs
/dev/loop5 squashfs
/dev/loop6 squashfs
/dev/loop7 squashfs
/dev/loop8 squashfs
/dev/loop9 squashfs
/dev/sda1 C773-6771 vfat
/dev/sda2 fe2a21fa-d91b-44e9-8744-d8fd09bea6d5 swap
/dev/sda3 c28f51fa-dc58-490b-b225-fb22cb321112 ext4

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda1 /boot/efi vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda3 / ext4 (rw,noatime)

=========================== sda3/boot/grub/grub.cfg: ===========================

DO NOT EDIT THIS FILE

It is automatically generated by grub-mkconfig using templates

from /etc/grub.d and settings from /etc/default/grub

BEGIN /etc/grub.d/00_header

insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ “${next_entry}” ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="–id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ “${prev_saved_entry}” ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z “${boot_once}” ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}

set menu_color_normal=light-gray/black
set menu_color_highlight=green/black

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root=‘hd0,gpt3’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275=‘ieee1275//disk@0,gpt3’ --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 c28f51fa-dc58-490b-b225-fb22cb321112
else
search --no-floppy --fs-uuid --set=root c28f51fa-dc58-490b-b225-fb22cb321112
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_IN
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=10

Fallback hidden-timeout code in case the timeout_style feature is

unavailable.

elif sleep --interruptible 10 ; then
set timeout=0
fi

END /etc/grub.d/00_header

BEGIN /etc/grub.d/10_linux

menuentry ‘Manjaro Linux’ --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-simple-c28f51fa-dc58-490b-b225-fb22cb321112’ {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root=‘hd0,gpt3’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275=‘ieee1275//disk@0,gpt3’ --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 c28f51fa-dc58-490b-b225-fb22cb321112
else
search --no-floppy --fs-uuid --set=root c28f51fa-dc58-490b-b225-fb22cb321112
fi
linux /boot/vmlinuz-5.8-x86_64 root=UUID=c28f51fa-dc58-490b-b225-fb22cb321112 rw quiet apparmor=1 security=apparmor resume=UUID=fe2a21fa-d91b-44e9-8744-d8fd09bea6d5 udev.log_priority=3
initrd /boot/intel-ucode.img /boot/initramfs-5.8-x86_64.img
}
submenu ‘Advanced options for Manjaro Linux’ $menuentry_id_option ‘gnulinux-advanced-c28f51fa-dc58-490b-b225-fb22cb321112’ {
menuentry ‘Manjaro Linux (Kernel: 5.8.18-1-MANJARO x64)’ --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-5.8.18-1-MANJARO x64-advanced-c28f51fa-dc58-490b-b225-fb22cb321112’ {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root=‘hd0,gpt3’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275=‘ieee1275//disk@0,gpt3’ --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 c28f51fa-dc58-490b-b225-fb22cb321112
else
search --no-floppy --fs-uuid --set=root c28f51fa-dc58-490b-b225-fb22cb321112
fi
linux /boot/vmlinuz-5.8-x86_64 root=UUID=c28f51fa-dc58-490b-b225-fb22cb321112 rw quiet apparmor=1 security=apparmor resume=UUID=fe2a21fa-d91b-44e9-8744-d8fd09bea6d5 udev.log_priority=3
initrd /boot/intel-ucode.img /boot/initramfs-5.8-x86_64.img
}
menuentry ‘Manjaro Linux (Kernel: 5.8.18-1-MANJARO x64 - fallback initramfs)’ --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option ‘gnulinux-5.8.18-1-MANJARO x64-fallback-c28f51fa-dc58-490b-b225-fb22cb321112’ {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root=‘hd0,gpt3’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275=‘ieee1275//disk@0,gpt3’ --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 c28f51fa-dc58-490b-b225-fb22cb321112
else
search --no-floppy --fs-uuid --set=root c28f51fa-dc58-490b-b225-fb22cb321112
fi
linux /boot/vmlinuz-5.8-x86_64 root=UUID=c28f51fa-dc58-490b-b225-fb22cb321112 rw quiet apparmor=1 security=apparmor resume=UUID=fe2a21fa-d91b-44e9-8744-d8fd09bea6d5 udev.log_priority=3
initrd /boot/initramfs-5.8-x86_64-fallback.img
}
}

END /etc/grub.d/10_linux

BEGIN /etc/grub.d/20_linux_xen

END /etc/grub.d/20_linux_xen

BEGIN /etc/grub.d/30_os-prober

END /etc/grub.d/30_os-prober

BEGIN /etc/grub.d/30_uefi-firmware

menuentry ‘UEFI Firmware Settings’ $menuentry_id_option ‘uefi-firmware’ {
fwsetup
}

END /etc/grub.d/30_uefi-firmware

BEGIN /etc/grub.d/40_custom

This file provides an easy way to add custom menu entries. Simply type the

menu entries you want to add after this comment. Be careful not to change

the ‘exec tail’ line above.

END /etc/grub.d/40_custom

BEGIN /etc/grub.d/41_custom

if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z “${config_directory}” -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi

END /etc/grub.d/41_custom

BEGIN /etc/grub.d/60_memtest86+

if [ “${grub_platform}” == “pc” ]; then
menuentry “Memory Tester (memtest86+)” --class memtest86 --class gnu --class tool {
search --fs-uuid --no-floppy --set=root --hint-ieee1275=‘ieee1275//disk@0,gpt3’ --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 c28f51fa-dc58-490b-b225-fb22cb321112
linux16 /boot/memtest86+/memtest.bin
}
fi

END /etc/grub.d/60_memtest86+

=============================== sda3/etc/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).

UUID=C773-6771 /boot/efi vfat umask=0077 0 2
UUID=fe2a21fa-d91b-44e9-8744-d8fd09bea6d5 swap swap defaults,noatime 0 2
UUID=c28f51fa-dc58-490b-b225-fb22cb321112 / ext4 defaults,noatime 0 1

=================== sda3: Location of files loaded by Grub: ====================

   GiB - GB             File                                 Fragment(s)

=============================== StdErr Messages: ===============================

cat: /tmp/BootInfo-dZfDQmp7/Tmp_Log: No such file or directory
mdadm: No arrays found in config file or automatically

4

Can you please edit your post and put three back-ticks (on own lines) before and after terminal outputs that you pasted?
Also if it is long, you can afterwards select that long portion including the back-ticks and click the gear icon in the editor and choose “Hide details”.
This will make your post more readable by viewers.
Example:

Click to see terminal output 
some terminal output
some terminal output
some terminal output
1 Like
5

Hi @Kunal :wink:

The time it takes to start the services looks like you have a spinning disk and not a SSD. If so, then this behavior is quite normal. It could improve it a bit by changing the scheduler:

https://wiki.archlinux.org/index.php/Improving_performance#Changing_I/O_scheduler

Could you also post just the output of this command?:

systemd-analyze

Another improvement could be masking some unnessecary services. If you don’t have lvm partitions, then you could mask this service:

sudo systemctl mask lvm2-monitor.service

Snapd also slow it down. Remove all snaps and snapd.

1 Like
6

Here is the output of systemd-analyze:

$ systemd-analyze
Startup finished in 4.847s (firmware) + 11.196s (loader) + 3.628s (kernel) + 1min 31.193s (userspace) = 1min 50.865s 
graphical.target reached after 30.578s in userspace
7

This is a known slow HDD model … hence some services that depend on it will take longer.

This can take longer also if the journal file size is large. Check that with:
journalctl --disk-usage

Personally i prefer small size even on fast HDD/SSD. For that you can edit the config file for journal:
sudo nano /etc/systemd/journald.conf
and set the

#SystemMaxUse=

to

SystemMaxUse=50M
8

Side note:

Learning new things every day :wink:

Would’n it be better to use an override config instead of altering that file, or does that not work in this case?
eg:

# /etc/systemd/journald.conf.d/admin.conf
[Journal]
SystemMaxUse=50M
9

Yes, but depending on OP experience i didn’t want to get too technical … :smiley:

1 Like
10

How do I know if I have lvm partitions, so that I can safely disable the service?

11

You should know as it’s a system you installed/set up?!

$ sudo vgs

If something shows up, there are some volume groups.

12

I created the partitions and installed. I didn’t know about volume groups. BTW, I found this.

Nothing shows up. Then I can disable the service, right?

13

Arch wiki is an excellent source of information.

Yes.

For the future and ease of mind: If you are in doubt wether your action leave the system in an unbootable state - have a bootable usb ready and manjaro-chroot from there to undo/fix any mistakes.

1 Like