Boot interruption

[ainals]

I recently did a fresh Mageia 7.1 install on an old laptop. It was dual-boot but had grub2 configured ok. Everything was running smoothly for a while until I tried to install magea-prime and the associated proprietary drivers. After failing to get mageia-prime running, I did mageia-prime-uninstall to undo the install. After that, I've been interrupted during boot almost everytime. The boot process stops and asks for the root password or Ctrl-D to continue.
I took this as a some kind of disk failure. I couldn't figure out which partition was at fault because systemd run things in parallel. After learning about systemd-analye blame and reading https://forums.mageia.org/en/viewtopic.php?f=7&t=13140&p=77006&hilit=systemd+analyze+blame#p77006 I figured out it was my /home partition. On the next boot, I fcsk'ed it and it corrected a lot of journal errors.
The following reboot sailed through ok. But the next bootup process stopped again with the same request for root password or Ctrl-D. This time my /root and /home were already mounted. I removed the windows partitions from /etc/fstab thinking it was trying to deal with the windows partition that failed to start after a windows 10 feature update. But everytime I rebooted, the same thing happen, the boot process stopped and I had to do a Ctrl-D to continue. I booted systemrescuecd and fsck'ed the root and home partition and they were clean.
The system because really slow once it finished booting and I logged in. Starting Firefox or Chrome would take in excess of 5 minutes before I could use it. Commands at the command line would pause for a while before continuing. I used gnome-disks to check SMART parameters and the short test showed no errors.

So I appreciate any help or ideas where to look for the cause of the problem.

Here are the output of the diagnostic commands (The postfix entry was in the most recent boot. In all the previous boots, the target (?) that consumed the most time was mandriva-everytime)

Code: Select all

# systemd-analyze time
Startup finished in 13.861s (firmware) + 1min 9.471s (loader) + 1min 25.458s (kernel) + 18min 40.042s (userspace) = 21min 28.833s
graphical.target reached after 13min 41.678s in userspace

# uname -a
Linux localhost.localdomain 5.5.9-desktop-1.mga7 #1 SMP Thu Mar 12 08:02:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

# systemd-analyze blame
      5min 173ms postfix.service
    4min 51.265s mandriva-everytime.service
    3min 44.452s systemd-tmpfiles-clean.service
    3min 30.523s dev-sda11.device
     2min 1.804s network-up.service
    1min 31.321s shorewall.service
    1min 28.019s systemd-logind.service
    1min 28.012s avahi-daemon.service
    1min 11.104s systemd-udevd.service
     1min 9.249s sensord.service
     1min 4.094s network.service
     1min 1.851s resolvconf.service
         43.749s mga-bg-res.service
         33.306s udisks2.service
         31.334s systemd-tmpfiles-setup.service
         29.425s systemd-tmpfiles-setup-dev.service
         28.758s systemd-backlight@backlight:intel_backlight.service
         27.039s ModemManager.service
         26.448s fedora-readonly.service
         25.521s dkms-autorebuild.service
         24.900s chronyd.service
         23.834s lm_sensors.service
         20.863s plymouth-start.service
         17.281s systemd-fsck-root.service
         14.061s preload.service
         12.849s systemd-journal-flush.service
         12.047s shorewall6.service
         11.373s polkit.service
         11.052s cups.service
          9.976s systemd-user-sessions.service
          9.953s mdmonitor.service
          9.086s gpm.service
          8.682s msec.service
          8.682s partmon.service
          7.794s dbus.service
          7.744s upower.service
          5.684s accounts-daemon.service
          5.648s systemd-sysctl.service
          4.795s acpid.service
          4.440s plymouth-quit.service
          4.436s plymouth-quit-wait.service
          3.776s dracut-shutdown.service
          3.628s dev-hugepages.mount
          3.627s sys-kernel-debug.mount
          3.064s systemd-rfkill.service
          2.766s systemd-update-utmp.service
          2.538s mdmonitor-takeover.service
          1.870s systemd-random-seed.service
          1.821s dev-mqueue.mount
          1.448s systemd-vconsole-setup.service
          1.428s dmraid-activation.service
          1.159s systemd-remount-fs.service
           969ms systemd-modules-load.service
           955ms systemd-udev-trigger.service
           945ms kmod-static-nodes.service
           612ms bluetooth.service
           499ms lvm2-activation.service
           440ms dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap
           356ms dnf-makecache.service
           294ms systemd-journald.service
           219ms systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service
           112ms lvm2-monitor.service
            98ms lvm2-activation-early.service
            82ms home.mount
            58ms user@1000.service
            58ms plymouth-read-write.service
            48ms fedora-loadmodules.service
            24ms systemd-udev-settle.service
            11ms tmp.mount
            11ms systemd-update-utmp-runlevel.service
            10ms user-runtime-dir@1000.service
             6ms rtkit-daemon.service
             3ms sys-fs-fuse-connections.mount

Code: Select all

systemd-analyze critical-chain
graphical.target @13min 41.678s
└─multi-user.target @13min 41.678s
  └─network.service @9min 37.390s +1min 4.094s
    └─resolvconf.service @8min 35.538s +1min 1.851s
      └─basic.target @8min 35.500s
        └─mandriva-everytime.service @3min 44.234s +4min 51.265s
          └─local-fs.target @8min 10.261s
            └─home.mount @5min 34.511s +82ms
              └─systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service @5min 34.248s +219ms
                └─local-fs-pre.target @5min 34.247s
                  └─lvm2-monitor.service @5min 34.135s +112ms
                    └─systemd-journald.socket @1min 48.666s
                      └─-.mount @1min 48.612s
                        └─system.slice @1min 48.612s
                          └─-.slice @1min 48.612s


My disk configs

Code: Select all

# lsblk -f

NAME    FSTYPE  LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                             
├─sda1  ntfs    WINRE_DRV   6AE61DB7E61D848B                                   
├─sda2  vfat    SYSTEM_DRV  B020-3591                                           
├─sda3  vfat    LRS_ESP     7E25-59BC                                           
├─sda4                                                                         
├─sda5  ntfs    Windows8_OS EAEE290AEE28D09D                                   
├─sda6  ntfs    LENOVO      8E82CA9582CA8167                                   
├─sda7  ntfs    PBR_DRV     00F22DDDF22DD824                                   
├─sda8                                                                         
├─sda9  swap                f88a7451-3c7c-4fb6-a48f-e5e713027b7e                [SWAP]
├─sda10 ext4                74317e21-9abd-43ce-ac8d-0a2943da2a36   26.4G    91% /home
└─sda11 ext4                27f9d6d3-47b4-46a5-9969-4f403b20d347   35.5G    23% /
sr0     iso9660 SYSRCD603   2019-04-14-11-35-22-00   

# more /etc/fstab
# Entry for /dev/sda11 :
UUID=27f9d6d3-47b4-46a5-9969-4f403b20d347 / ext4 noatime,acl 1 1
# Entry for /dev/sda10 :
UUID=74317e21-9abd-43ce-ac8d-0a2943da2a36 /home ext4 noatime,acl 1 2
# Entry for /dev/sda5 :
#UUID=EAEE290AEE28D09D /media/win_c ntfs-3g defaults,nofail,umask=000 0 0
# Entry for /dev/sda6 :
#UUID=8E82CA9582CA8167 /media/win_d ntfs-3g defaults,nofail,umask=000 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda9 :
UUID=f88a7451-3c7c-4fb6-a48f-e5e713027b7e swap swap defaults 0 0

# journalctl -ab | grep -i 74317e21
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device: Job dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device/start timed out.
May 02 17:21:20 localhost.localdomain systemd[1]: Timed out waiting for device /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36.
May 02 17:21:20 localhost.localdomain systemd[1]: systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service: Job systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device: Job dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device/start failed with result 'timeout'.
May 02 17:23:36 localhost.localdomain systemd[1]: Starting File System Check on /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36...
May 02 17:23:36 localhost.localdomain systemd[1]: Started File System Check on /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36.
May 02 17:23:36 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 02 17:23:36 localhost.localdomain kernel: audit: type=1130 audit(1588411416.422:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'



I've also attached the journalctl -xb output.
Thanks in advance.

[doktor5000]

Seems your /home filesystem takes really long, because of a dependency on the swap partition, but the swap partition seems to be the cause of the issue, because it times out.

How do you usually shut down your system?

I'd suggest to boot again from system rescue CD, and format your swap partition, but keep the current UUID.

Code: Select all

mkswap -U f88a7451-3c7c-4fb6-a48f-e5e713027b7e /dev/sda9

Although you may need to adjust /dev/sda9 to what it is in the live system.

May 02 17:20:38 localhost.localdomain systemd[1]: Starting udev Kernel Device Manager...
-- Subject: A start job for unit systemd-udevd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit systemd-udevd.service has begun execution.
--
-- The job identifier is 14.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device: Job dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device/start timed out.
May 02 17:21:20 localhost.localdomain systemd[1]: Timed out waiting for device /dev/disk/by-uuid/f88a7451-3c7c-4fb6-a48f-e5e713027b7e.
-- Subject: A start job for unit dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device has finished with a failure.
--
-- The job identifier is 51 and the job result is timeout.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for /dev/disk/by-uuid/f88a7451-3c7c-4fb6-a48f-e5e713027b7e.
-- Subject: A start job for unit dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap has finished with a failure.
--
-- The job identifier is 50 and the job result is dependency.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for Swap.
-- Subject: A start job for unit swap.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit swap.target has finished with a failure.
--
-- The job identifier is 49 and the job result is dependency.
May 02 17:21:20 localhost.localdomain systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap: Job dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device: Job dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.device/start failed with result 'timeout'.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device: Job dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device/start timed out.
May 02 17:21:20 localhost.localdomain systemd[1]: Timed out waiting for device /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36.
-- Subject: A start job for unit dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device has finished with a failure.
--
-- The job identifier is 27 and the job result is timeout.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for /home.
-- Subject: A start job for unit home.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit home.mount has finished with a failure.
--
-- The job identifier is 24 and the job result is dependency.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for Local File Systems.
-- Subject: A start job for unit local-fs.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit local-fs.target has finished with a failure.
--
-- The job identifier is 23 and the job result is dependency.
May 02 17:21:20 localhost.localdomain systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
May 02 17:21:20 localhost.localdomain systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/74317e21-9abd-43ce-ac8d-0a2943da2a36.
-- Subject: A start job for unit systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l ... temd-devel
--
-- A start job for unit systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service has finished with a failure.
--
-- The job identifier is 25 and the job result is dependency.
May 02 17:21:20 localhost.localdomain systemd[1]: systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service: Job systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service/start failed with result 'dependency'.
May 02 17:21:20 localhost.localdomain systemd[1]: dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device: Job dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.device/start failed with result 'timeout'.

[ainals]

I shutdown using the shutdown button on which ever WM I am using. Right now, I'm using cinnamon or MATE and sometimes KDE.
Thank you for the analysis and suggestion. I'm not sure whatyou my to adjust "/dev/sda9 to what it is on my system". I checked the configuration for the swap. but couldn't find any refence to dev/sda9 other than the swapon command

Code: Select all

# systemctl list-dependencies swap.target
swap.target
● └─dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap

# systemctl list-dependencies   dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap
dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap
# systemctl list-dependencies   dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap
dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap

# systemctl cat   dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap
No files found for dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap.
# systemctl cat dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap
No files found for dev-disk-byx2duuid-f88a7451x2d3c7cx2d4fb6x2da48fx2de5e713027b7e.swap.

# swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/sda9 partition 7.8G   4M   -2


I booted into systemrescuecd and followed the instruction on making the swap partition.
I rebooted and again it went into emergency mode. I entered the root password but it kept scrolling. When the prompt came up, it wasn't displaying what I was typing but it was executing the commands I typed. I managed to check that the /root and /home partition was already mounted so I couldn't fsck them. I gave up and exited. The message that came out eventually was "systemctl status systemd-journal-flush.service for details." I tried the command later when I logged in but it didn't finish or took so long I stopped it.
After some more waiting the login screen came up and I logged in. Applications were really slow to start but once started, was ok. Except that from time to time, everything kept pausing/freezing for brief periods before returning to normal. I could move the mouse and typein commands but nothing happens. Then it unpauses and whatever click or command I did was executed. top didn't show anything consuming a lot of CPU or memory. My guess is a kernel issue. I had the same things happen on another PC with Mageia 6. It went away when I upgraded.

Below are the diagnostic outputs

Code: Select all

# systemd-analyze blame --no-pager
   11min 50.854s mandriva-everytime.service
    8min 14.839s dev-sda11.device
    7min 14.970s shorewall.service
      5min 247ms postfix.service
       5min 60ms network-up.service
    4min 41.841s mga-bg-res.service
      4min 398ms resolvconf.service
    3min 34.416s network.service
    2min 41.348s chronyd.service
    2min 21.896s systemd-tmpfiles-setup-dev.service
      2min 105ms systemd-udev-settle.service
    1min 57.433s dkms-autorebuild.service
    1min 37.832s lm_sensors.service
    1min 36.238s systemd-tmpfiles-setup.service
    1min 30.672s preload.service
    1min 30.170s ModemManager.service
    1min 30.078s sensord.service
    1min 30.023s systemd-journal-flush.service
    1min 28.232s systemd-logind.service
    1min 19.370s systemd-udevd.service
    1min 13.452s dbus.service
         57.273s msec.service
         57.267s partmon.service
         56.429s upower.service
         54.784s plymouth-start.service
         53.221s fedora-readonly.service
         49.618s systemd-fsck-root.service
         42.588s systemd-backlight@backlight:intel_backlight.service
         36.237s accounts-daemon.service
         36.178s mdmonitor.service
         36.168s systemd-user-sessions.service
         35.863s dnf-makecache.service
         32.878s gpm.service
         32.870s acpid.service
         32.620s shorewall6.service
         25.563s cups.service
         25.334s dev-disk-by\x2duuid-f88a7451\x2d3c7c\x2d4fb6\x2da48f\x2de5e713027b7e.swap
         23.285s systemd-sysctl.service
         20.521s systemd-journald.service
         20.327s polkit.service
         16.099s systemd-random-seed.service
         14.473s systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service
         12.740s dev-mqueue.mount
         12.507s dracut-shutdown.service
         11.039s sys-kernel-debug.mount
         11.037s dev-hugepages.mount
          9.666s mdmonitor-takeover.service
          8.300s udisks2.service
          8.238s systemd-tmpfiles-clean.service
          7.825s systemd-udev-trigger.service
          7.362s systemd-remount-fs.service
          6.062s systemd-modules-load.service
          5.023s lvm2-activation-early.service
          4.736s plymouth-quit.service
          4.729s plymouth-quit-wait.service
          4.093s kmod-static-nodes.service
          3.827s systemd-rfkill.service
          3.377s systemd-update-utmp.service
          2.516s lvm2-monitor.service
          1.318s systemd-vconsole-setup.service
           913ms avahi-daemon.service
           577ms lvm2-activation.service
           564ms bluetooth.service
            69ms fedora-loadmodules.service
            58ms user@1000.service
            41ms home.mount
            34ms plymouth-read-write.service
            31ms dmraid-activation.service
            11ms rtkit-daemon.service
            10ms tmp.mount
             9ms user-runtime-dir@1000.service
             6ms systemd-update-utmp-runlevel.service
             3ms sys-fs-fuse-connections.mount


Code: Select all

# 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 @26min 21.347s
└─multi-user.target @26min 21.347s
  └─network.service @22min 46.930s +3min 34.416s
    └─resolvconf.service @18min 46.530s +4min 398ms
      └─basic.target @18min 20.390s
        └─mandriva-everytime.service @6min 29.536s +11min 50.854s
          └─local-fs.target @15min 7.782s
            └─home.mount @12min 48.335s +41ms
              └─systemd-fsck@dev-disk-by\x2duuid-74317e21\x2d9abd\x2d43ce\x2dac8d\x2d0a2943da2a36.service @12min 33.829s +14.473s
                └─local-fs-pre.target @12min 33.828s
                  └─lvm2-monitor.service @12min 31.311s +2.516s
                    └─dm-event.socket @15min 7.793s
                      └─-.mount @3min 1.798s
                        └─system.slice @3min 1.798s
                          └─-.slice @3min 1.798s
# systemd-analyze time
Startup finished in 22.017s (firmware) + 2min 5.479s (loader) + 2min 21.956s (kernel) + 50min 24.383s (userspace) = 55min 13.837s
graphical.target reached after 26min 21.347s in userspace


I've been learning more on systemd to understand what is going on and try to show various configs. If I have missed anythings, please inform me and I'll execute it on my side.

[ainals]

There was a kernel update and I rebooted the laptop. This time my root partition (/dev/sda10) was automatically fsck'ed during boot. The same thing I described above happened (the emergency stop, the keystrokes not apprearing, /root and /home mounted etc). What triggers the emergency stop?
I'm thinking that maybe there is somethings wrong with the shutdown sequence which then messes up the startup
Should I do what is recommended elsewhere : bypass mandriva-everytime to avoid boot time hardware detection?

[doktor5000]

I'm not sure whatyou my to adjust "/dev/sda9 to what it is on my system".

If you boot from a live CD/DVD, then what you currently see as /dev/sda might then be /dev/sdb or /dev/sdc, so you would need to adjust the mkswap command to the actual devicename for your swap partition.
That is currently the UUID f88a7451-3c7c-4fb6-a48f-e5e713027b7e and the device name /dev/sda9.

I checked the configuration for the swap. but couldn't find any refence to dev/sda9 other than the swapon command

Not sure what you want to check there. It's your swap partition, it's listed in your /etc/fstab, that is basically the only reference that is required.

I booted into systemrescuecd and followed the instruction on making the swap partition.
I rebooted and again it went into emergency mode. I entered the root password but it kept scrolling.

You should format your swap partition, not make a new one. And going by the times you posted from systemd-analyze blame it seems you really broke something badly - probably the swap partition.

I'd suggest you to reinstall, and format everything apart from your /home partition.

[ainals]

If you boot from a live CD/DVD, then what you currently see as /dev/sda might then be /dev/sdb or /dev/sdc, so you would need to adjust the mkswap command to the actual devicename for your swap partition.

Ok no worries about that. It is /dev/sda9 on systemrescuecd too. But I do get a warning message about disk partitions not being sequential.

Not sure what you want to check there. It's your swap partition, it's listed in your /etc/fstab, that is basically the only reference that is required.

I've read that systemd has an alternative ways of activating swap. at https://wiki.archlinux.org/index.php/swap it says

Activation by systemd
systemd activates swap partitions based on two different mechanisms. Both are executables in /usr/lib/systemd/system-generators. The generators are run on start-up and create native systemd units for mounts. The first, systemd-fstab-generator, reads the fstab to generate units, including a unit for swap. The second, systemd-gpt-auto-generator inspects the root disk to generate units. It operates on GPT disks only, and can identify swap partitions by their type GUID, see systemd#GPT partition automounting for more information.

and that systemd can activate swap via unit files and it takes precedence over fstab. Ref https://www.freedesktop.org/software/systemd/man/systemd.swap.html. I went to look for unit files for my swap partition UUID and found none. So back to fstab, then.

The system partition automounting informaiton had me take a look at my partition tables

Code: Select all

# parted /dev/sda print
Model: ATA ST500LT012-1DG14 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  1050MB  1049MB  ntfs            Basic data partition          hidden, diag
 2      1050MB  1322MB  273MB   fat32           EFI system partition          boot, hidden, esp
 3      1322MB  2371MB  1049MB  fat32           Basic data partition          hidden
 4      2371MB  2505MB  134MB                   Microsoft reserved partition  msftres
 5      2505MB  75.9GB  73.4GB  ntfs            Basic data partition          msftdata
 8      75.9GB  75.9GB  2097kB                                                bios_grub
11      75.9GB  130GB   54.0GB  ext4
 9      130GB   139GB   8394MB  linux-swap(v1)                                msftdata
10      139GB   459GB   321GB   ext4                                          msftdata
 6      459GB   486GB   26.8GB  ntfs            Basic data partition          msftdata
 7      486GB   500GB   14.2GB  ntfs            Basic data partition          hidden, diag

# gdisk
GPT fdisk (gdisk) version 1.0.4

Type device filename, or press <Enter> to exit: /dev/sda
Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Model: ST500LT012-1DG14
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 9190261E-EDF9-447B-BC9B-3AA7795AC007
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 548845 sectors (268.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2050047   1000.0 MiB  2700  Basic data partition
   2         2050048         2582527   260.0 MiB   EF00  EFI system partition
   3         2582528         4630527   1000.0 MiB  ED01  Basic data partition
   4         4630528         4892671   128.0 MiB   0C01  Microsoft reserved ...
   5         4892672       148252671   68.4 GiB    0700  Basic data partition
   6       896671744       949100543   25.0 GiB    0700  Basic data partition
   7       949100544       976773119   13.2 GiB    2700  Basic data partition
   8       148252672       148256767   2.0 MiB     EF02 
   9       254275584       270669823   7.8 GiB     0700 
  10       270669824       896671743   298.5 GiB   0700 
  11       148256768       253728767   50.3 GiB    8300 


According to https://wiki.archlinux.org/index.php/GPT_fdisk#Partition_typethe code for the swap partition 8200. Here it's 0700.
If this was a work machine, I'd re-install a long time ago. But I'd like to see if there could be a solution.