rp2470 ignite restore problem

[Mikikiki]

Hi all,

We have hp rp2470 server running hp-ux 11.00, with LVM mirroring. As for redundancy we have second rp2470 same hw (same two processors, same ram, same two hdd’s, same number of lan cards).

I want to clone first one to the second. For that purpose I am making ignite tape with the following command: make_tape_recovery -x inc_entire=vg00

Ignite tape finishes without problems. When I boot second server from this ignate tape, server is starting to boot, and ignite restore finishes without any errors, only few notes, which are normal.

However vmunix is not booting and when restore finishes, it boot to ISL> prompt.

From this I cannot boot /stand/vmunix.

I tried to run recovery shell but no success. When recovery shell ask to do frecover to restore critical files, then I receive error: frecover(5405): unable to open /dev/rmt/0m

I will appreciate any help.

Regards,

[Henry Fauni]

Attempt to create another make_tape_recovery archive with -I (interactive) option:

# make_tape_recovery -I -x inc_entire=vg00

This will force you to interact when you do the recovery on the other system.

Modify hostname, IP address, LVM filesystem size per your needs.

Although you mentioned everything is identical, when you do the recovery, go in to the "Basic" tab, and under "Additional", select "cloning to different HW?" (Set it to true). The system will generate a new kernel from the /stand/system file that was created from the archive, and not simply use what was on /stand/vmunix.

[Mikikiki]

Hello Henry,

Thank you for your reply.

Can you be more specific when you mention: "go in to the "Basic" tab, and under "Additional", select "cloning to different HW?" (Set it to true). "

Where I can find this basic and additional tabs? Will I have that option after when using "I" option when creating the archive tape?

Br,

[Torsten.]

>> From this I cannot boot /stand/vmunix

Any error messages?

[Mikikiki]

Hi torsten,

I can find any error.

Please find part of the restore log attached.

If you need additional info please say.

Br, 

[Torsten.]

Did you start "hpux" from there?

[Mikikiki]

I tried but no success.

All the time when I put hpux it wait for a few seconds and again goes to ISL> prompt.

I also tried hpux with -q and -lq because production server uses lvm mirroring but again same isl prompt.

Br,

[Torsten.]

Please do

ISL> hpux ls -l

to list the files in /stand.

[Mikikiki]

Hi Torsten,

I tried with command you suggested, but again nothing to display.

This is output:

ISL> hpux ls -l

ISL>

Do  you have anything in mind why this is happening?

Br,

[Torsten.]

Hmmm, I would try with a newer firmware: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=2511789&swItem=PF-CHAW4350&prodNameId=86730&swEnvOID=7&swLang=13&taskId=135&mode=4&idx=0

[Mikikiki]

Hi,

Newer firmware on the production server is not an option.  It is business critical server so I can not play so much with it.

Is it maybe possible to start recovery shell to try to rebuild kernel or critical files?

If so, I will need help to do this, because as I mentioned I already tried but couldn't find helpful manual for this.

Br,

[Torsten.]

What is the firmware of the other server? Well, this "new" version is from 2006 - so there is no risk!

There are many boot related fixes between your version and the current version.

[Mikikiki]

Hi Torsten,

I can't do any restarts on the production server.

Firmware Revision C.02.14 Apr 14 2003, this is on production server.

Br,

[Torsten.]

This is the revision of the GSP, not the server. Run STM to get the PDC version, e.g.:

# echo "sel dev all;info;wait;il"|cstm|grep -i pdc

[Dennis Handly]

>Newer firmware on the production server is not an option.

Not even on the broken server, the one you are trying to restore?

[Mikikiki]

Hello,

On the second server ofcourse I can do firmware upgrade because it is not usable at this moment. But I think it has newer fw version. From boot log I could see this: Firmware Version  42.19.

[Mikikiki]

Hi Torsten,

fw version of production server is: Firmware Version  43.50

and fw version of backup server is: Firmware Version  42.19

so probably my production server has newer firmware. I can do fw upgrade on  backup. I will see if I can do it from this point from gsp or from isl and come back then.

Br,

[Henry Fauni]

---

@Mikikiki wrote:

Hello Henry,

Thank you for your reply.

Can you be more specific when you mention: "go in to the "Basic" tab, and under "Additional", select "cloning to different HW?" (Set it to true). "

Where I can find this basic and additional tabs? Will I have that option after when using "I" option when creating the archive tape?

Br,

 Yes, after you create the archive with the -I option, and then when you boot from the tape, you will see the Menu with all the tabs I was referring to.

---

[Mikikiki]

Henry,

thank you for your reply.

I will try first fw upgrade because there is fw difference between those two servers and after that try restore with -I flag.

After that I will send you feedback.

Best regards,

[Mikikiki]

Dear All

I did fw upgrade so now both servers have fw version 43.50. After this I tried recovery but again cant boot the system.

Next I did archive tape with -I flag as Henry suggested, and tried recovery with it, again no good.

I cannot find any error or warnings on ignite log, but cannot boot hpux. I am only on ISL> prompt.

However on gsp log I noticed this:

************* SYSTEM ALERT **************
SYSTEM NAME: mcnfwim1
DATE: 07/27/2003 TIME: 10:18:49
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O
SOURCE DETAIL: 6 = disk SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH OFF ON ON ON
LED State: Boot Failed. Running non-OS code.
Check Chassis and Console Logs for error messages.

0x00000060860010B0 00000000 00000000 - type 0 = Data Field Unused
0x58000860860010B0 00006706 1B0A1231 - type 11 = Timestamp 07/27/2003 10:18:49

Can this be the root of a problem?

Any help is appreciated.

Br,

[Mikikiki]

Another gsp log:

Log Entry #   3 :
SYSTEM NAME: mcnfwim1
DATE: 07/27/2003 TIME: 10:12:20
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 8 = I/O
SOURCE DETAIL: 6 = disk   SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 1 = test   STATUS: 0
CALLER SUBACTIVITY: 0B = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00

0x00000060860010B0 00000000 00000000 type  0 = Data Field Unused
0x58000860860010B0 00006706 1B0A0C14 type 11 = Timestamp 07/27/2003 10:12:20
Type CR for next entry, - CR for previous entry, Q CR to quit.

Thank you in advance,

[spirit986]

I was examining this thread and your other thread here: http://h30499.www3.hp.com/t5/Ignite-UX/Can-t-boot-after-ignite-recovery-ALERT-LEVEL-6-Boot-possible/m-p/5397031#M23688

What you said in the second thread was: "From cold instaled server I did recovery tape with the same command and it is working perfectly. But when I try to clone the production server it is not working."

This is just a hinch that poped in my head and i think that there may be something that is interupting  the creation of the ignite tape on the production server.

[Mikikiki]

Hi,

Thank you for your reply.

Ignite log from creation recovery tape is same on production and on second server. I  can not find any errors.

The only problem and error I can see is from gsp log, but as I mentioned cold install and ignite recovery from the same server is working.

Is maybe lvm mirroring causing some problem? I don't know now, and I am only guessing what could be the problem.

The only think I can come up now is, run recovery shell, but as I mentioned I have no proper manual on how to do that.

If anybody else have something in mind I can test everything in this situation.

Br,

[Henry Fauni]

During the recovery, were you able to get to the menu and tried the "cloning to different HW?"= TRUE option?

[Mikikiki]

Hi Henry,

Yes I was able to go to advanced meny you sugested and change: cloning to different HW?"= TRUE option.

And again, whole ignite is going and when last reboot is executed it is not booting from the hdd which is primary path but goes to isl? prompt.

Any idea?

Br,