Now that we know why the filesystem is in the Read-Only mode, we can resolve it. Forcing the filesystem to go from Read-Only to Read-Write is actually pretty easy. However, because we don't know all of the circumstances around the failure that caused the filesystem to go into the Read-Only mode, we must be careful.
Recovering from filesystem errors can be extremely tricky; if not done properly, we could easily find ourselves in a situation where we have corrupted the filesystem or in other ways caused partial or even full data loss.
Since we have multiple filesystems in the Read-Only mode, we will first start with the /boot filesystem. The reason we are starting with the /boot filesystem is because this is technically the best filesystem to experience data loss. Since the /boot filesystem is only used during the server boot process, we can simply ensure that we do not reboot this server before the /boot filesystem can be recovered.