Hey everyone!
I have a customer that started having an issue about a month ago. Their running 2012 R2 with a hyper-v cluster. Their backups would fail until a server reboot was performed. We have narrowed it down to the drive not being ejected properly. But it's not just one drive. We have 15 of them and all of them have the same issue.
I have read tons of forums about ejecting safely to off-lining the drive (which is a big no no) to changing the hardware policy. None of which have worked.
Basically we found out that as soon as we hit the eject option from the tray the system just sits there. All of the sudden the below processes show up:
Then we get the error:
No matter how many times we try we cannot eject the drive. If we just unplug it we get thousands of these:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume7.
(A device which does not exist was specified.)
Once that happens then we have to force reboot the system and can't migrate and of the hyper-v cluster roles away ending up in a entire system crash.
We have learned though! After each backup is complete we drain the cluster roles from the server and reboot it. We can then eject the drive safely.
So... Anyone got any ideas? Maybe a recent microsoft patch?
Please let me know. Thanks!
