# Unexpected entries in journalctl. system only boots randomly

**URL:** <https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [January 28, 2024, 8:55am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518 "2024-01-28T08:55:36Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 8:55am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/1 "2024-01-28T08:55:36Z")

</div>

I have noticed very strange entries in the journalctl.  
My system only boots very irregularly. Sometimes I have to start a few times, sometimes it boots immediately, but most of the time it hangs as shown in the picture. I have also attached a few journalctl entries.  
Who can help me to bring my system back to a normal level?

```auto
ryzen bootctl[758]: ! Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! !
ryzen bootctl[758]: ! Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! 

ryzen systemd-logind[776]: /efi/loader/loader.conf:5: Unknown line 'reboot-for-bitlocker', ignoring.

ryzen systemd-fstab-generator[454]: Mount point 0 is not a valid path, ignoring.

```

> **Pictures of the boot process**
>
> ![IMG_20240128_082515](https://forum.endeavouros.com/uploads/default/original/3X/5/2/5200cafd15e6ea8a14cff75395f48aa03428c791.jpeg)  
> ![IMG_20240128_082700](https://forum.endeavouros.com/uploads/default/original/3X/e/5/e51f01cf758ed89255c87ea1fd2ad64346c40904.jpeg)  
> ![IMG_20240128_082838](https://forum.endeavouros.com/uploads/default/original/3X/6/8/68a9181c34bf80b982657c6634cb2ec0015b3b1e.jpeg)

```auto
`journalctl -b`
https://0x0.st/HDr8.txt

```

```auto

`journalctl -xb`
https://0x0.st/HDrP.txt

```

```auto
➜ lsblk -o name,type,size,PTTYPE,FSTYPE
NAME TYPE SIZE PTTYPE FSTYPE
sda disk 931,5G dos    
└─sda1 part 931,5G dos ext4
sdb disk 931,5G ext4
sdc disk 223,6G gpt    
└─sdc1 part 223,6G gpt ext4
sr0 rom 1024M        
nvme0n1 disk 931,5G gpt    
└─nvme0n1p1 part 931,5G gpt ext4
nvme1n1 disk 232,9G gpt    
├─nvme1n1p1 part 500M gpt vfat
└─nvme1n1p2 part 232,4G gpt ext4

```

```auto
➜ inxi -Fza   
System:
  Kernel: 6.6.14-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: initrd=\f329784de44446948b3869b7b1d20a31\6.6.14-1-lts\initrd
    nvme_load=YES nowatchdog rw
    root=UUID=de0eeb1f-095d-408b-b6c3-ebda58df6d41
    systemd.machine_id=f329784de44446948b3869b7b1d20a31
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_x11 vt: 2
    dm: SDDM Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2
    serial: <superuser required> UEFI: American Megatrends LLC. v: F16h
    date: 12/25/2023
CPU:
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000F
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1062 high: 3148 min/max: 400/4673 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3021 2: 400 3: 400
    4: 3023 5: 400 6: 400 7: 400 8: 400 9: 400 10: 3006 11: 400 12: 400
    13: 400 14: 400 15: 3148 16: 400 bogomips: 121408
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-2
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 03:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: DP-2 mapped: DisplayPort-1 model: LG (GoldStar) ULTRAGEAR
    serial: <filter> built: 2022 res: 1920x1080 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.4-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
    LLVM 16.0.6 DRM 3.54 6.6.14-1-lts) device-ID: 1002:73ff memory: 7.81 GiB
    unified: no
  API: Vulkan v: 1.3.276 layers: 3 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6600 (RADV NAVI23) driver: mesa radv v: 23.3.4-arch1.2
    device-ID: 1002:73ff surfaces: xcb,xlib
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 09:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 09:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Device-4: Logitech V10 Notebook Speakers
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-3:2 chip-ID: 046d:0a10 class-ID: 0300
  API: ALSA v: k6.6.14-1-lts status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.17 TiB used: 2.14 TiB (67.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 28.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QGXA7 temp: 31.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A8R0 scheme: MBR
  ID-4: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A8R0
  ID-5: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 052 scheme: GPT
Partition:
  ID-1: / raw-size: 232.39 GiB size: 227.69 GiB (97.97%)
    used: 59.79 GiB (26.3%) fs: ext4 dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /home raw-size: 931.51 GiB size: 915.82 GiB (98.31%)
    used: 537.55 GiB (58.7%) fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 16 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 38.1 C mobo: 27.0 C gpu: amdgpu temp: 34.0 C
    mem: 34.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Processes: 385 Uptime: 28m wakeups: 0 Memory: total: 16 GiB
  available: 15.46 GiB used: 4.43 GiB (28.6%) Init: systemd v: 255
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1779 libs: 391 tools: yay pm: flatpak pkgs: 0
  Shell: Zsh v: 5.9 default: Bash v: 5.2.26 running-in: konsole inxi: 3.3.31

```

---

<div class="post-metadata">

**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\
**Post date:** [January 28, 2024, 9:07am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/2 "2024-01-28T09:07:44Z")

</div>

have you try to boot kernel with theses options  
“amd-pstate=guided” ?

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:08am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/3 "2024-01-28T09:08:45Z")

</div>

No, what do I have to do to boot this way?

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 9:09am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/4 "2024-01-28T09:09:38Z")

</div>

> [@swh](#):
>
> ```auto
> ryzen bootctl[758]: ! Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! !
> ryzen bootctl[758]: ! Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! 
> 
> ```

For this, see:

> [@"bootctl install" outputs some warnings about /efi mount point and random seed file in the terminal](https://forum.endeavouros.com/t/bootctl-install-outputs-some-warnings-about-efi-mount-point-and-random-seed-file-in-the-terminal/43991):
>
> I needed to recreate my systemd-boot’s EFI boot entry in an oldish system converted from Grub. I did a sudo bootctl install and I got the output here below: Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi". Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".warning Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! warningwarning Random seed file '/efi/loader/random-seed' is wo…

> [@swh](#):
>
> `ryzen systemd-logind[776]: /efi/loader/loader.conf:5: Unknown line 'reboot-for-bitlocker', ignoring.`

This is the fist time I see ‘reboot-for-bitlocker’ in /efi/loader/loader.conf.  
I cannot find any reference to this option in `man loader.conf` and I guess it must have gotten in there by mistake (?).

> [@swh](#):
>
> `ryzen systemd-fstab-generator[454]: Mount point 0 is not a valid path, ignoring.`

What is the content of your `/etc/fstab` ?

Also, are you using a seperate partition for /home?

---

<div class="post-metadata">

**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\
**Post date:** [January 28, 2024, 9:10am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/5 "2024-01-28T09:10:20Z")

</div>

are you using dracut ( systemd-boot ) or grub ?  
this is bootlctl ( direct systemd )

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:12am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/6 "2024-01-28T09:12:49Z")

</div>

> [@pebcak](#):
>
> What is the content of your `/etc/fstab` ?

```auto
  GNU nano 7.2 /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=74af6462-ba4b-48bf-993b-164ba88fbabb /home ext4 defaults,noatime 0 2
UUID=D3E2-C3D4 /efi vfat defaults,noatime 0 2
UUID=de0eeb1f-095d-408b-b6c3-ebda58df6d41 / ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

#Swapfile
/swapfile none swap defaults 0 0

#Mediathek sda1
UUID=9b940cbe-8123-4748-91f3-8116edd8bd43 /run/media/swh/Mediathek ext4 defaults 0 0
#Stuff sdb
UUID=70357a40-3800-404d-a68e-dc5b32c83377 /run/media/swh/Stuff ext4 defaults 0 0
#SSD ssd
UUID=76bd6be1-9d39-40d3-817a-e3acbc647e0a /run/media/swh/76bd6be1-9d39-40d3-817a-e3acbc647e0a ext4 defaults 0 0

#nfsv4
/run/media/swh/Mediathek/Share/ /srv/nfsv4/Share/ none bind 0 0
/run/media/swh/Stuff/Filme/ /srv/nfsv4/Filme/ none bind 0 0

#smbFritzBox
//192.168.178.1/FRITZBox/3xt1/ /mnt/FRITZBox/3xt1/ cifs x-systemd.automount,x-systemd.idle-timeout=1min,rw,uid=swh,gid=swh,credentials=/etc/samba/private/credfile.cred,noserverino,
iocharset=utf8,vers=1.0 0 0

```

> [@pebcak](#):
>
> Also, are you using a seperate partition for /home?

It’s a seperate nvme

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:13am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/7 "2024-01-28T09:13:21Z")

</div>

I am using dracut

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 9:17am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/8 "2024-01-28T09:17:48Z")

</div>

> [@swh](#):
>
> > [@pebcak](#):
> >
> > Also, are you using a seperate partition for /home?
> 
> It’s a seperate nvme

I would fire up the Live usb and run a filesystem check on the home partition:

```auto
UUID=74af6462-ba4b-48bf-993b-164ba88fbabb /home 

```

---

<div class="post-metadata">

**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\
**Post date:** [January 28, 2024, 9:17am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/9 "2024-01-28T09:17:49Z")

</div>

check then in this file  
/etc/dracut.conf.d/cmdline.conf where you can find  
“nvme\_load=YES nowatchdog”

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:21am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/10 "2024-01-28T09:21:40Z")

</div>

I dont have a `cmdline.conf` . Can I create this file again and enter it with this entry?

```auto
➜ ls                                   
eos-defaults.conf

```

---

<div class="post-metadata">

**Author:** ![BS86](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/bs86/32/18119_2.png) [@BS86](https://forum.endeavouros.com/u/BS86)\
**Post date:** [January 28, 2024, 9:25am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/11 "2024-01-28T09:25:43Z")

</div>

ignore Stephanes hints. The iommu part can help in very rare cases with old CPUs/mainboards and the pstate part would actually do nothing but is also aimed at the CPU while your logs clearly show some file system related problems.

pebcak’s hints and suggestions should help you identify and solve your problem as those are trying to find the file system fault.

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:31am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/12 "2024-01-28T09:31:02Z")

</div>

> [@pebcak](#):
>
> I would fire up the Live usb and run a filesystem check on the home partition:

Ok thank you.

But can you guide me point by point on how to do this?  
I really reach my limits with such actions 😉 But it’s a good way to learn new things!

---

<div class="post-metadata">

**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\
**Post date:** [January 28, 2024, 9:31am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/13 "2024-01-28T09:31:34Z")

</div>

i understand after details in the 2nd log  
also a df -Th may be required for space

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 9:41am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/14 "2024-01-28T09:41:25Z")

</div>

If you have Gparted in the Live usb, launch it, double click on the partition and choose Check (or something similar) from the menu and apply the operation in the toolbar ✅

If memory serves me right, kde partition manager should have something similar as well.

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:45am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/15 "2024-01-28T09:45:58Z")

</div>

KDE Manager got the same. I ll check if there is GParted on LiveUSB. Ill report later. Thank you.  
I thought I had to do this somehow with fschk. That’s why I asked.

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 9:48am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/16 "2024-01-28T09:48:16Z")

</div>

> [@swh](#):
>
> I thought I had to do this somehow with fschk. That’s why I asked.

You can use [fsck](https://wiki.archlinux.org/title/Fsck) as well from the terminal but using Gparted (or kde partition manager) is more convenient I think.

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 9:52am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/17 "2024-01-28T09:52:34Z")

</div>

Gonna try it. I have a backup running. I ll report when finished!

---

<div class="post-metadata">

**Author:** ![Zesko](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/zesko/32/77795_2.png) [@Zesko](https://forum.endeavouros.com/u/Zesko)\
**Post date:** [January 28, 2024, 10:19am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/18 "2024-01-28T10:19:01Z")

</div>

> [@pebcak](#):
>
> > [@swh](#):
> >
> > ```auto
> > ryzen bootctl[758]: ! Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! !
> > ryzen bootctl[758]: ! Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! 
> > 
> > ```
> 
> For this, see:
> 
> > [@](#):
> >
> > I needed to recreate my systemd-boot’s EFI boot entry in an oldish system converted from Grub. I did a sudo bootctl install and I got the output here below: Copied “/usr/lib/systemd/boot/efi/systemd-bootx64.efi” to “/efi/EFI/systemd/systemd-bootx64.efi”. Copied “/usr/lib/systemd/boot/efi/systemd-bootx64.efi” to “/efi/EFI/BOOT/BOOTX64.EFI”. warning Mount point ‘/efi’ which backs the random seed file is world accessible, which is a security hole! warning warning Random seed file ‘/efi/loader/random-seed’ is wo…

Add `fmask=0077,dmask=0077` instead of `fmask=0137,dmask=0027`, because `0077` has more restriction of root permission than others. It is default for FAT32 on the _esp_ partition. AFAIK.

Note: `fmask=0077,dmask=0077` is the same as `umask=0077` that is an abbreviation.

[https://www.kernel.org/doc/Documentation/filesystems/vfat.txt](https://www.kernel.org/doc/Documentation/filesystems/vfat.txt)

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [January 28, 2024, 10:27am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/19 "2024-01-28T10:27:26Z")

</div>

> [@Zesko](#):
>
> Add `fmask=0077,dmask=0077` instead of `fmask=0137,dmask=0027`, because `0077` has more restriction of root permission than others. It is default for FAT32 on the _esp_ partition. AFAIK.

This is what is generated automatically by genfstab in a Vanilla Arch install:

> UUID=95E3-3E45 /boot/efi vfat rw,relatime, **fmask=0022,dmask=0022** ,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

🤔

---

<div class="post-metadata">

**Author:** ![swh](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/swh/32/95303_2.png) [@swh](https://forum.endeavouros.com/u/swh)\
**Post date:** [January 28, 2024, 10:28am UTC](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518/20 "2024-01-28T10:28:58Z")

</div>

@pebcak this is my new `journalctl -xb`

[https://0x0.st/HDr9.txt](https://0x0.st/HDr9.txt)

Can you look over it again. I’m sorry, I don’t know how to read this

[Next page](https://forum.endeavouros.com/t/unexpected-entries-in-journalctl-system-only-boots-randomly/50518.md?page=2)