Stuck at loading initial ramdisk with nfs share error sometimes

Hello.
From de last 2 kernel, I notice some issue to boot into system.
I get stuck into «Loading initial ramdisk» like this topic [Solved] Stuck at loading initial ramdisk

So I did a ctrl + alt + suppr to force reboot and try again after 5/6 times I can boot
I'm a bit confused but when I try to debug my issue
I saw in the boot log

sudo cat /var/log/boot.log
[FAILED] Failed to mount /home/user/Syno/Syno_Music.
[DEPEND] Dependency failed for Remote File Systems.
[FAILED] Failed to mount /home/user/Syno/Syno_Partage.
[FAILED] Failed to mount /home/user/Syno/Syno_Photo.
[FAILED] Failed to mount /home/user/Syno/Syno_Syn.
[FAILED] Failed to mount /home/user/Syno/Syno_Video.
------------ Sun Dec 04 11:58:59 CET 2022 ------------
setfont: KDFONTOP: Function not implemented
[FAILED] Failed to mount /home/user/Syno/Syno_Music.
[DEPEND] Dependency failed for Remote File Systems.
[FAILED] Failed to mount /home/user/Syno/Syno_Photo.
[FAILED] Failed to mount /home/user/Syno/Syno_Partage.
[FAILED] Failed to mount /home/user/Syno/Syno_Syn.
[FAILED] Failed to mount /home/user/Syno/Syno_Video.
------------ Sun Dec 04 12:20:51 CET 2022 ------------
setfont: KDFONTOP: Function not implemented

I've got nfs share and when it's failed to mount it get stuck
I was stuck at Sun Dec 04 11:58:59 CET 2022 and finally boot at Sun Dec 04 12:20:51 CET 2022
We see no error when I can boot rellated to nfs share
I don't think error «setfont: KDFONTOP: Function not implemented» is important here
So I only one to have this issue ?
May be is related to my unit file systemd ?
I already add network-online.target to wait to have network to mount it

sudo systemctl cat home-user-Syno-Syno_Music.mount   
# /run/systemd/generator/home-user-Syno-Syno_Music.mount
# Automatically generated by systemd-fstab-generator

[Unit]
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
SourcePath=/etc/fstab
Before=remote-fs.target

[Mount]
What=192.168.1.99:/volume1/music
Where=/home/user/Syno/Syno_Music
Type=nfs
Options=_netdev,auto,rw

# /etc/systemd/system/home-user-Syno-Syno_Music.mount.d/override.conf
[Unit]
After=syslog.target network-online.target

My system is up to date so I only see this but sometimes the nfs share is well mounted sometimes not and I get stuck :disappointed_relieved:
If some have any idea.

System:
  Kernel: 5.15.81-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: Xfce v: 4.16.1 tk: Gtk v: 3.24.34 info: xfce4-panel, plank
    wm: xfwm v: 4.16.1 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME H510M-A v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1017
    date: 07/12/2021
CPU:
  Info: model: Intel Core i5-10400F bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA5 (165) stepping: 3 microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 800 high: 801 min/max: 800/4300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
    5: 801 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 69597
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  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: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
    v: 525.60.11 alternate: nouveau,nvidia_drm non-free: 520.xx+
    status: current (as of 2022-10) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:2507 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 compositor: xfwm v: 4.16.1
    driver: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.60.11 renderer: NVIDIA GeForce RTX
    3050/PCIe/SSE2 direct render: Yes
Audio:
  Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:228e class-ID: 0403
  Sound API: ALSA v: k5.15.81-1-lts running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.61 running: yes
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: ASUSTek type: USB driver: btusb v: 0.8 bus-ID: 1-14:6
    chip-ID: 0b05:190e class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 2.37 TiB used: 1.04 TiB (43.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SanDisk model: ADATA SX6000NP
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s
    lanes: 2 type: SSD serial: <filter> rev: V6005-af temp: 49.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT480BX500SSD1
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 054 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM008-2FR102
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: MBR
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 92.1 GiB (77.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 592 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 92.1 GiB (77.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 92.1 GiB (77.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 92.1 GiB (77.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.48 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 46%
Info:
  Processes: 352 Uptime: 12m wakeups: 0 Memory: 15.48 GiB
  used: 2.62 GiB (16.9%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1687
  libs: 534 tools: paru Shell: Zsh v: 5.9 running-in: xfce4-terminal
  inxi: 3.3.23
Garuda (2.6.10-1):
  System install date:     2022-03-18
  Last full system update: 2022-12-04 ↻
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:   

Have a nice day

Change it to
Options=_netdev,auto,rw,nofail
Even if mount fails, boot shouldn't get stuck anymore, assuming there aren't any other problems,

1 Like

I checked dmesg log and I compare it to the boot log at Sun Dec 04 12:20:51 CET 2022

[dim.  4 déc. 12:20:50 2022] usbcore: registered new interface driver usbhid
[dim.  4 déc. 12:20:50 2022] usbhid: USB HID core driver
[dim.  4 déc. 12:20:51 2022] asus_wmi: ASUS WMI generic driver loaded
[dim.  4 déc. 12:20:51 2022] asus_wmi: Initialization: 0x0
[dim.  4 déc. 12:20:51 2022] asus_wmi: BIOS WMI version: 0.0
[dim.  4 déc. 12:20:51 2022] asus_wmi: SFUN value: 0x0
[dim.  4 déc. 12:20:51 2022] eeepc-wmi eeepc-wmi: Detected AsusMbSwInterface, not ASUSWMI, use DSTS
[dim.  4 déc. 12:20:51 2022] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input22
[dim.  4 déc. 12:20:51 2022] iTCO_vendor_support: vendor-support=0
[dim.  4 déc. 12:20:51 2022] ee1004 1-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[dim.  4 déc. 12:20:51 2022] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=6, TCOBASE=0x0400)
[dim.  4 déc. 12:20:51 2022] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[dim.  4 déc. 12:20:51 2022] BTRFS info (device sda1): using free space tree
[dim.  4 déc. 12:20:51 2022] BTRFS info (device sda1): has skinny extents
[dim.  4 déc. 12:20:51 2022] BTRFS info (device sda1): enabling ssd optimizations
[dim.  4 déc. 12:20:51 2022] Bluetooth: Core ver 2.22
[dim.  4 déc. 12:20:51 2022] NET: Registered PF_BLUETOOTH protocol family
[dim.  4 déc. 12:20:51 2022] Bluetooth: HCI device and connection manager initialized
[dim.  4 déc. 12:20:51 2022] Bluetooth: HCI socket layer initialized
[dim.  4 déc. 12:20:51 2022] Bluetooth: L2CAP socket layer initialized
[dim.  4 déc. 12:20:51 2022] Bluetooth: SCO socket layer initialized
[dim.  4 déc. 12:20:51 2022] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[dim.  4 déc. 12:20:51 2022] mousedev: PS/2 mouse device common for all mice
[dim.  4 déc. 12:20:51 2022] usbcore: registered new interface driver btusb
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[dim.  4 déc. 12:20:51 2022] NET: Registered PF_QIPCRTR protocol family
[dim.  4 déc. 12:20:51 2022] Bluetooth: hci0: RTL: fw version 0x09a98a6b
[dim.  4 déc. 12:20:51 2022] e1000e 0000:00:1f.6 eno1: renamed from eth0
[dim.  4 déc. 12:20:51 2022] intel_rapl_common: Found RAPL domain package
[dim.  4 déc. 12:20:51 2022] intel_rapl_common: Found RAPL domain core
[dim.  4 déc. 12:20:51 2022] intel_rapl_common: Found RAPL domain dram
[dim.  4 déc. 12:20:51 2022] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[dim.  4 déc. 12:20:51 2022] Bluetooth: BNEP filters: protocol multicast
[dim.  4 déc. 12:20:51 2022] Bluetooth: BNEP socket layer initialized
[dim.  4 déc. 12:20:51 2022] NET: Registered PF_ALG protocol family
[dim.  4 déc. 12:20:52 2022] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[dim.  4 déc. 12:20:52 2022] Bluetooth: HIDP socket layer initialized
[dim.  4 déc. 12:20:54 2022] e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[dim.  4 déc. 12:20:54 2022] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[dim.  4 déc. 12:20:54 2022] kauditd_printk_skb: 48 callbacks suppressed
[dim.  4 déc. 12:20:54 2022] audit: type=1130 audit(1670152855.017:59): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[dim.  4 déc. 12:20:55 2022] FS-Cache: Loaded
[dim.  4 déc. 12:20:55 2022] RPC: Registered named UNIX socket transport module.
[dim.  4 déc. 12:20:55 2022] RPC: Registered udp transport module.
[dim.  4 déc. 12:20:55 2022] RPC: Registered tcp transport module.
[dim.  4 déc. 12:20:55 2022] RPC: Registered tcp NFSv4.1 backchannel transport module.
[dim.  4 déc. 12:20:55 2022] FS-Cache: Netfs 'nfs' registered for caching
[dim.  4 déc. 12:20:55 2022] Key type dns_resolver registered
[dim.  4 déc. 12:20:55 2022] NFS: Registering the id_resolver key type
[dim.  4 déc. 12:20:55 2022] Key type id_resolver registered
[dim.  4 déc. 12:20:55 2022] Key type id_legacy registered

Checked other topic on internet to to see the unit file parameter

No change
I did the change and reboot
Still stuck if i boot, I'll disable automount and try to get more verbosity in boot screen to find what s really goin one

Maybe, is adding graphical.target to the After= an option and does it make a difference?
The "random" fail hints at a possible timing problem, so perhaps mounting as late as possible could solve it. Just guessing but worth a shot.

Is NetworkManager-wait-online.service enabled?

Can you post your /etc/fstab?

This is almost certainly unrelated, but you can resolve this by adding " setfont" to the BINARIES section of /etc/mkinitcpio.conf:

BINARIES=(setfont)

Then rebuild it.

sudo mkinitcpio -P
1 Like

This may sound totally unrelated, but the kernel in use can sometimes be an issue with NFS. I have sometimes had to switch to the LTS or others to solve boot issues when using NFS.

1 Like

Thanks you all for your reply
TLDR ; I give a try no change ....

I decide to boot into chroot because I don't achieve to boot into system from yesterday

I make the change in /etc/mkinitcpio.conf and it's good


sh-5.1# sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.15.81-1-lts
  -> 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: [consolefont]
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.15.81-1-lts
  -> 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: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> 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: [consolefont]
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful

My fstab

sh-5.1# cat /etc/fstab 
# /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=36C8-F8BD                            /boot/efi      vfat    umask=0077 0 2
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /              btrfs   subvol=/@,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /home          btrfs   subvol=/@home,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /root          btrfs   subvol=/@root,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /srv           btrfs   subvol=/@srv,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/cache     btrfs   subvol=/@cache,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/log       btrfs   subvol=/@log,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

#Partiton Jeux
/dev/disk/by-uuid/a250d308-71c1-4213-a5d4-56168dacc2c0 /home/user/Jeux btrfs defaults
/dev/disk/by-uuid/8b74e58c-839a-4674-9b50-09a63ae48278 /home/user/Seagate ext4 defaults

#NFS
192.168.1.99:/volume1/music /home/user/Syno/Syno_Music nfs _netdev,auto,rw 0 0
192.168.1.99:/volume1/Syn /home/user/Syno/Syno_Syn nfs _netdev,auto,rw 0 0
192.168.1.99:/volume1/video /home/user/Syno/Syno_Video nfs _netdev,auto,rw 0 0
192.168.1.99:/volume1/photo /home/user/Syno/Syno_Photo nfs _netdev,auto,rw 0 0
192.168.1.99:/volume1/Partage /home/user/Syno/Syno_Partage nfs _netdev,auto,rw 0 0

So i give a try to disable *.mount service of my nfs share and i comment the NFS section in fstab
About Network_wait-online
I don't see this in chroot (but it seems normal)
when I try list-ynit I've got

multi-user.target                          static   -       
network-online.target                      static   -       
network-pre.target                         static   -       
network.target                             static   -       
nfs-client.target                          disabled disabled

Try to reboot
No luck ! Still stuck

And into /var/log/boot.log I only have error about nfs share like in my previous post
I'll try to chroot again and check the log and I'll try to have verbosity. I don't search how to do this now.

Try adding the nofail option mrvictory suggested to these fstab entries.

I try and still stuck, I'm not suprise now because I try to disable the nfs part in fstab / disable *.mount service
So the issue is not related to my nfs share
I remove quiet quiet splash from /etc/grub.d/grub.cfg and regenerate grub
https://wiki.archlinux.org/title/kernel_parameters#GRUB
And reboot
I see it's blocked at the beginning

loading linux-lts 
loading initial ramdisk 
/new black screen/
: running early hook [udev]
: running early hook [plymouth]

If nobody have idea I can give a try to restore previous snapshot but not a fix ...

So i try something. I boot into Garuda like normally into grub I modify the arguments provide and remove splash and make F10 to boot into system and voila (cf previous link about GRUB into wiki archlinux)
I need to investigate more about this

EDIT :

------------ Mon Dec 05 15:34:15 CET 2022 ------------
[FAILED] Failed to mount /home/anael/Syno/Syno_Music.
[DEPEND] Dependency failed for Remote File Systems.
[FAILED] Failed to mount /home/anael/Syno/Syno_Partage.
[FAILED] Failed to mount /home/anael/Syno/Syno_Photo.
[FAILED] Failed to mount /home/anael/Syno/Syno_Syn.
[FAILED] Failed to mount /home/anael/Syno/Syno_Video.
------------ Mon Dec 05 15:42:56 CET 2022 ------------
[ SKIP ] Ordering cycle found, skipping Permit User Sessions
[ SKIP ] Ordering cycle found, skipping Virtualization daemon

I add to override.conf in system unit with

[Unit]
After=syslog.target remote-fs.target network-online.target graphical.target

[Mount]
Options=_netdev,auto,rw,nofail

Tryin to reboot . NOK

I disable / mask nfs systemd unit file and comment nfs section in fstab and reboot with grub editing : OK (I dont thing grub modification helped)

------------ Mon Dec 05 17:30:49 CET 2022 ------------
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: running hook [consolefont]
:: Loading console font...done.
:: running hook [plymouth]
:: mounting '/dev/nvme0n1p2' on real root
:: running late hook [plymouth]
:: running late hook [grub-btrfs-overlayfs]
:: running cleanup hook [udev]

Welcome to Garuda Linux!

[  OK  ] Created slice Virtual Machine and Container Slice.
[  OK  ] Created slice Slice /system/getty.
[  OK  ] Created slice Slice /system/modprobe.
[  OK  ] Created slice Slice /system/systemd-fsck.
[  OK  ] Created slice Slice /system/systemd-zram-setup.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Set up automount Arbitrary Executable File Formats File System Automount Point.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Local Integrity Protected Volumes.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slice Units.
[  OK  ] Reached target Local Verity Protected Volumes.
[  OK  ] Listening on Device-mapper event daemon FIFOs.
[  OK  ] Listening on LVM2 poll daemon socket.
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on Userspace Out-Of-Memory (OOM) Killer Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Mounting Kernel Trace File System...
         Starting Create List of Static Device Nodes...
         Starting Monitoring of LVM2 mirrors, …tc. using dmeventd or progress polling...
         Starting Load Kernel Module configfs...
         Starting Load Kernel Module drm...
         Starting Load Kernel Module fuse...
         Starting Journal Service...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting Coldplug All udev Devices...
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Trace File System.
[  OK  ] Finished Create List of Static Device Nodes.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
         Mounting Kernel Configuration File System...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Load Kernel Module fuse.
         Mounting FUSE Control File System...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Journal Service.
[  OK  ] Finished Load Kernel Modules.
         Starting Apply Kernel Variables...
[  OK  ] Finished Coldplug All udev Devices.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Monitoring of LVM2 mirrors, … etc. using dmeventd or progress polling.
[  OK  ] Finished Remount Root and Kernel File Systems.
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
         Starting Setup Virtual Console...
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Preparation for Local File Systems.
         Starting Rule-based Manager for Device Events and Files...
[  OK  ] Finished Setup Virtual Console.
[  OK  ] Started Rule-based Manager for Device Events and Files.
         Starting Show Plymouth Boot Screen...
[  OK  ] Found device /dev/zram0.
[  OK  ] Created slice Slice /system/udisks2-zram-setup.
         Starting Create swap on /dev/zram0...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Finished Create swap on /dev/zram0.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
         Activating swap Compressed Swap on /dev/zram0...
[  OK  ] Found device ADATA SX6000NP root.
[  OK  ] Found device ADATA SX6000NP NO_LABEL.
         Starting File System Check on /dev/disk/by-uuid/36C8-F8BD...
[  OK  ] Found device CT480BX500SSD1 Jeux.
[  OK  ] Found device ST2000DM008-2FR102 1.
[  OK  ] Finished File System Check on /dev/disk/by-uuid/36C8-F8BD.
[  OK  ] Activated swap Compressed Swap on /dev/zram0.
[  OK  ] Reached target Swaps.
         Mounting /boot/efi...
         Mounting /home...
         Mounting /root...
         Mounting /srv...
         Mounting /tmp...
         Mounting /var/cache...
         Mounting /var/log...
         Mounting /var/tmp...
[  OK  ] Mounted /root.
[  OK  ] Mounted /srv.
[  OK  ] Mounted /tmp.
[  OK  ] Mounted /home.
[  OK  ] Mounted /var/cache.
[  OK  ] Mounted /var/log.
[  OK  ] Mounted /var/tmp.
         Mounting /home/anael/Jeux...
         Mounting /home/anael/Seagate...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Finished Flush Journal to Persistent Storage.
[  OK  ] Mounted /home/anael/Jeux.
[  OK  ] Mounted /boot/efi.
[  OK  ] Mounted /home/anael/Seagate.
[  OK  ] Reached target Local File Systems.
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Set Up Additional Binary Formats...
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Tell Plymouth To Write Out Runtime Data.
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Userspace Out-Of-Memory (OOM) Killer...
         Starting Network Time Synchronization...
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
         Mounting Arbitrary Executable File Formats File System...
[  OK  ] Mounted Arbitrary Executable File Formats File System.
[  OK  ] Finished Set Up Additional Binary Formats.
[  OK  ] Started Userspace Out-Of-Memory (OOM) Killer.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Monitors for new snapshots.
[  OK  ] Started Daily Cleanup of Snapper Snapshots.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Path Units.
[  OK  ] Reached target System Time Set.
[  OK  ] Started Refresh existing PGP keys of archlinux-keyring regularly.
[  OK  ] Started Balance block groups on a btrfs filesystem.
[  OK  ] Started Defragment file data and/or directory metadata.
[  OK  ] Started Scrub btrfs filesystem, verify block checksums.
[  OK  ] Started Discard unused blocks on a mounted filesystem.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Daily verification of password and group files.
[  OK  ] Started Daily locate database update.
[  OK  ] Reached target Timer Units.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on Libvirt local socket.
[  OK  ] Listening on Libvirt admin socket.
[  OK  ] Listening on Libvirt local read-only socket.
[  OK  ] Listening on Virtual machine lock manager socket.
[  OK  ] Listening on Virtual machine log manager socket.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting D-Bus System Message Bus...
         Starting Pacman lock cleaner...
         Starting Optimizing pacman hooks...
         Starting Clean up modules from old kernels...
         Starting Authorization Manager...
         Starting User Login Management...
         Starting Virtual Machine and Container Registration Service...
         Starting UDisks2 managed ZRAM device zram0 setup...
[  OK  ] Finished Pacman lock cleaner.
[  OK  ] Finished Clean up modules from old kernels.
[  OK  ] Finished UDisks2 managed ZRAM device zram0 setup.
[  OK  ] Finished Optimizing pacman hooks.
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Virtual Machine and Container Registration Service.
[  OK  ] Started User Login Management.
[  OK  ] Started Authorization Manager.
         Starting Modem Manager...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting Virtualization daemon...
         Starting Permit User Sessions...
         Starting Hostname Service...
[  OK  ] Finished Permit User Sessions.
         Starting Light Display Manager...
         Starting Hold until boot process finishes up...

NFS share are not mounted and system boot fast ....

So it really related to my nfs share ....

Have you tried the other kernels yet?

I have also in the past found that using a systemd mount/automount unit for my NFS shares sometimes eliminated delays that occurred when using fstab, (& vice versa).

Not yet
what do you mean ?
you already have similar issue and you switched to another kernel or just change something in the way you mount NFS share ?

Did more test
like i said before, I've got in

 /etc/defaults/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off" # Modified by garuda-migrations: ibt=off

So I remove the

quiet splash splash

from GRUB_CMDLINE_LINUX_DEFAULT
And regenerate grub

grub-mkconfig -o /boot/grub/grub.cfg

I did few reboot
everything work ... but not my nfs share, I just broke my unit file system in my test with a wrong copy / paste :tired_face:

I currently don't have this issue, but I have experienced boot slowdowns in the past related to NFS.

Switching to a kernel such as the LTS or mainline sometimes helped.

On other occasions switching to using a mount/automount rather than fstab would correct this.

See:

https://man.archlinux.org/man/systemd-mount.1.en

https://man.archlinux.org/man/systemd.automount.5.en

Systemd mount units may look daunting upon first read, but they are actually quite straightforward.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.