UUID=fb2b6c2e-a8d7-4855-b109-c9717264da8a / ext4 auto,noatime,noload,data=ordered,commit=10,defaults 1 1 in fstab
And now server fails to reboot. It can reboot but reject all kind of connections.
This is what my provider said:
Yeah, the noload option might be problematic... I can't edit /etc/fstab from single user mode, but I might be able to edit it using one of my pxe boot tools to enter the filesystem manually. With regards to your request about /var/log/messages and /var/log/secure, I'm afraid I can't do that for you (technically, I'm already bordering on managed services by editing your fstab for you, but I am justifying it as necessary to restore connectivity)...
I search for the purpose of noload option in google
and have no issue. Someone in linux forum says that it disable journaling.
I'm unable to paste the actual error messages without manually typing them out, but I assure you they're not really very descriptive (basically, system indicates that it is unable to remount root in read/write mode, and then errors composed of read/write problems, particularly in /var are printed to the screen)...
It does end in a happy ending:
Your server is back online, and I was able to successfully disable your iptables (which for reference, I did confirm were causing connectivity issues), and I am now able to ssh into your server with the credentials provided earlier in this ticket: