garethEds Posted October 25, 2019 Posted October 25, 2019 Evening All, So this evening, as it was the end of our 8 week term I decided to look at upgrading our HyperV cluster from 2016 to 2019 using an in-place upgrade. I'd planned to do a clean upgrade next week anyway so thought I'd try it. Everything was backed up - all HyperV machines and the three cluster servers. All safe and tested. So - here we go. Set off Server 1 (HP380g8 e)- Took all the VMs off, restarted it to clear any pending restarts and set it off. It chugged away. Took about an hour. Rebooted and everything was in the same place but a nice speedy 2019 server. Set off Server 2 (HP380g8 e) - accessed the mounted ISO, started looking for 2019 updates and bang - died. Blue screen a 'Stop Code: DPC Watchdog Violation' - thought - hmmmm. Ok. Leave it for a mo. I'll look it up. Could be a driver issue. Set off Server 3 (HP380g8 p) - did exactly the same, moved VMs to Server 1 and 2 (which was still on 2016) - off it went, upgraded. I went for a run and when I came back it was running 2019 - all nice and dandy. I now have my cluster running in mixed mode (or whatever it is called). I'll have to go in on Monday and look at Server 2. I've made sure all drivers are updated, all CUs are in place, everything looked to be working - no cluster errors. No event viewer errors (besides thge big one). Apart from Server 2 - it all went really well. But what is wrong with Server 2. Anyone have any ideas based on that stop code? Have a good weekend everyone, Gareth 1
mavhc Posted October 26, 2019 Posted October 26, 2019 https://www.nirsoft.net/utils/blue_screen_view.html
jslate1980 Posted October 26, 2019 Posted October 26, 2019 Evening All, So this evening, as it was the end of our 8 week term I decided to look at upgrading our HyperV cluster from 2016 to 2019 using an in-place upgrade. I'd planned to do a clean upgrade next week anyway so thought I'd try it. Everything was backed up - all HyperV machines and the three cluster servers. All safe and tested. So - here we go. Set off Server 1 (HP380g8 e)- Took all the VMs off, restarted it to clear any pending restarts and set it off. It chugged away. Took about an hour. Rebooted and everything was in the same place but a nice speedy 2019 server. Set off Server 2 (HP380g8 e) - accessed the mounted ISO, started looking for 2019 updates and bang - died. Blue screen a 'Stop Code: DPC Watchdog Violation' - thought - hmmmm. Ok. Leave it for a mo. I'll look it up. Could be a driver issue. Set off Server 3 (HP380g8 p) - did exactly the same, moved VMs to Server 1 and 2 (which was still on 2016) - off it went, upgraded. I went for a run and when I came back it was running 2019 - all nice and dandy. I now have my cluster running in mixed mode (or whatever it is called). I'll have to go in on Monday and look at Server 2. I've made sure all drivers are updated, all CUs are in place, everything looked to be working - no cluster errors. No event viewer errors (besides thge big one). Apart from Server 2 - it all went really well. But what is wrong with Server 2. Anyone have any ideas based on that stop code? Have a good weekend everyone, Gareth Noticed a blog where someone had the same issue caused by the ilo channel interface driver needed updating. 1
garethEds Posted October 26, 2019 Author Posted October 26, 2019 https://www.nirsoft.net/utils/blue_screen_view.html Thanks mate - I'll take a look at this on Monday. Gareth
garethEds Posted October 26, 2019 Author Posted October 26, 2019 Noticed a blog where someone had the same issue caused by the ilo channel interface driver needed updating. Thanks @jslate1980 - I'll have a search for this via Google. If you have any idea where it is then let me know. Weird thing is - Server 1 has exactly the same drivers and updated fine. Gareth
garethEds Posted October 28, 2019 Author Posted October 28, 2019 Noticed a blog where someone had the same issue caused by the ilo channel interface driver needed updating. HI @jslate1980 - I didn't find the blog but I did find updated iLO drivers on the HPE website alongside another raft of updates. I UPdated the iLO first and upgraded to 2019. Everything went swimmingly and we now have a 2019 HyperV cluster in place. Hooray. Gareth 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now