Why did my Linux VM go read only?

Why did my Linux VM go read only?

I have several Linux VMs on VMware + SAN. A problem occured on the SAN (failed path) so that for some time, there were I/O errors on the Linux VMs drives. When the path failover had been done, it was too late: every Linux machine considered most of its drives as not “trustworthy” anymore, setting them as read-only devices.

Can a virtual machine read and write from a shared folder?

Access to files in the shared folder is also governed by permission settings on the host computer. For example, if you are running VMware Workstation as a user named User, the virtual machine can read and write files in the shared folder only if User has permission to read and write them.

What causes RedHat virtual machine to become read only?

This issue is caused due to the temporary disconnection to storage disks. As per Redhat article ,When a storage failure occurs at the VMware Hypervisor level, It may takes longer sometime than the actual SCSI timeout to expire.

Why is there an error on my VM?

The VM decides that the disk is inaccessible and the disk write faults, causing an error. The error is handled in tune with how the file systems “error” value is set.

What to do when your VM won’t start?

If the disk fails to mount, run the xfs_repair command with the -L option (force log zeroing): Next, try to mount the file system. If the disk is mounted successfully, you will receive the following output: Restart the VM, and then check if the problem is resolved.

How to set up a recovery VM in Linux?

Attach the system disk of the VM as a data disk to a recovery VM (any working Linux VM). To do this, you can use CLI commands or you can automate setting up the recovery VM using the VM repair commands. Locate the drive label of the system disk that you attached.

Why is my Linux VM not remounting?

[ 14.252404] EXT4-fs (sda1): Couldn’t remount RDWR because of unprocessed orphan inode list. Please unmount/remount instead An error occurred while mounting /. This example is caused by a clean fsck. In this case, there are also additional data disks attached to the VM (/dev/sdc1 and /dev/sde1).