[Linux-ntfs-dev] Log unsafe read-only re-mount as an error

[Alex H. <tu...@gm...>]

Hello friends, I hope I'm in the right place!

I booted into Windows by mistake this morning, foolishly did a hard-reset,
not thinking anything of it and then my Linux system wouldn't work. I just
happened to install a new DKMS driver yesterday so I assumed that was the
issue and started digging...

It took me over half an hour to trace the issue back to the boot message
saying my root NTFS drive (a small SSD I use for both OS system-files) was
unsafe and mounted read-only. I did as instructed, booted and re-booted
Windows and here I am again a happy-penguin writing this.

While I am extremely thankful for that message which led me to easily fix
the issue, I'd suggest that you consider making it an error-priority
log-event. That would have saved me a good chunk of time and I can only
imagine less-skilled or less-lucky users could have missed it entirely.

Conceptually speaking, the unsafe status and the read-only re-mount was in
fact the one error that had my system broken and with it fixed everything's
back to normal.

Thank you all who put in the hard work that goes unnoticed until something
breaks! Cheers!