Ignite 7.1

[Tim Nelson]

Has anyone used IUX 7.1 to create a DVD image ( i.e. for use as a two step recovery )

Both my IVM test servers crash with "init died with 132" when booting from a 7.1 created ISO.

6.10.x worked fine.

Any experiences would be helpfull.

Thanks !

[Steven E. Protter]

Shalom Tim,

Knowing the OS would help.

I've also done it extensively with earlier versions of Ignite and might be able to try it out if I know the OS.

SEP

[Tim Nelson]

Sorry Steve..

Ignite server used to create DVD ISO.
11.23 IA

IVM guest used to boot the virtual DVD ISO image.

I had everything working fine when using a 6.10 version of Ignite from a PA-risc server except issues with recovery speed. I installed 7.1 Ignite on an IA server as I saw there was some issues with 11.11 PA Ignite client recoveries so I figured I would migrate my ignite server to 11.23 IA and a newer version of ignite.

[Sameer_Nirmal]

The system panic with "init died" would mean in your case as with bad OS DVD Image or problem with the DVD media. Did you verify the ISO Image ?

I don't know what 132 means and haven't worked on IG-UX 7.1 though.

Do you have same Ignite-UX version used for the tape as well?

[Tim Nelson]

I opened a call with HP and my process and procedure is correct but they have no known issues yet ( I may be the first ).

If I create an ISO image the exact same way with version 6.10 all works. If I create the image with 7.1 no luck.

I have not yet had the opportunity to create a bootable tape, I will update if I find anything.

[Al Miller_1]

Tim,

As of Ignite-UX version C.7.0, the startup sequence has changed considerably. Prior versions of Ignite-UX ran as the "init" process throught the first phase of the cold-install process. In other words, the kernel launced /sbin/init, which was special Ignite-UX code. That program essentially managed the entire first phase of the cold-install up until the first reboot.

However, beginning with C.7.0, the cold-install process is managed by the standard /sbin/init, and is driven out of a special version of /etc/inittab. Its a bit complicated -- the /sbin/init started by the kernel is in fact special Ignite code which saves some configuration information, then copies the real init into place and execs that to become a bona-fide init which parses a special /etc/inittab that executes programs which configure RAM filesystems and begin the system configuration and software load.

Without knowing the details of how you are creating your DVD image its hard to guess what might be going wrong. If you could post the 10 or 20 lines above the "init died" message from your console output there might be some clues there.

Al

[Tim Nelson]

Hey Al,

command used to create boot helper DVD ISO is
/make_media_install -r B.11.23 -m IUX-IMAGE

( also tried specifying -o IA )


Nothing special here. Taken directly from the white paper and the text with-in the make_media_install script itself.

If the vMP direct lanboot using dbprofile would work I would not have to do any of this.

Thanks for the comments.

[Tim Nelson]

Attached console log.

[Al Miller_1]

Hi Tim,

The console log you attached was most helpful. It shows that the kernel boots as normal, and the installation process has begun its internal memory configuration ("Configuring RAM filesystems...") when init exits, causing the kernel to panic. A unix kernel without an init process doesn't do anyone much good ;).

Looking at your console log, I see that your IVM has about 500 MB of RAM allocated. I believe that the minimum supported RAM amount in an Integrity VM is 1GB. If possible, I would suggest you try to allocate more memory to the VM and try again. See http://docs.hp.com/en/T2767-90024/ch03s01.html#memory_section for more information.

As I mentioned in my post yesterday, The inner workings of the Ignite-UX startup process have changed with C.7.0, and it would not surprise me that a marginal memory configuration that worked with C.6.10 and earlier may have problems in C.7.0 and beyond.

[Tim Nelson]

Good point Al,

I will create a different guest with a larger allocation.

I only had 4GB to work with on the VM Host and was creating a number of guest to test things in one manner and another and another..

I will test again today with a larger mem config and post the results.