Long story short, I was mounting a disk to my vm instances but I didn't specify the NOFAIL_OPTION on /etc/fstab. Thus, after resarting the instance, i could not access the ssh. After trying to access the serial console, I got the error in the image above. I have tried to search some answer and have add startup script to add sudo user
However, it didn't solve my problem. Basically,I need the data on the boot and additional persistent disk. Would appreciate any help. Thank you.
I solve the problem by making changes to the file by attaching the bootable disk as additional disk on new instance just like John said in his article :) Thanks! hope this will be helpful for those who could not access ssh and need to make changes to the unbootable system file.
This also happened to me recently. I solved the issue by attaching the boot disk of the problematic instance to a new instance, however, the NO_FAIL causing the system to break is what interests me. This has never happened before. The UUID is correct, and the syntax is also correct, hence what was the cause of the original problem in your case? I'm still trying to figure mine out.
