Accepted Solutions
Your ungraceful shutdown happened on 05/09 at 22:58:49 - 23:04:05. You can see that you have 2 "Boot" statements in a row which indicates the VM was either hard powered down or reloaded ungracefully. This is mentioned in the document that @Roger Kallberg included.
The most common scenarios for ungraceful shutdowns are someone inadvertently hard powering off the VM in ESXi using Power Off instead of gracefully shutting it down with Shut Down Guest. Shutting the guest OS down will gracefully send the shutdown commands using VMTools so it behaves as if you issue "utils system shutdown" from the CLI. The former will just abruptly power the VM off instantly, thus causing the dual Boot entries you see without a Shutdown/Restart entry.
That’s a warning that tells you that the system was shutdown in an incorrect way. As this can cause inconsistencies or corruption in the file system it is not a good thing. Your advices to verify that the system integrity is intact and if it ain't your adviced to reinstall the server and restore a backup. If all is okay there is a command to turn off the warning, see this article. Recover from Ungraceful Shutdowns on VOS
I can see in the documentation we can verify whether we have 'Ungraceful shutdown' or not in the log
But if i check in my log there is no 'Ungraceful shutdown'
Your ungraceful shutdown happened on 05/09 at 22:58:49 - 23:04:05. You can see that you have 2 "Boot" statements in a row which indicates the VM was either hard powered down or reloaded ungracefully. This is mentioned in the document that @Roger Kallberg included.
The most common scenarios for ungraceful shutdowns are someone inadvertently hard powering off the VM in ESXi using Power Off instead of gracefully shutting it down with Shut Down Guest. Shutting the guest OS down will gracefully send the shutdown commands using VMTools so it behaves as if you issue "utils system shutdown" from the CLI. The former will just abruptly power the VM off instantly, thus causing the dual Boot entries you see without a Shutdown/Restart entry.
Cisco introduced this feature in 12.5 SU releases to notify of ungraceful server shutdowns, which may negatively impact operations.
Disable it using the CLI command: utils ungraceful warn disable. Before disabling, perform checks outlined in the document shared by @Roger Kallberg .
This is common among some of my customers.
