unexpectedly last booting failed with this error message:
DATEN0500: Superblock needs_recovery flag is clear, but journal has data.
DATEN0500: Run journal anyway
DATEN0500: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
I pulled the respective data drive and got a normal boot. Also after this on a second try, overriding this message with [CTRL] [D] continues to boot, and data on this drive are still present.
Any idea was caused this error (SMART data are ok.) ?
How to proceed with fsck, which options should be used, to regain consistency and not to erase anything?
As my server is normally running headless, is there an option that this error does not stop the boot process, but just send an report via email or some message inside the web-gui?
Thanks for any help