Hyper-V FOM install problems (2562 Views)
Reply
Occasional Visitor
Tenus
Posts: 3
Registered: ‎03-19-2013
Message 1 of 12 (2,562 Views)

Hyper-V FOM install problems

Hi,

 

I have try FOM install to hyper-v a month with no success. First I extracted hvsa_original.vhd from HP_P4000_Failover_Manager_FOM_for_HYPER-V_BM480-10513.exe, coz installer didin't work.

 

I have created new Virtual machine from hvsa_original.vhd, only way it reboots is when it's IDE disk.

When trying to make it SCSI disk, it gives 'Boot failure. Reboot and Select proper Boot device'.

 

Linux boot prompt default saniq will give me a error mount: could not find file system '/dev/root' And hangs to Kernel panic. There's also 'test' command at linux boot prompt, what allows me to boot with success. And then CMC find's it, but it's old version 9.5.00.1215 and don't allow me to add it to exist managment group. When trying to upgrade FOM with cmc, it fails. And upgrade log I found error:

 

**ERROR**: root filesystem [/dev/ide/host0/bus0/target0/lun0/part5

/dev/hda5] is not regonized partition. Upgrade cannot proceed. Recognized OS partitions are:

[/dev/hda5]  [/dev/hda9]

umount: /mnt/upgraded/proc: not found

umount: /mnt/upgraded/dev: not found

umount: /mnt/upgraded: not found

 

I have try to apply hvsa_original and config.vhd to scsi controller location 0,1,2,3,4 with no success. Only way it boots is when hvsa_original.vhd is in ide controller 0.

 

Is there way to get to the unix shell to look where is trying to mount root device with saniq boot? 

 

Anyone have failover manager with hyper-v work? And if it, how they do it?

Valued Contributor
Dirk Trilsbeek
Posts: 62
Registered: ‎01-18-2010
Message 2 of 12 (2,546 Views)

Re: Hyper-V FOM install problems

we have, but we just used the installer. The installer is a bit quirky though, at least the one from version 9.5 was unable to put together the correct path and file name for the hyper-v files when the path for the hyper-v machines configured in hyper-v manager had a backslash at the end.

 

For instance:

D:\Hyper-V\Machines\   <- this didn't work (at least not with the installer from 9.5 on a Win 2008 R2 system)

D:\Hyper-VMachines  <- this did work

 

Occasional Visitor
Tenus
Posts: 3
Registered: ‎03-19-2013
Message 3 of 12 (2,542 Views)

Re: Hyper-V FOM install problems

[ Edited ]

I try installer to c:\hyperv folder, but it seems to create VM with name 2060f387-4f5a-464c-9515-419404489707.

Then it starts the vm, and installer hangs 'Waiting for VM to shutdown...' When looked the vm window, theres Kernel Panic.

 

We using 2012 servers as hyper-v hosts.

 

 

I can get it up with typing 'test' again in linux boot prompt, but when trying to update it from cmc, it gives following error:

 

Installation failed. An error was encountered with the configuration, RAID, or parts. (Exit Status 171)

 

And heres the log from cmc, the error in FOM is exactly same as before (not detecting the root drive):

 

Installation process started on: 19.3.2013 12:19

Name field from Package: C:\Program Files\HP\P4000\UI\downloads\10054-07.20130131.patch

Name field from Package: C:\Program Files\HP\P4000\UI\downloads\SANiQ_10.5.00.0149_20130207_legacy.upgrade

Name field from Package: C:\Program Files\HP\P4000\UI\downloads\10054-07.20130131.patch

Name field from Package: C:\Program Files\HP\P4000\UI\downloads\10147-00.20130212.patch

Performance Instrumentation -- Upgrade: --NSM Configuration--

Performance Instrumentation -- Upgrade: Number of NSMs: 1

Performance Instrumentation -- Upgrade: NSM Model Name: P4000 VSA (Hyper-V)

Performance Instrumentation -- Upgrade: NSM Software Version: 9.5.00.1215.0

Performance Instrumentation -- Upgrade: NSM Host Name: saniqfom

Performance Instrumentation -- Upgrade: NSM IP Address: 10.23.230.243

Performance Instrumentation -- Upgrade: NSM Serial Number: 00:15:5D:82:F2:00

Performance Instrumentation -- Upgrade: --End Of NSM Configuration--

/10.23.230.243:11120: connectToServer received a Status message from the install server running on the node It was: 'OK', and the error flag was: false

Online Upgrade: preparing for post-qualification analysis.

Completed post-qualification test analysis.

/10.23.230.243:11120: sendPackageToServer received a Status message from the install server running on the node It was: 'OK', and the error flag was: false

/10.23.230.243:11120: Received an UpgradeServerStatus message from the install server running on the node It was : Heart beat to the client...only stage of one stage package

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Extracting the install file ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Preparing for installation of patch 10054-07 ... (Tue Mar 19 10:19:53 GMT 2013)

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Current SAN/iQ version is 9.5.00.1215

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Begin installing new software modules

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Finished installing new software modules

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Patch 10054-07 has been successfully installed.

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Wrote /mnt/lhnupgrade/10054-07.xml to /etc/lefthand/patches/

/10.23.230.243:11120: Received an UpgradeFinished message from the install server running on the node It was : Completed installation 3.

/10.23.230.243:11120: Done listening for messages from the upgrade server.

Online Upgrade: preparing for post-qualification analysis.

Completed post-qualification test analysis.

/10.23.230.243:11120: connectToServer received a Status message from the install server running on the node It was: 'OK', and the error flag was: false

/10.23.230.243:11120: sendPackageToServer received a Status message from the install server running on the node It was: 'OK', and the error flag was: false

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Extracting the install file ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Extracting package contents ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : MESG: Configuring platform specific settings ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Configuring platform specific settings ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : HWID: 252

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : HWID Model: P4000

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : HWID Config: VMNSM

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Brand Directory: /etc/lefthand/brand/VMNSM/

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : platform configuration: '/mnt/lhnupgrade/platforms/HVNSM.sh' ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Starting software upgrade ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Current Software Version: 9.5.00.1215

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : New Software Version: 10.5.00.0149

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Checking storage node ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : begin MAIN install_saniq.sh: Preparing for upgrade ...

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : This is a virtual platform where LEGACY_VIRTUAL_UPGRADES=true (in common.sh)

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Aborting due to an error encountered during installation of the software upgrade.

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Contact Customer Support to resolve the issue.

/10.23.230.243:11120: Received an UpgradeScriptStatus message from the install server running on the node It was : Installation aborted.

/10.23.230.243:11120: Received an UpgradeServerStatus message from the install server running on the node It was : INSTALL_STATUS_MESSAGE: done [171]

 

 

Honored Contributor
oikjn
Posts: 797
Registered: ‎07-20-2011
Message 4 of 12 (2,533 Views)

Re: Hyper-V FOM install problems

your problem is 9.5 doesn't support windows 2012.  You need to upgrade to the latest VSA software... 10.5

Occasional Visitor
Tenus
Posts: 3
Registered: ‎03-19-2013
Message 5 of 12 (2,516 Views)

Re: Hyper-V FOM install problems

I found updated HP_StoreVirtual_Failover_Manager_FOM_for_Hyper-V_BM480-10535.exe

That seems to be version 10.0.00.1896, same as my storage systems.

 

Everything went good, until I try to add it to managment group, it gives error in CMC: 

 

Storage system TESTFOM (10.23.230.29) did not join the management group TESTMG1.

The required directory /etc/lefthand/data is not mounted. Please restore OS using recovery media.

 

So what I can try next?

 

Honored Contributor
oikjn
Posts: 797
Registered: ‎07-20-2011
Message 6 of 12 (2,509 Views)

Re: Hyper-V FOM install problems

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=StoreVirtualSW

 

I believe the current version is HP StoreVirtual Failover Manager FOM for Hyper-V (BM480-10543.exe). 

 

Try deleting the current FOM, delete the total directory and then try installing it again.  I've done it a dozen times without issue. 

Occasional Advisor
JohD
Posts: 6
Registered: ‎09-13-2011
Message 7 of 12 (1,980 Views)

Re: Hyper-V FOM install problems

Hi,

 

Don't know if you solved your issue but I got the same.

I reinstalled the FOM like a hundred times and still got the same error.

I finally managed to add the FOM to my mgmt group by restoring the FOM through Config Management ==> Reset to the Default Settings

It rebooted the FOM, I entered again my network settings and went to CMC to add it to my mgmt group.

 

Peace

 

 

HP Pro
Prakash Singh_1
Posts: 194
Registered: ‎11-25-2010
Message 8 of 12 (1,956 Views)

Re: Hyper-V FOM install problems

Hi,

 

For StoreVirtual/P4000 SAN solutions querries you can also visit the HP Guided troubleshooting tree.

 

Below is the link for HPGT:

http://h20180.www2.hp.com/apps/Nav?h_pagetype=s-905&h_lang=en&h_cc=us&h_product=304617&h_audience=sm...

 

I work for HP

Regards,

PS
To assign points on this post? Click the white Thumbs up below!
Visitor
beigewell
Posts: 3
Registered: ‎01-16-2013
Message 9 of 12 (1,894 Views)

Re: Hyper-V FOM install problems

having the same issues as everyone else, am running the very latest FOM installer and using Server 2012 Hyper-V. I can see the second vhd isnt loaded and have the error below when running diagnostics from the CMC

Honored Contributor
oikjn
Posts: 797
Registered: ‎07-20-2011
Message 10 of 12 (1,889 Views)

Re: Hyper-V FOM install problems

sounds like the installation didn't complete for some reason.  The fact that you can get into that screen in CMC says that at least basic functionality of the FOM is working.  You can try initilizing the disk and rebooting the FOM and it might fix itself or simply remove the FOM, delete it and re-install it.

Visitor
MarkU
Posts: 4
Registered: ‎09-07-2011
Message 11 of 12 (1,724 Views)

Re: Hyper-V FOM install problems

Many thanks - this worked for me. Great advice.

Mark

Regular Visitor
RajaS
Posts: 4
Registered: ‎11-05-2009
Message 12 of 12 (1,184 Views)

Re: Hyper-V FOM install problems

I also got the error drive 1 uninitialized on hardware information tab of the FOM. Issue is solved after connecting to FOM and Config Management => reset option.
-Thanks for JohD
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.