We have some Windows 2012 R2 Hyper-V with dozens of VM running legacy systems and some departmental systems (XP, Win2003, Win2008, Win2012R2). They had worked for years without any problem.
In last December, we approve the monthly Windows Updates in the guest systems. In the next day, our IBM x3650 hosts presented disk errors and hanged, losing the disk array after restarted.
The host system logs had these records on Windows event viewer:
- Megasas2 ID 129 reset to device, \device\raidport0, was issued.
- Disk ID 153 - the IO operation at logical block address 0x for disk 2 (PDO: \device\0000005d) was retried.
- Megasas2 ID 11 - the driver detected a controller error on \device\raidport0
The systems running on HP DL160/360 were not affected. The problematic environment is IBM x3650 M4 HD 5460 configured to boot from internal LSI MegaRAID M5210e. We are using fixed VHDX.
All diagnosis made after reboot have no errors and the hosts work fine after reinstall until an updated guest is started. VM guests run normally in another environment.
With this, we have tried to reinstall the host system using all versions of LSI MEGASAS drivers that we can, with or without Windows updates in host OS. In all attempts, we have a server crash and disk array loss when a guest starts.
Has anyone experienced this problem? How can we confirm that this is a driver issue?
- Edited by Rafael_Araújo Wednesday, March 11, 2015 7:50 PM