You are not logged in.

#1 2018-07-13 00:19:53

avi9526
Member
Registered: 2015-05-15
Posts: 77

random emergency mode

Few days getting random emergency mode:

    Welcome to emergency mode! …

    Cannot open access to console, the root account is locked.
    See sulogin(8) man page for more details.

    Press Enter to continue.

pressing Enter does work and system start properly.

I have seem to find corelation, this happens only if message shown:


… systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/4b8769c0-e042-4465-9683-7437dfbfa809.
… systemd[1]: Dependency failed for /media/hdd1.
… systemd[1]: Dependency failed for Local File Systems.
… systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
… systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
… systemd[1]: media-hdd1.mount: Job media-hdd1.mount/start failed with result 'dependency'.
… systemd[1]: systemd-fsck@dev-disk-by\x2duuid-4b8769c0\x2de042\x2d4465\x2d9683\x2d7437dfbfa809.service: Job systemd-fsck@dev-disk-by\x2duuid-4b8769c0\x2de042\x2d4465\x2d9683\x2d7437dfbfa809.service/start failed with result 'dependency'.

Starting manually

sudo systemctl start systemd-fsck@dev-disk-by\x2duuid-4b8769c0\x2de042\x2d4465\x2d9683\x2d7437dfbfa809.service

A dependency job for systemd-fsck@dev-disk-byx2duuid-4b8769c0x2de042x2d4465x2d9683x2d7437dfbfa809.service failed. See 'journalctl -xe' for details.

but

ls -la /dev/disk/by-uuid/4b8769c0-e042-4465-9683-7437dfbfa809 
lrwxrwxrwx 1 root root 10 лип 13 02:55 /dev/disk/by-uuid/4b8769c0-e042-4465-9683-7437dfbfa809 -> ../../sdb1

sudo systemctl start systemd-fsck@dev-sdb1.service

works fine. What is going on?

systemctl show systemd-fsck@dev-disk-by\x2duuid-4b8769c0\x2de042\x2d4465\x2d9683\x2d7437dfbfa80.service| grep -i exec
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=0
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/lib/systemd/systemd-fsck ; argv[]=/usr/lib/systemd/systemd-fsck /dev/disk/byx2duuid/4b8769c0x2de042x2d4465x2d9683x2d7437dfbfa80 ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
MemoryDenyWriteExecute=no

notice badly escaped "/dev/disk/byx2duuid/4b8769c0x2de042x2d4465x2d9683x2d7437dfbfa80", not sure it is reason, maybe running it in bash cause escape to stop working

My configs just in case I miss something

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/vg2-root rw quiet resume=/dev/vg2/root resume_offset=106496
uname -a
Linux ***** 4.17.5-1-ARCH #1 SMP PREEMPT Sun Jul 8 17:27:31 UTC 2018 x86_64 GNU/Linux

/etc/mkinitcpio.conf

# 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 plymouth systemd autodetect modconf block sd-lvm2 filesystems fsck"
HOOKS="base udev systemd autodetect modconf block sd-lvm2 filesystems fsck"

# 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=cat

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Offline

#2 2018-07-13 00:22:07

circleface
Member
Registered: 2012-05-26
Posts: 528

Re: random emergency mode

See https://bbs.archlinux.org/viewtopic.php?id=238554 for the same issue (despite the title of that thread, I am pretty sure you are experiencing the same thing, I am too).  It seems a lot of people are experiencing this right now.

Last edited by circleface (2018-07-13 00:23:53)

Offline

Board footer

Powered by FluxBB