I put UUID=fb2b6c2e-a8d7-4855-b109-c9717264da8a /                       ext4    auto,noatime,noload,data=ordered,commit=10,defaults        1 1 in fstabAnd 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 fromsingle user mode, but I might be able to edit it using one of my pxe boot toolsto 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 fstabfor you, but I am justifying it as necessary to restore connectivity)...I search for the purpose of noload option in googlehttps://www.google.com/search?q=fstab+noload&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-aand 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:
What does the noload option do in fstab?
fstab
noload doesn't turn off journaling. It suppresses the loading of the journal, without turning off journaling. As you can imagine, that's usually not a good thing.noload is mostly useful to mount a disk as read-only without changing it in the slightest way, not even replaying the journal. You can read most data this way, and you can even read all data if the journal was flushed (by calling sync). For example, this is a way of reading from a filesystem that is currently mounted by a hibernated system.noload may or may not be the cause of your problem, but in any case it's a very bad idea, and definitely not something to use in /etc/fstab.