Ignite error recovery

[fmndata]

Hi,

When i'm trying to make ignite recovery it shows the following error:

WARNING: send_smapi_command: smapi_send_and_wait failed, got: CONTINUE
ERROR: IO action QUERY_PROCESSOR failed: got
WARNING: Could not find Q_BOOT device. Cannot determine what the boot device
was.
ERROR: Could not get io-device data (ioscan)
WARNING: send_smapi_command: smapi_send_and_wait failed, got: CONFIG_SAVE
ERROR: Could not write disk information file
NOTE: System rebooting

[skt_skt]

Are you running make_tape_recovery or make_net_recovery?

[fmndata]

make_net_recovery

[Tricia Sambrano]

I got the same thing.

What hardware are you on and what version of Ignite did you use?
I am on an (HPUX 11.23) rx6600 with Ignite 7.2.94.

[fmndata]

HP 11.23 rx2620
Ignite-UX-11-23 C.7.1.93

[Tricia Sambrano]

I just did a double check and I am also at 7.1.93.

I thought it might have to do with the SAS disks but I don't think the rx2620 have them. So I am back to... maybe a bug. The 7.2 version of Ignite is out on software.hp.com. I may give that a shot. I will let you know if I get better results.

[fmndata]

I must also install it single in the client or in the server also.

[Saurav_1]

Hello,

Are you booting your rx26xx server from DVD and pointing to your Ignite Server for Ignite Image?

If yes then check the version of ignite on DVD and the version on Master Server, they are different.

Maintain Same version everywhere whether it is DVD, Master, Client. Don't just simply upgrade the Ignite/UX as it is available on HP's Website. DVDs play an important role in restoration on itanium boxes.

Old version of Ignite is available on the Application DVDs those came with the OS.

Thanks

[fmndata]

It can influence that the file /opt/ignite/boot/AUTO this forming like PA

[Tricia Sambrano]

I understand what you are saying about maintaining IgniteUX versions with the DVD version if you are booting to the DVD first. It's a good thing to keep in mind.

In my case though, I am booting from the Ignite tape and getting the same error as fmndata. I'm thinking it is either a SAS firmware/driver issue or a bug.

Sadly, I had to turn over the box to our DBAs so I won't be able to try anything new for a while.