On Wednesday 10 Dec 2025, at 16:22, [email protected] wrote: > In either case the filesystem is dirty and you should > force a filesystem check. The journaling code has no > knowledge about such manual interventions.
I did a new boot to single user, configured the raidframe, fsck -f (still no errors), then forcibly clri the inode with fsdb and fsck again. All seems fine, so I don't know what happened in the first place and why that apparently vanished. Let's see if this triggers again. I could also try to create the infamous inode with fsdb and see what happens.
