My vm starts with the system disk in read-only mode, so system can't load anything properly. The instance was created with the disk of and old vm, but in the instance properties disk is "boot, read/write" mode.

Server responds to ping, and I can connect by using FTP. Files are there but a lot of processes are not loaded as they should be.

Any tip for solving this issue?

  • It sounds a little like you might suffer from the XY problem. What makes you say the disk is in read-only mode, and what exact errors are you seeing? There isn't a fundamental issue with the boot/system disk being read-only, so long as the system is configured accordingly. I think it might help get you some answers if you could expand a little on the issues you see with your processes, and provided a bit more background on how you moved your disk to a new VM. – iwaseatenbyagrue Mar 23 '17 at 8:51
  • If you were able to solve this, you can post self-answer here for other community members who may be seeing this same issue. If not, you can provide further information as @iwaseatenbyagrue suggested to further troubleshooting. – Faizan Mar 31 '17 at 16:35
  • Is there a filesystem error inside the VM file? – Matt Jun 6 '17 at 22:12

The only typical scenario where a disk get mounted as read only is when the disk is attached to multiple VMs. You might want to check the FS consistency and the information given by dmesg. Another place to have a look is the content of /etc/fstab just in case the default file was re-written and is mounting the disk as read only.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.