The system that has the read-only file system problem, I have only seen it in Linux and Mac, the solution is the same.
When a file gets a read-only file system errorGenerally, the system is not shut down properly, resulting in a file system error on the virtual disk.
If this problem occurs with the system that has just been installed, it probably isMotherboard compatible or HDDThe problem is that the probability of this problem is small, and it needs to be analyzed in detail.
To fix this issue, it may lead to the loss of individual files or data, so make a backup before modifying itBe sure to make a backup when it comes to repairing files and databases
Workaround:Use fsck to manually repair disk files.
Steps to Resolve:
1. Use mount to view disk loading.
mount: used to check which module is read-only (if the partition mounted with the word ro appears, the partition is read-only).
2. Unmount the read-only partition with the command umount
If you find a prompt "device is busy", find out what process is making him busy
For example, you can execute etc initCommands such as d httpd stop stop some services that are running.
fuser -m home will show the PID using this module
fuser -mk home will kill that pid directly
3. fsck repairs disk files.
Command: fsck -fvy
4. Repeat the operations in 1-3 above.
5. Finally, restart the system.
ps: If there is a read-only problem in the root directory, and I haven't found a solution so far, it is recommended to reinstall the system.