You are not logged in.

#1 2017-04-18 15:08:28

olivine
Member
Registered: 2009-10-24
Posts: 19

Long hangtime at passphrase during reboot

Hello,

I have Arch installed with LVM on LUKS, and a separate unencrypted boot partition. The network adapter shows up missing after cold booting the computer, but gets set up properly after a reboot, similarly to what is described in https://bbs.archlinux.org/viewtopic.php?id=185765. However, during the reboot the system hangs for a long time (between 10s and 1 min or more) after I enter the passphrase. During the initial cold boot, that step usually takes 5-10 seconds.

Here is what I get after the reboot:

$ systemd-analyze
Startup finished in 14.107s (firmware) + 3.345s (loader) + 29.222s (kernel) + 5.936s (userspace) = 52.610s

$ systemd-analyze blame
          2.549s dev-mapper-valpelline\x2droot.device
          2.394s user@1000.service
          1.421s lvm2-pvscan@254:0.service
          1.036s org.cups.cupsd.service
           440ms NetworkManager.service
           430ms systemd-journald.service
           366ms systemd-udev-trigger.service
           360ms systemd-fsck@dev-disk-by\x2duuid-b6c86c8c\x2dd689\x2d48e1\x2db53b\x2d3381f12eb45e.service
           334ms polkit.service
           315ms systemd-journal-flush.service
           311ms systemd-modules-load.service
           306ms systemd-fsck@dev-disk-by\x2duuid-65de110b\x2d2e50\x2d4107\x2da72c\x2d7674bb610a2f.service
           306ms systemd-fsck@dev-disk-by\x2duuid-5d3e7a91\x2d5776\x2d40d1\x2db658\x2da883fad0aa97.service
           296ms colord.service
           268ms systemd-timesyncd.service
           266ms systemd-tmpfiles-setup-dev.service
           264ms systemd-binfmt.service
           218ms kmod-static-nodes.service
           207ms systemd-remount-fs.service
           204ms mnt-valpelline.mount
           199ms tmp.mount
           199ms dev-mqueue.mount
           191ms dev-hugepages.mount
           179ms systemd-udevd.service
           178ms systemd-tmpfiles-setup.service
           177ms alsa-restore.service
           163ms systemd-update-utmp.service
           152ms var.mount
           146ms wpa_supplicant.service
           146ms systemd-backlight@backlight:intel_backlight.service
           136ms systemd-rfkill.service
           135ms home.mount
           126ms systemd-sysctl.service
           124ms systemd-random-seed.service
           115ms sys-kernel-debug.mount
            99ms systemd-fsck@dev-disk-by\x2duuid-ACA6\x2dFA13.service
            93ms systemd-logind.service
            89ms rtkit-daemon.service
            83ms systemd-tmpfiles-clean.service
            77ms boot.mount
            66ms sys-kernel-config.mount
            64ms systemd-user-sessions.service
            50ms proc-sys-fs-binfmt_misc.mount
            30ms sys-fs-fuse-connections.mount

If I understand correctly, the problem is the "(kernel)" part, for which I would like to get more information.

$ journalctl -b  gives:

https://ptpb.pw/NUdj

and here is the /etc/fstab file:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/mapper/valpelline-root
UUID=b3601846-b2b0-41cd-99c2-986346a5b545	/         	ext4      	rw,relatime,data=ordered	0 1
# /dev/sda1
UUID=ACA6-FA13      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2
# /dev/mapper/valpelline-var
UUID=b6c86c8c-d689-48e1-b53b-3381f12eb45e	/var      	ext4      	rw,relatime,data=ordered	0 2
# /dev/mapper/valpelline-home
UUID=65de110b-2e50-4107-a72c-7674bb610a2f	/home     	ext4      	rw,relatime,data=ordered	0 2
# /dev/mapper/valpelline-data
UUID=5d3e7a91-5776-40d1-b658-a883fad0aa97	/mnt/valpelline	ext4      	rw,relatime,data=ordered	0 2

The system worked nicely (no network adapter issue, and reasonable boot time) for over a year and a half before an update this winter. I've tried fixing the network adapter issue at cold boot by changing various things in the BIOS settings without success.  Is the slow boot time related to the network adapter issue, or to the way I have my partitions set up? I am not really sure how to proceed from here. Any hint or suggestion would be appreciated.

Offline

Board footer

Powered by FluxBB