> That is completely expected. The fsck check is ran on unmounted disks... > mounting first and repairing later doesn't make sense and is unsupported > by fsck... So there is no /var/log/messages to log to.
i was just expecting that there's some in-memory ring buffer that is flushed when root becomes available in rw mode... > fsck is always ran on startup, the question is if it reports everything > is clean or not. i often see a few lines (0-10) of orphaned inodes and stuff like that. nothing dramatic, and certainly nothing that demands user feedback. but i think the `recovering journal` part is an unambigous indication that the fs was not cleanly unmounted. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- Human culture grows in the cracks of power.
