Failed to boot and to mount drives after update to 10.0.1

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • Date | 2026-02-07 15:19:24
  • Program name | DietPi-Drive_Manager
  • Command | mount -o noatime,lazytime,rw,permissions,big_writes /dev/sda4 /mnt/F40E7C7B0E7C3926
  • Exit code | 255
  • DietPi version | v10.0.1 (MichaIng/master)
  • Distro version | bookworm (ID=7,RASPBIAN=0)
  • Kernel version | Linux HarderPi 6.12.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1~bookworm (2026-01-19) aarch64 GNU/Linux
  • Architecture | arm64
  • Hardware model | RPi 5 Model B (aarch64) (ID=5)
  • Power supply | (EG: RAVPower 5V 1A)
  • SD card | (EG: SanDisk Ultra 16 GB)

Steps to reproduce:

  1. Update from 9.x to 10.0.1
  2. reboot
  3. get notice about maintance mode (see Help with booting problem Rpi4 and Ssd)
  4. continue with Ctrl-D
  5. try to mount drives with Drive_Manager

Expected behaviour:

  • after reboot it should start normally and auto login without me going to raspi and manually put the device out of maintance mode
  • auto mount drives without problems

Actual behaviour:

  • after reboot my pi tells me that it started in maintance mode
  • drives can’t be mounted, nor with Drive Manger, nor per command line

Extra details:

  • I have paperless and ownfoil running as docker service by other user

Additional logs:
2

Can you share a picture or error message? DietPi don’t have a maintenance mode. Mean’s, it’s something else.

3

https://photos.app.goo.gl/wvkN1C1oFP83NoPk6 (with videos)

PXL_20260207_151038665
PXL_20260207_1510386651920×1080 569 KB

P.S. i have missspelled, not maintaince but emergency mode

4

are there any red / failed messaged above? Probably there are issues to read the external drive, hence system is not able to boot up correctly

5

i had unplugged all drives and rebooted - same behavior.

but this ist the failed line:
failed to start systemd-fsck-root.service - File System Check on Root Device

Details:

root@HarderPi:~# systemctl status systemd-fsck-root.service
× systemd-fsck-root.service - File System Check on Root Device
     Loaded: loaded (/lib/systemd/system/systemd-fsck-root.service; enabled-runtime; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2025-06-26 16:58:50 CEST; 7 months 12 days ago
  Condition: start condition failed at Sat 2026-02-07 16:11:47 CET; 47min ago
             └─ ConditionPathIsReadWrite=!/ was not met
       Docs: man:systemd-fsck-root.service(8)
   Main PID: 172 (code=exited, status=1/FAILURE)
        CPU: 393ms

Jun 26 16:58:48 HarderPi systemd-fsck[196]: /dev/mmcblk0p2 contains a file system with errors, check forced.
Jun 26 16:58:50 HarderPi systemd-fsck[196]: /dev/mmcblk0p2: Inodes that were part of a corrupted orphan linked list found.
Jun 26 16:58:50 HarderPi systemd-fsck[196]: /dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Jun 26 16:58:50 HarderPi systemd-fsck[196]:         (i.e., without -a or -p options)
Jun 26 16:58:50 HarderPi systemd-fsck[172]: fsck failed with exit status 4.
Jun 26 16:58:50 HarderPi systemd[1]: systemd-fsck-root.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 16:58:50 HarderPi systemd[1]: systemd-fsck-root.service: Failed with result 'exit-code'.
Jun 26 16:58:50 HarderPi systemd[1]: Failed to start systemd-fsck-root.service - File System Check on Root Device.
Jun 26 16:58:50 HarderPi systemd[1]: systemd-fsck-root.service: Triggering OnFailure= dependencies.
Feb 07 16:11:47 HarderPi systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).

and sometimes i had the issue that even basic commands got an error: bash: /usr/bin/ls: Input/Output error. i had to pull power cable cus i couldn’t reboot it with command