I am hoping to see what really triggers the error in dmesg even if that might corrupt some data somewhere in the process.
The only challenge now is that I may not see the i/o error that freezes the system as root will not become read only.
What should I specifically look for in dmesg?
If I move /var/log into a separate partition on the same disk and keep root as remount,ro on errors and mount the /var/log partition without the ro remount option would I be able to see the error that leads to the remounting read only?
The system was crashing every few minutes today. Took a backup of the relevant data in the system and changed fstab mount option for root partition to
UUID=3167581c- 60b0-4db8- 972c-a8dfafc882 c5 / ext4 defaults
So took out the remount,ro option.
I am hoping to see what really triggers the error in dmesg even if that might corrupt some data somewhere in the process.
The only challenge now is that I may not see the i/o error that freezes the system as root will not become read only.
What should I specifically look for in dmesg?
If I move /var/log into a separate partition on the same disk and keep root as remount,ro on errors and mount the /var/log partition without the ro remount option would I be able to see the error that leads to the remounting read only?