Deploying Updates Using OME: one of the filesystems was not cleanly unmounted and had to be checked
I recently deployed some updates to a server running RHEL 5. Everything seemed to have gone well, it rebooted to the Lifecycle Controller and installed all of the updates without any problems.
After installing the updates, when the OS booted I was informed that one of the filesystems was not cleanly unmounted and had to be checked. This was a local file system (not NFS, etc.)
Question: How is the system restart performed when deploying updates using OME? Is there anything that could have prevented it from performing a clean restart?
Fortunately the filesystem check passed this time - I would just like to be sure to avoid this in the future since we are now starting to use OME with our RHEL servers. I have never had this come up with any of my Windows servers.