Page 1 of 1
3.0.0.9 Update failed after reboot on HyperV
Posted: 22 Mar 2016 15:56
by bryanyoung
Right after loading the DVD driver, it starts complaining about LVM and crashes.
I had this same problem with the 3.0.0.8 and just had to use a new image to get it to work.
Anybody else have this problem?

- EFA.png (35.11 KiB) Viewed 5422 times
Re: 3.0.0.9 Update failed after reboot on HyperV
Posted: 22 Mar 2016 21:07
by darky83
The system somehow can't find the mapping to the root filesystem anymore.
I upgraded about 10 hyper-v systems without any issues, so a few questions:
- Which hyper-v version are you running?
- Do you have extra cd/hdd's/floppy's added to the system, if so try to remove them.
- please check if your harddrive is added under IDE controller 0 and location 0
during the boot quickly press an key to get into the grub menu.
If you select an older kernel does it boot then?
Re: 3.0.0.9 Update failed after reboot on HyperV
Posted: 11 Apr 2016 16:22
by bryanyoung
Same thing happened when I tried to upgrade to 3.0.0.8. Ended up just rebuilding the config with a fresh install.
Now, 3.0.0.8 trying to upgrade to 3.0.0.9
It's HyperV on Windows 2012R2.
Hard drive is on IDE0, location 0.
I had an extra SCSI controller, so I removed it along with a DVD drive on IDE1. It wouldn't let me delete IDE1. Rebooted with no problem.
Did the update and rebooted for the kernel update and... kernel panic again (see attached)
Rebooted with the old kernel (2.6.32-504.16.2.el6_x86_64) and all is well.
Is it possibly related to HyperV's Linux Integration Services?
Re: 3.0.0.9 Update failed after reboot on HyperV
Posted: 11 Apr 2016 17:44
by bryanyoung
It looks like Linux Integration Services was the problem.
Before doing the upgrade, I did
rpm -qa | grep microsoft
to get the LIS packages
and then did
rpm -e on those packages.
Then I started the upgrade script and did the reboot and got it up and running on the new kernel so I could proceed with the upgrade.
Thanks for the help.
Re: 3.0.0.9 Update failed after reboot on HyperV
Posted: 11 Apr 2016 18:57
by darky83
Ah,
Which packages had you installed?
as we don't install any specific services for hyper-v (except the one's already in the kernel), i guess you manually installed some a while back?