Page 1 of 1
Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 4:02 am
by Catalin-
Hello MX community!
Code: Select all
System:
Kernel: 5.10.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64
root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-21.1_KDE_x64 Wildflower April 9 2022
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Desktop Mobo: Gigabyte model: B365M H v: x.x
serial: <filter> UEFI: American Megatrends v: F3
date: 09/05/2019
CPU:
Info: 6-Core model: Intel Core i5-9400F bits: 64 type: MCP
arch: Kaby Lake note: check family: 6 model-id: 9E (158)
stepping: A (10) microcode: EC cache: L2: 9 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 34798
Speed: 1819 MHz min/max: 800/4100 MHz Core speeds (MHz):
1: 1819 2: 1742 3: 1933 4: 1947 5: 1448 6: 1838
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache
flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass
disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and
__user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte
driver: nvidia v: 510.47.03 bus-ID: 01:00.0 chip-ID: 10de:1f82
class-ID: 0300
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver:
loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
alternate: nv display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 91
s-size: 535x301mm (21.1x11.9") s-diag: 614mm (24.2")
Monitor-1: DP-0 res: 1920x1080 dpi: 90
size: 544x303mm (21.4x11.9") diag: 623mm (24.5")
OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
v: 4.6.0 NVIDIA 510.47.03 direct render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-14-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel port: d000
bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci
v: 3.0 port: f020 bus-ID: 00:17.0 chip-ID: 8086.2822 rev:
class-ID: 0104
Drives:
Local Storage: total: 1.18 TiB used: 143.88 GiB (11.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston
model: SA400S37240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: B1D2 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-60WN4A1 size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: 1A03 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Kingston
model: DataTraveler 3.0 size: 57.73 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 0000 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported
enclosure?
Partition:
ID-1: / raw-size: 70.11 GiB size: 68.45 GiB (97.64%)
used: 10.18 GiB (14.9%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
ID-2: /home raw-size: 150 GiB size: 146.59 GiB (97.72%)
used: 100.64 GiB (68.7%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17
Swap:
Kernel: swappiness: 15 (default 60)
cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 20 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda4 maj-min: 8:4
Sensors:
System Temperatures: cpu: 27.8 C mobo: 16.8 C gpu: nvidia
temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: note: see --pkg apt: 2506 lib: 1396 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
3: deb-src http://deb.debian.org/debian/ bullseye non-free contrib main
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_11/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirrors.netix.net/mx/MX-Packages/mx/repo/ bullseye main non-free
2: deb https://mirrors.netix.net/mx/MX-Packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
1: deb https://download.onlyoffice.com/repo/debian/ squeeze main
Info:
Processes: 295 Uptime: 48m wakeups: 1 Memory: 15.58 GiB
used: 4.09 GiB (26.3%) Init: SysVinit v: 2.96 runlevel: 5
default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10
Shell: Bash v: 5.1.4
running-in: quick-system-info-mx inxi: 3.3.06
Boot Mode: UEFI
I have an issue with booting Systemd - when it's loading before showing me the login option it stops and then it tell me
cannot open access to console, the root account is locked https://i.imgur.com/YF0zJND.jpg
What I did is to use live mode via chroot to reinstall grub. But that didn't work. I haven't done anything to my system.. I don't know what it's doing it like this but I would like to be able to also use systemd too. At the moment I am using the standard init.
I am still rather new to Linux, so I would appreciate some baby steps. Thanks!
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 6:05 am
by Huckleberry Finn
https://forum.mxlinux.org/viewtopic.php ... 02#p663302
Also (though this may/may not be related) change sata mode to Ahci (from Raid) in Bios settings.
(If you have Windows, too: Before Bios,
open Regedit and make 2 simple changes there to not make Windows unbootable.)
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 7:11 am
by Catalin-
Sata option was set to intel but not it's AHCI and I reinstalled systemd.
I followed these steps but it's still not working, same error. I don't have dual boot, only MX.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 7:21 am
by dolphin_oracle
any custom boot options?
its not a grub error, its well after grub hands off to the system, but it could be a boot option with a format problem.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 7:59 am
by Catalin-
dolphin_oracle wrote: Mon May 30, 2022 7:21 am
any custom boot options?
I haven't modified Grub in /etc/default. I only used Grub Customizer to select mx_logo_ribbon theme and I also added a couple of days ago this
flock -n /tmp/google_drv_sync.lock /usr/bin/rclone copy --transfers 20 --retries 5 "/mnt/HDD/HDD2/Datele mele/Catalin" "GoogleDrive:Backup Linux/Catalin" to Job Scheduler for Rclone sync to my GDrive at an hourly rate.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 10:30 am
by dolphin_oracle
Probably should post your /boot/grub/grub.cfg file.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 10:51 am
by Catalin-
This is my grub info
Code: Select all
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT="1>0"
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR="$(unset PRETTY_NAME; (. /etc/lsb-release; echo ${PRETTY_NAME:?}) 2>/dev/null || echo Debian)"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE="1024x768"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_DISABLE_OS_PROBER="false"
#export GRUB_MENU_PICTURE="/usr/share/backgrounds/MXLinux/grub/linen-gradientblu-grub.png"
#export GRUB_MENU_PICTURE="/usr/share/backgrounds/MX18ALPHAWALL.png"
GRUB_THEME="/boot/grub/themes/mx_logo_ribbon/theme.txt"
and grub.cfg file
Code: Select all
#
# 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 ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
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="1>0"
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
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1024x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
insmod gfxmenu
loadfont ($root)/boot/grub/themes/mx_logo_ribbon/DejaVuSans-Bold14.pf2
loadfont ($root)/boot/grub/themes/mx_logo_ribbon/DejaVuSans10.pf2
loadfont ($root)/boot/grub/themes/mx_logo_ribbon/DejaVuSans12.pf2
loadfont ($root)/boot/grub/themes/mx_logo_ribbon/ascii.pf2
insmod png
set theme=($root)/boot/grub/themes/mx_logo_ribbon/theme.txt
export theme
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=3
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=3
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'MX 21.1 Wildflower' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
echo 'Loading Linux 5.10.0-14-amd64 ...'
linux /boot/vmlinuz-5.10.0-14-amd64 root=UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec ro quiet splash
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-14-amd64
}
submenu 'Advanced options for MX 21.1 Wildflower' $menuentry_id_option 'gnulinux-advanced-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
menuentry 'MX 21.1 Wildflower, with Linux 5.10.0-14-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-14-amd64-advanced-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
echo 'Loading Linux 5.10.0-14-amd64 ...'
linux /boot/vmlinuz-5.10.0-14-amd64 root=UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec ro quiet splash
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-14-amd64
}
menuentry 'MX 21.1 Wildflower, with Linux 5.10.0-14-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-14-amd64-init-systemd-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
echo 'Loading Linux 5.10.0-14-amd64 ...'
linux /boot/vmlinuz-5.10.0-14-amd64 root=UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec ro quiet splash init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-14-amd64
}
menuentry 'MX 21.1 Wildflower, with Linux 5.10.0-13-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-13-amd64-advanced-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
echo 'Loading Linux 5.10.0-13-amd64 ...'
linux /boot/vmlinuz-5.10.0-13-amd64 root=UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec ro quiet splash
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-13-amd64
}
menuentry 'MX 21.1 Wildflower, with Linux 5.10.0-13-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-13-amd64-init-systemd-7b80403e-f1bb-40a2-bfb7-ca024d1884ec' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
echo 'Loading Linux 5.10.0-13-amd64 ...'
linux /boot/vmlinuz-5.10.0-13-amd64 root=UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec ro quiet splash init=/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-13-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
if [ "${grub_platform}" == "efi" ]; then
if [ "${grub_cpu}" == "x86_64" ]; then
true
menuentry "Memory Test (64-bit UEFI)" {
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
else
search --no-floppy --fs-uuid --set=root 7b80403e-f1bb-40a2-bfb7-ca024d1884ec
fi
chainloader /boot/uefi-mt/mtest-64.efi
}
fi
fi
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $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 ###
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 10:52 am
by Huckleberry Finn
Yes, but : /boot/grub/grub.cfg
Edit: Ok now :)
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 11:08 am
by dolphin_oracle
well I don't think its a boot option, nothing is jumping out at me.
you could set up a root account while under sysVinit and then see if that helps anything.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 11:19 am
by dolphin_oracle
its probably worth checking the journal, as the boot message indicates. I think the ACPI messages might be a red-herring.
dumb question, if you remove the job scheduler, (which uses cron) does the the boot improve?
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 12:12 pm
by Catalin-
Done:
1.
2.
dolphin_oracle wrote: Mon May 30, 2022 11:19 am
dumb question, if you remove the job scheduler, (which uses cron) does the the boot improve?
Now I get it like this
https://i.imgur.com/ROwtrpd.jpg
I don't like the ACPI errors neither but a developer from this forum told me this it's something normal..
https://forum.mxlinux.org/viewtopic.php ... 72#p683072
They are not as bad as PCIE flooding errors that I used to have on the laptop which i tried with Huckleberry Finn to make work but.. but this is another story.
Re: Systemd boot - Cannot open access to console, the root account is locked [Solved]
Posted: Mon May 30, 2022 12:34 pm
by dolphin_oracle
my new guess is that something in your fstab has the wrong UUID.
and
may shed some light.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 12:55 pm
by Catalin-
Code: Select all
$ cat /etc/fstab
# Pluggable devices are handled by uDev, they are not in fstab
UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec / ext4 discard,noatime 1 1
UUID=9e4bf024-388d-4bac-b39d-110dda8c3713 /home ext4 noatime 1 2
UUID=d0c4bf5d-b443-4e1e-940b-7b382b067dbf swap swap discard 0 2
UUID=957D-A008 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0
UUID=100b0c34-ade9-4d04-a12c-898db9ca2a3d /mnt/HDD/HDD1 ext4 defaults 0 0
UUID=227b998a-4bf3-4da2-aee1-c1a1ea480b64 /mnt/HDD/HDD2 ext4 defaults 0 0
Code: Select all
$ sudo blkid
/dev/sdb1: LABEL="homeMX" UUID="9e4bf024-388d-4bac-b39d-110dda8c3713" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="897a042f-9dc8-5b4d-af12-1b9c52f9007d"
/dev/sdb2: UUID="100b0c34-ade9-4d04-a12c-898db9ca2a3d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="22dceee0-f34f-f64c-99c9-499fde1ce521"
/dev/sdb3: UUID="227b998a-4bf3-4da2-aee1-c1a1ea480b64" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3e9b8b18-6e80-4842-bc65-da029a0f4db6"
/dev/sdb4: UUID="a2702f41-04c1-452b-9818-568de968e0a7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8221f8fe-535a-9b4f-9e44-0ff20b4676e1"
/dev/sda1: LABEL_FATBOOT="BOOT_EFI" LABEL="BOOT_EFI" UUID="B22B-87AE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f419b698-17ac-0c40-932f-4641be02c85f"
/dev/sda2: LABEL="rootMX21" UUID="7b80403e-f1bb-40a2-bfb7-ca024d1884ec" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="98c7ef40-48b2-8e4a-810a-9f952939f7a0"
/dev/sda4: LABEL="swapMX" UUID="d0c4bf5d-b443-4e1e-940b-7b382b067dbf" TYPE="swap" PARTUUID="45008913-fe0d-7941-9902-d785e80665d9"
So.. I have to replace UUID=957D-A008 with UUID="B22B-87AE" right?
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 1:27 pm
by Huckleberry Finn
Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 2:14 pm
by Catalin-
Huckleberry Finn wrote: Mon May 30, 2022 1:27 pm
Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?
Because (SysV)init is superior
You guys are the Linux experts here, I've been only using Linux for like 4-5 months now but usually from what I've read on the internet, with systemd, if one thing goes wrong then the whole system goes down, pretty much like a domino game.
Now I've also heard for example that Clear Linux can mount your drives even without having an fstab directory? Like okay that's crazy.
I thought to use systemd as it might make it easier with making software run automatically in the background. Also lately I've seen Timeshift acting weird like making snapshots at odd hours, missing a day sometimes or not making as many as I want to.
Edit- I have to go now but I will come back with a reply after this!
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 2:34 pm
by dolphin_oracle
Huckleberry Finn wrote: Mon May 30, 2022 1:27 pm
Good catch . Just, the question is: Why doesn't it cause any issues with the default (SysV)init ?
because sysVInit doesn't do any mounting, unlike systemd.
Code: Select all
# Pluggable devices are handled by uDev, they are not in fstab
UUID=7b80403e-f1bb-40a2-bfb7-ca024d1884ec / ext4 discard,noatime 1 1
UUID=9e4bf024-388d-4bac-b39d-110dda8c3713 /home ext4 noatime 1 2
UUID=d0c4bf5d-b443-4e1e-940b-7b382b067dbf swap swap discard 0 2
UUID=957D-A008 /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0
UUID=100b0c34-ade9-4d04-a12c-898db9ca2a3d /mnt/HDD/HDD1 ext4 defaults 0 0
UUID=227b998a-4bf3-4da2-aee1-c1a1ea480b64 /mnt/HDD/HDD2 ext4 defaults 0 0
OK, I think that UUID=957D-A008 should be UUID=B22B-87AE for the efi partition. Just edit your fstab and you should be good.
fun part is that even though systemd tries to mount it, and times out, its not actually harmful to not mount an efi partition. its a convenience thing.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 4:14 pm
by Catalin-
Thanks guys. This was the issue,
now it works!
About the other topic https://forum.mxlinux.org/viewtopic.php ... 28#p684628
Regarding this issue I will have come back as I tried to make my laptop run again on Manjaro but it started freezing. At the moment it's running and "accepting" Garuda Xfce.
God knows why and I tried like all distros out there (Ubuntu and its flavours, Linux Mint, Fedora, Modicia, Linux Lite, Clear Linux, Ultramarine, Zorin, Debian OG, Pop_OS! etc) and they all have some issue. Mostly all distros freeze during the installation, I suspect some PCIE continous error happening in the background.. not sure how a Linux installation could be started in a way that it's not freezing by hardware incompatibility. And one that doesn't eat free space afterwards.
I can't keep it on Garuda as my family members don't know how to use it. The same issue that I had on MX with it running out of space also happened on PC Linux distro. But i'll get back on that thread.
Re: Systemd boot - Cannot open access to console, the root account is locked
Posted: Mon May 30, 2022 6:21 pm
by Huckleberry Finn
Posted there about that issue.
