Unsolved
This post is more than 5 years old
24 Posts
0
8480
OME 2.0 in-bound update rebooted servers not through Windows?
It happened on several R620 with Windows 2012R2. OME System update rebooted the server. It seems that the rebooting was not done through Windows. (asked the OS to reboot)
Windows event log did not log this event. It hit hard on hyper-v. Virtual machines were not properly shut down. Many VMs booted into recovery model when windows came up. This may cause VM disc corruption.
Anyone encountered similar issue? So can someone explain the rebooting process?
f2000sa
24 Posts
0
October 9th, 2014 11:00
I have OMSA installed on every server. All updates use in-bound. Thanks
DELL-Pupul M
1K Posts
0
October 9th, 2014 11:00
Hi,
Were you trying to perform system update through out of band of through OMSA method?
DELL-Pupul M
1K Posts
0
October 9th, 2014 12:00
Hi,
Let me do a little bit of digging around and i'll get back with what i get.
DELL-Arun Mo
116 Posts
0
November 5th, 2014 06:00
Hi,
Thanks for the post. OME does OS reboot through windows only (asked the OS to reboot).
In case of Hyper-V, it is the setting in Hyper-V to decide what action to perform on VMs when host is rebooting.
This action is controlled by the setting called "Automatic Stop Action Shutdown".
It has 3 possible settings,
1) save the virtual machine state (this is default)
2) Turn off the virtual machine (this will result in abrupt restart of VM)
3) Shutdown the guest operating system
I would recommend to choose the 3rd option.
Let us know if it helps.
Thanks,
Arun