topic Re: ignite question in Operating System - HP-UX

ignite question

Fabian Briseño — Sun, 08 May 2005 20:00:49 GMT

Hello to all.
My problem is this.
we have two identical workstations let's say box A and B, box B root account is locked and im unable to unlock it (it's in trusted mode).

here's what I have in mind, do an ignite backup of box A since it's the same hardware and software, and recover it in box B.

The questions is, would that unlock the root account in box B?

any help would be appreciated, thanks in advanced.

Re: ignite question

Isralyn Manalac_1 — Sun, 08 May 2005 20:05:21 GMT

Hi Fabian,

Have you tried logging in through the console?

Regards,

Isralyn

Re: ignite question

Fabian Briseño — Sun, 08 May 2005 20:14:17 GMT

yes I have, but it does not let me log on, we also tryed to boot in single user mode, but the boot process get stuck, FLT 100D conditional trap is displayed in the LED that is located in the front of the worstation case.

that why i was wondering if it is posible to recover from an ignite backup from box A to B

Re: ignite question

Warren_9 — Sun, 08 May 2005 20:23:55 GMT

Fabian,

This may help to unlock to root.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=595949

Re: ignite question

Bill Hassell — Sun, 08 May 2005 20:40:42 GMT

The Ignite backup saves exactly what is on the disk, so box B will be in the same state as box A. How are you booting into single user mode? Do not use shutdown 0 or init s.

Re: ignite question

Ermin Borovac — Sun, 08 May 2005 20:41:30 GMT

It sounds like your system is having hardware problems. If that's the case, Ignite restore won't help you.

Have you tried completely powering off your system and then powering it back on?

You'll probably need to log a hardware call with HP to get this fixed.

Re: ignite question

Fabian Briseño — Sun, 08 May 2005 21:01:51 GMT

i used shutdown -r, but as soon as its about to enter ISL it frezzes.

Yes i also think we have a HW problem but the system is fine and functioning, it just doesnt let me in single user mode

Re: ignite question

Steven E. Protter — Sun, 08 May 2005 21:53:29 GMT

You have to fix the hardware problem prior to the Ignite Tranfer/replication. Ignite doesn't do well unless all hardware is present and accounted for like it was when the make_tape_recovery was made.

Golden Images are a bit more flexible.

After fixing the hardware issues, you should be able to boot single user mode.

SEP

Re: ignite question

Mark Nieuwboer — Mon, 09 May 2005 00:55:49 GMT

It sure sounds like a hardware problem.
You have to make a call by HP for this problem.

grtz. Mark

Re: ignite question

Fabian Briseño — Mon, 09 May 2005 09:24:34 GMT

the strange thing is, if you do a normal shutdown -r the system reboots ok, but if you try to reboot in single user mode the system get's stuck.

anyway I' will try your sugestions, and i'll let you now how it turns out, thanks a lot to everyone, I will give points later on

Re: ignite question

Fabian Briseño — Mon, 09 May 2005 10:44:24 GMT

anyway, how do I make a golden image backup?

Re: ignite question

Wim Rombauts — Tue, 10 May 2005 01:52:07 GMT

It sounds strange to me that a HW defect causes a system to hang ONLY when you boot in single user mode. That would be the first time in my life !
Have you tried booting to ISL ?
If that works and a "hpux -is" gets stuck after loading the kernel, I thing this would rather be an OS issue that prevents you from booting in single user mode, and not a HW issue.
A Golden image is created the easiest with a Ignite/UX server. Otherwise, look at the manpage of commands like make_tape_recovery, make_boot_tape, make_net_recovery

Re: ignite question

Fabian Briseño — Mon, 16 May 2005 18:09:17 GMT

hello everyone.

The problem i had was that a workstation in my company had root account disabled and I was unable to unlock it, added to this was the fact that i could not enter single user mode because every time i tryed to enter single user the system got stuck.

since we have 3 similar workstations, I did and ignite on one of them and recovered it on the troubled machine, after I recovered the backup (ignite), i changed the system name, ip address, etc, etc. I pluged it back to the network and like magic everything worked again like new.

I hope this information helps someone out there, thanks a lot to everyone for their support.