Fix error disk read-only in VestaCP after reboot

by Daniel Pham
Published: Updated:

How to fix error disk read-only in VestaCP server after reboot?

Today I will share with you an error I encountered when using VestaCP.

Describe the error situation

I use a CentOS 7.6.1810 (Core) server and VestaCP 0.9.8-23.

Today I modified the nginx file configuration of a website in VestaCP and restarted the server.

After about 2 minutes, I could not connect to the server using SSH.

I made the console connection into the VestaCP server to see what was going on.

Error appears when reboot VestaCP

On the console window I get a message that I cannot start the server because It cannot read the partition on the disk.

Fortunately, the console window allows me to enter the root password to login to see what happens. And I don’t see partition /home. VestaCP installed on this partition.

This partition has the XFS system file type before installing VestaCP. After that, I checked the /etc/fstab file and found it to be quite strange file system format.

/dev/mapper/centos-home /home                       xfs     defaults,usrquota,grpquota,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0        0 0
the /home partition changes the system file from XFS to a new format
The /home partition changes the system file from XFS to a new format.

I tried using the mount -a command to re-mount the partitions on the disk but failed.

try mount the partitions but failed
Try mount the partitions but failed.

Cause error disk read-only when reboot VestaCP

Recommended Reading: How to install VestaCP in CentOS 7

After searching one round, I found out that I’m not the only one who encountered this case.

There are people who are like the dark and they wrote on the VestaCP forum.

And I also found a confirmation bug link for this error of VestaCP.

Fix error disk read-only after reboot

What should I do now? If it’s a bug, then don’t wait. I have followed the suggestions on the forum.

I edited the file /etc/fstab, reformatted the /home partition to file system type XFS. Then reboot the server.

It looks like this.

/dev/mapper/centos-home /home                       xfs     defaults        0 0

And it worked again. Something very strange.

Why does VestaCP change the file system format of the /home partition so that error happens.

Conclusion

I have shared a very practical case I have encountered in the process of using VestaCP. If you encounter it like me, I hope you will solve it like I did. Good luck.

(This is an article from my old blog that has been inactive for a long time, I don’t want to throw it away so I will keep it and hope it helps someone).

0 0 votes
Article Rating

You may also like

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments

DevOps Lite is a personal blog specializing in technology with main topics about DevOps, DevSecOps, SRE and System Administrator. Articles are shared for free and contributed to the community.

SUPPORT US

FOLLOW US

Subscribe my Newsletter for new blog posts. Stay updated from your inbox!

© 2021-2024 DevOpsLite.com – All rights reserved.

Please write sources “DevOpsLite.com” when using articles from this website.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

0
Would love your thoughts, please comment.x
()
x

Adblock Detected

Please support us by disabling your AdBlocker extension from your browsers for our website.