filesystem eventually becomes read-only

Ralf Mardorf kde.lists at yahoo.com
Wed Mar 31 16:20:16 UTC 2021


On Wed, 31 Mar 2021 07:50:37 -0700, Noah wrote:
>that is not the answer - the problem is the drive is read-only

If so, then in addition to one of Colin's suggestions [1] you might be
able to get more details of what happened, as described by

https://serverfault.com/questions/962292/centos-zsh-locking-failed-for-root-zsh-history-read-only-file-system-readin/962319#962319

"[snip] When your root file-system encounters such an error, most of the
time the error won't be recorded in your log-files, as they will now be
read-only too. Fortunately since it is a kernel action the original
error message is recorded in memory first, in the kernel ring buffer.
Unless already flushed from memory you can display the contents of the
ring buffer with the dmesg command. [snip]"


[1]
On Wed, 31 Mar 2021 08:54:35 +0100, Colin Law wrote:
>If you look in syslog or use journalctl you will probably see errors
>occurring before it is set to readonly.




More information about the ubuntu-users mailing list