Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Boot fails with "mount-fstab: fatal: crash!" (Read 1049 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Boot fails with "mount-fstab: fatal: crash!"

This is a service which belongs to boot@system in the boot tree. I have tried regenerating the fstab with fstabgen, and it looks right. Not sure where the problem is here, but cannot boot. I installed a DKMS module vendor-reset-dkms-git which may have caused some issues. I have since tried to remove it, mostly successfully.
I also couldn't find a relevant log file under /var/log or /run/66.

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #1
Paste your fstab file and /run/66/log/0/current

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #2
Code: [Select]
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=8A45-2551                            /boot/efi      vfat    umask=0077 0 2
UUID=4e65bf78-a9bd-412f-a294-ee31746ff7c2 /              ext4    defaults,noatime 0 1
# /dev/nvme0n1p2
UUID=4e65bf78-a9bd-412f-a294-ee31746ff7c2 /         ext4      rw,relatime 0 1

# /dev/nvme0n1p1
UUID=8A45-2551      /boot/efi vfat      rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

# /dev/nvme0n1p3
UUID=b6cb3da5-f748-4296-9eb5-642a66bf64e2 none      swap      defaults  0 0

There is no
Code: [Select]
/run/66/log/0/current
Code: [Select]
grep -r "mount-fstab" /run/66/log/*
no output

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #3
You have / and /boot/efi in fstab twice, which is what is causing the issue
I am assuming you did fstabgen -U / >> /etc/fstab instead of a single '>'

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #4
Code: [Select]
# /dev/nvme0n1p2
/dev/nvme0n1p2      /         ext4      rw,relatime 0 1

# /dev/nvme0n1p1
/dev/nvme0n1p1      /boot/efi vfat      rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

# /etc/resolv.conf/etc/resolv.conf
/etc/resolv.conf/etc/resolv.conf /etc/resolv.conf none      rw,lowerdir=/run/artix/sfs/livefs:/run/artix/sfs/rootfs,upperdir=/run/artix/overlay_root/upper,workdir=/run/artix/overlay_root/work,index=off,xino=off,bind 0 0

# /dev/nvme0n1p3
/dev/nvme0n1p3      none      swap      defaults  0 0

I must have done that after trying to fix it. It also crashes with single entries. But it happened sometime after I installed vendor-reset-dkms-git. Here is logs from reinstalling kernel:

Code: [Select]
# pacman -S linux-zen
warning: linux-zen-5.13.13.zen1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-zen-5.13.13.zen1-1

Total Installed Size:  133.99 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> Unable to remove module vendor-reset/0.1.1 for kernel 5.13.13-zen1-1-zen: Not found in dkms status output.
:: Processing package changes...
(1/1) reinstalling linux-zen                       [######################] 100%
:: Running post-transaction hooks...
(1/3) Updating module dependencies...
(2/3) Install DKMS modules
==> dkms install --no-depmod -m vendor-reset -v 0.1.1 -k 5.13.13-zen1-1-zen
Error! Bad return status for module build on kernel: 5.13.13-zen1-1-zen (x86_64)
Consult /var/lib/dkms/vendor-reset/0.1.1/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m vendor-reset -v 0.1.1 -k 5.13.13-zen1-1-zen' returned 10
==> depmod 5.13.13-zen1-1-zen
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 5.13.13-zen1-1-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [modconf]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 5.13.13-zen1-1-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [modconf]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful

Code: [Select]
# cat /var/lib/dkms/vendor-reset/0.1.1/build/make.log 
DKMS make.log for vendor-reset-0.1.1 for kernel 5.13.13-zen1-1-zen (x86_64)
Mon Aug 30 14:20:33 GMT 2021
make -C /usr/lib/modules/5.13.13-zen1-1-zen/build M=/var/lib/dkms/vendor-reset/0.1.1/build modules
make[1]: Entering directory '/usr/lib/modules/5.13.13-zen1-1-zen/build'
scripts/Kbuild.include:1: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:2: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:3: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:4: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:5: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:6: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:7: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:8: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:9: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:10: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:11: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:12: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:13: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:14: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:15: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:16: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:17: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:18: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:19: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:20: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:21: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:22: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:23: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:24: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:25: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:26: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:27: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:28: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:29: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:30: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:31: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:32: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:33: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:34: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:35: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:36: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:37: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:38: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:39: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:40: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:41: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:42: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:43: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:44: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:45: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:46: warning: NUL character seen; rest of line ignored
scripts/Kbuild.include:47: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:1: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:2: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:3: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:4: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:5: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:6: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:7: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:8: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:9: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:10: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:11: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:12: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:13: warning: NUL character seen; rest of line ignored
scripts/Makefile.compiler:14: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:1: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:2: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:3: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:4: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:5: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:6: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:7: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:8: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:9: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:10: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:11: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:12: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:13: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:14: warning: NUL character seen; rest of line ignored
scripts/Makefile.extrawarn:15: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:1: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:2: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:3: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:4: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:5: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:6: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:7: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:8: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:9: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:10: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:11: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:12: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:13: warning: NUL character seen; rest of line ignored
scripts/Makefile.gcc-plugins:14: warning: NUL character seen; rest of line ignored
make: Entering an unknown directory
make: *** empty variable name.  Stop.
make: Leaving an unknown directory
make[1]: *** [Makefile:1862: /var/lib/dkms/vendor-reset/0.1.1/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.13.13-zen1-1-zen/build'
make: *** [Makefile:8: build] Error 2

Tried removing relevant files and packages but unsuccessful so far.

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #5
Did you try rm -rf /var/lib/dkms/vendor-reset
then mkinitcpio -p linux-zen

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #6
Had to remove entire dkms package. Ran basestrap base base-devel linux-zen, downgraded from 5.13.13 to 5.13.12, still occurs :/. Disabled/enabled boot and default tree, is perhaps possible to recreate them? Since the error states mount-fstab.

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #7
Had to remove entire dkms package. Ran basestrap base base-devel linux-zen, downgraded from 5.13.13 to 5.13.12, still occurs :/. Disabled/enabled boot and default tree, is perhaps possible to recreate them? Since the error states mount-fstab.
You can recreate boot tree with:
Code: [Select]
66-enable -t boot -F boot@system

Though I don't expect it to help. It should only fail if there is something wrong with your fstab file.

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #8
Managed to fix it by using UUID instead of device path in fstab. Now I got to the desktop on 5.13.12-zen, so I tried upgrading to 5.13.13 and there I only get a shell. The last error is nevertheless present on both kernels:

Code: [Select]
2021-08-30 18:19:03.953281078  [Initiate db of tree boot...]
2021-08-30 18:19:03.970170745  [Start db services of tree boot...]
2021-08-30 18:19:04.014421759  mount-tmp: info: starts...
2021-08-30 18:19:04.014832108  mount-run: info: starts...
2021-08-30 18:19:04.016059409  mount-proc: info: starts...
2021-08-30 18:19:04.018906750  system-hostname: info: starts...
2021-08-30 18:19:04.032385745  populate-run: info: starts...
2021-08-30 18:19:04.034587305  mount-sys: info: starts...
2021-08-30 18:19:04.035190123  populate-tmp: info: starts...
2021-08-30 18:19:04.043776475  populate-sys: info: starts...
2021-08-30 18:19:04.044852587  mount-dev: info: starts...
2021-08-30 18:19:04.067438029  mount-pts: info: starts...
2021-08-30 18:19:04.067877077  populate-dev: info: starts...
2021-08-30 18:19:04.069039818  mount-shm: info: starts...
2021-08-30 18:19:04.070185551  mount-cgroups: info: starts...
2021-08-30 18:19:04.111647795  system-random: info: starts...
2021-08-30 18:19:04.114192316  system-sysctl: info: starts...
2021-08-30 18:19:04.115330443  system-hwclock: info: starts...
2021-08-30 18:19:04.115489832  modules-kernel: info: starts...
2021-08-30 18:19:04.120295992  modules-system: info: starts...
2021-08-30 18:19:04.121858193  * Applying /usr/lib/sysctl.d/10-artix.conf ...
2021-08-30 18:19:04.121861270  fs.inotify.max_user_instances = 1024
2021-08-30 18:19:04.121862882  fs.inotify.max_user_watches = 524288
2021-08-30 18:19:04.121864622  * Applying /usr/lib/sysctl.d/60-libvirtd.conf ...
2021-08-30 18:19:04.121866075  fs.aio-max-nr = 1048576
2021-08-30 18:19:04.121867751  * Applying /etc/sysctl.d/99_magic_sysrq.conf ...
2021-08-30 18:19:04.121869405  kernel.sysrq = 1
2021-08-30 18:19:04.121870622  * Applying /etc/sysctl.conf ...
2021-08-30 18:19:04.121872053  net.ipv4.ip_forward = 1
2021-08-30 18:19:05.236108691  udevadm: info: starts...
2021-08-30 18:19:07.204856476  system-fontnkey: info: starts...
2021-08-30 18:19:07.233786205  system-fsck: info: starts...
2021-08-30 18:19:07.250635153  system-fsck: info: /dev/nvme0n1p2 is mounted.
2021-08-30 18:19:07.250657591  e2fsck: Cannot continue, aborting.
2021-08-30 18:19:07.250659546 
2021-08-30 18:19:07.250660572 
2021-08-30 18:19:07.258185961  mount-fstab: info: starts...
2021-08-30 18:19:07.274008587  mount-rw: info: starts...
2021-08-30 18:19:07.291992033  mount-netfs: info: starts...
2021-08-30 18:19:07.300201524  local-tmpfiles: info: starts...
2021-08-30 18:19:07.300790646  local-time: info: starts...
2021-08-30 18:19:07.301361838  local-loop: info: starts...
2021-08-30 18:19:07.306712545  local-locale: info: starts...
2021-08-30 18:19:07.307475389  local-sethostname: info: starts...
2021-08-30 18:19:07.309146972  local-sysusers: info: starts...
2021-08-30 18:19:07.320082618  local-authfiles: info: starts...
2021-08-30 18:19:07.339599320  local-dmesg: info: starts...
2021-08-30 18:19:07.348765037  all-Runtime: info: starts...
2021-08-30 18:19:07.394281257  66-all: fatal: unable to start classic services list
2021-08-30 18:19:07.395403784  all-Runtime: fatal: crashed! -- Your machine is operational but some runtime service failed to start correctly. Please see the complete boot log at /run/66/log/0/current for further information.

I ran a fsck while on rescue USB on bootloader and it modified 5 files, after I told it to restore from backup. Funnily enough e2fsck tries to run on bootup now. "Please see the complete boot log at /run/66/log/0/current for further information." this log file is that one.

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #9
What is your output of 66-intree

Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #10
Code: [Select]
66-intree
Name         : default
Initialized  : no
Enabled      : yes
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : acpid-log acpid qemu-guest-agent-log qemu-guest-agent
               cronie-log cronie dnsmasq-log dnsmasq dbus-log dbus
               NetworkManager-log NetworkManager virtlockd-socket
               virtlockd-log virtlockd virtlogd-log virtlogd cupsd-log
               cupsd bluetoothd-log bluetoothd libvirtd-log libvirtd
               elogind-log elogind sddm-log sddm syslog-ng-log syslog-ng

Name         : boot
Initialized  : no
Enabled      : yes
Starts after : default
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : tty-earlier@tty12 system-hostname mount-run populate-run
               mount-tmp populate-tmp mount-proc mount-sys populate-sys
               mount-dev mount-pts mount-shm populate-dev mount-cgroups 00
               all-Mount modules-kernel udevd-log udevd udevadm
               system-fontnkey system-fsck mount-fstab system-hwclock
               system-random modules-system system-sysctl all-System
               mount-rw mount-netfs local-loop local-sethostname local-time
               local-authfiles local-tmpfiles local-sysusers local-dmesg
               local-locale all-Local all-Runtime All tty-rc@tty2
               tty-rc@tty5 tty-rc@tty3 tty-rc@tty4 tty-rc@tty1 boot@system


Re: Boot fails with "mount-fstab: fatal: crash!"

Reply #11
Fixed, disabled following GRUB options:

#CONFIG_FTRACE=y
#CONFIG_KPROBES=y
#CONFIG_PCI_QUIRKS=y
#CONFIG_KALLSYMS=y
#CONFIG_KALLSYMS_ALL=y
#CONFIG_FUNCTION_TRACER=y