I lost control of one of my VM after reboot

Question

Azure identified that one of our VM is currently in an inaccessible state because the file system table (fstab) file contains syntax errors or an entry for a file system that is not present on the VM.
This can occur due to multiple reasons, including incorrect naming of the file system in place or removing a data disk and restarting without updating the fstab file.

I do not know how to solve such an issue. Can I redeploy my system on another VM

Answer 1

Something here could help.
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux-virtual-machine-cannot-start-fstab-errors

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hello @Oliver.deprez ,
Welcome to Microsoft QnA.
Please share with us the contents of the fstab file (as is) without any modification.
fstab file will reside in /etc/fstab path. Also, share with me the result of lsblk command.
Whenever you mount a disk to Azure, you need to make the mount persistent by adding the UUID record to the fstab file. If you do not add the UUID record entry to fstab file, then once the VM reboots, the mount will not be persistent.
I think your fstab file is throwing error because of either some syntax issue in the file or misconfiguration.
You can share with me the above requested details if you're unable to fix it on your own and I can help further.

Do let me know if this helps and feel free to reach back to me by dropping a reply. Thank you.

-------------------

Please accept as answer and upvote if the above information is helpful.