Quantcast
Channel: openSUSE Forums
Viewing all articles
Browse latest Browse all 40713

Delay on startup after switching to SSD on laptop + Upgrade to 13.1

$
0
0
After switching to the SSD from the HDD on my laptop (and following upgrade to 13.1) I'm experiencing a pretty long delay on startup. It happens somewhere before Login request.

If I use arrow keys, then I can see output telling me something about time out on trying to connect to a partition on my old HDD as well as a couple of other messages. Last of them says about apparmor.
The strange thing is, the graphical startup screen seems to blink multiple times and console seems to generate messages, but they seems to be the same messages again and again.
The whole system start till the login screen takes about one minute.

In the boot logs I've found following entries:
Code:

/usr/sbin/cron[2311]: pam_unix(crond:session): session opened for user root by (uid=0)
systemd[1]: Starting user-0.slice.
systemd[1]: Created slice user-0.slice.
systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device...
systemd[1]: Starting User Manager for 0...
systemd[1]: Starting Session 2 of user root.
systemd[1]: Started Session 2 of user root.
systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0)
systemd[2312]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
...
systemd[1]: Job dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device/start timed out.systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device.
systemd[1]: Dependency failed for /dev/disk/by-id/ata-Hitachi_HTS545050B9A300_120517PBN4751710V8WE-part5.

And the systemd-analyze tells, that I should take a look on the user space:
Code:

Startup finished in 3.731s (kernel) + 3min 312ms (userspace) = 3min 4.043s
It brought me to the idea, that my system tries to find/mount the exchanged hdd and waits till timeout and possibly repeats the attempts multiple times.

The systemd-analyze blame command generates following output:
Code:

          566ms systemd-udev-settle.service
          335ms apparmor.service
          325ms SuSEfirewall2.service
          175ms media-DataStore.mount
          163ms SuSEfirewall2_init.service
          108ms ModemManager.service
          101ms systemd-fsck@dev-disk-by\x2duuid-60ca15d7\x2d01ce\x2d4f48\x2d95ce\x2d60d2ef77997d.service
            84ms xdm.service
            76ms kmod-static-nodes.service
            72ms bluetooth.service
            71ms systemd-vconsole-setup.service
            71ms media-readyshare.mount
            68ms avahi-daemon.service
            68ms systemd-sysctl.service
            66ms wpa_supplicant.service
            64ms systemd-readahead-replay.service
            63ms systemd-readahead-collect.service
            63ms NetworkManager.service
            63ms dev-hugepages.mount
            62ms dev-mqueue.mount
            62ms systemd-udev-root-symlink.service
            53ms systemd-tmpfiles-clean.service
            51ms rsyslog.service
            48ms systemd-logind.service
            45ms systemd-remount-fs.service
            42ms alsa-restore.service
            41ms udisks2.service
            32ms polkit.service
            27ms lvm2-activation.service
            27ms lvm2-activation-early.service
            26ms user@0.service
            26ms plymouth-start.service
            25ms user@1000.service
            21ms systemd-udev-trigger.service
            15ms plymouth-read-write.service
            14ms home.mount
            14ms rc-local.service
            12ms systemd-tmpfiles-setup-dev.service
            11ms upower.service
            9ms systemd-tmpfiles-setup.service
            8ms systemd-modules-load.service
            7ms systemd-journal-flush.service
            7ms systemd-backlight@acpi_video0.service
            6ms NetworkManager-dispatcher.service
            5ms systemd-update-utmp.service
            5ms systemd-random-seed.service
            5ms systemd-readahead-done.service
            5ms NetworkManager-wait-online.service
            5ms systemd-update-utmp-runlevel.service
            4ms var-lock.mount
            4ms var-run.mount
            4ms sys-kernel-debug.mount
            3ms sys-fs-fuse-connections.mount
            3ms systemd-user-sessions.service
            3ms systemd-udevd.service

Any help would be appreciated.

Viewing all articles
Browse latest Browse all 40713

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>