System booting problem

[Sumit Ghosal]

Hi All,

I have a ia64 rx4640 hp server, the system hangs up during booting with the following message -

Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Starting the STREAMS daemons-phase 1

I tried booting in single user mode , but it hangs with the same message . can anybody help me ???

Thanks,
Sumit

[Steven E. Protter]

Shalom,

Seems you have a bad system disk. If its mirrored, try booting off the alternate. If not or the mirror is corrupt, find your latest Ignite make_tape_recovery or make_net_recovery and prepare to recover the system.

SEP

[Torsten.]

Was the system running before?
It could be a wrong console setting (input/output devices) in the MP configuration.

[Sumit Ghosal]

hi Torsten,

The system was working fine earlier. but it got hanged after rebooting. I dont see any wrong console setting in MP

Thanks
Sumit

[Torsten.]

How about booting from the alternate disk? Does it work? (you have to use the "-lq" parameter probably).

[Sumit Ghosal]

I reinstalled the OS in 2nd disk . the system is up now , but i wanna know what caused the problem. both the Hard disks are ok . its not a disk problem as suggested by Steven. any suggestions for the cause of problem ??

[Torsten.]

You should review the MP system logs for error entries.

MP>SL

[Torsten.]

But it could be really related to the disk (or disk controller), because the next step should be this:


...
Starting the STREAMS daemons-phase 1

Checking root file system.
file system is clean - log replay is not required
Root check done.

...

[Sumit Ghosal]

I can mount the disk which was causing problem and access the data , so how to confirm that the disk was having problem ??

[Torsten.]

Hm, there won't be logs on the disk, because the OS was not loaded. There could be logs in the MP system logs, but I guess there was not enough time for a timeout.

Simply try to run the "dd" command to ensure your disk is good as a first step.

BTW, what firmware is on this box?

MP:CM>sysrev

[Sumit Ghosal]

dd is working fine. Is this a problem related to OS ??

Current firmware revisions of the system -

MP FW : E.02.29
BMC FW : 02.37
EFI FW : 02.10
System FW : 02.13

[Torsten.]

Without information nobody can say where the problem was.

Many activities while booting are related to the systems firmware and your firmware is not new.

It's up to you, but I would consider to upgrade first. Look at this link:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=88837&swItem=ux-38905-1&prodNameId=346361&swEnvOID=54&swLang=13&taskId=135&mode=3

And how about the MP logs?

[Makesh Annamalai]

Hi All,

I do have the same issue in rx2620. Is there any solution for this?

[Rod White]

Hi

I had a similar type of hang on a B132L workstation where the root filesystem lvol3 was vxfs.

After the streams message the replay intent log message appears and the system waits indefinitely at this point (like no timeout).

I took the disk to another machine and imported the VG then fsck'd each lvol until all but the lvol3 was clean.

I ran fsck -F vxfs -o full,nolog -Y /dev//lvol3

this runs and pass0 to pass4 are OK, then "au 0 state file" is fixed then

the command then waits indefinitely on "OK to clear Log ?"

(for a 200 meg 1vol3 it has been running now for over an hour and the disk is not showing activity from this command).

I assume I have a physical corruption in the intent log of the root filesystem which FSCK cannot handle (ie, read or clear when corrupt) resulting in some type of loop.

Since the lvol that was corrupted was the root filesystem lvol3, then the system cannot boot (however data can be recovered via the manual mount on another system).

Without being able to clear the intent log I guess I'll have to either

A) wipe the VG and start over on the entire disk (instant ignition) and then restore or
B) delete the lvol3 on the mounted disk, recreate it then mkboot the lvol

can anyone tell me if B) will work when I am managing the boot filesystems on a disk under a seperate hpux OS (sort of operate on an external disk's layout for an operating system that will be run from that disk but operating under the OS which is not on that disk)

Rod

[Rod White]

Guys

before anyone worries about the my last questions I found a solution.

Since it was a timeout issue I changed the timeout value for the lvol3

lvchange -t 60 /dev//lvol3

I then ran

fsck -F vxfs -o full,nolog -y /dev//lvol3

and the fsck ran to completion in less than 2 seconds. I had expected the timeout of the intent log clear to make the process run for 60 seconds at least so it appears that the issue was the fact that no timeout had been set for the lvol3.

I've put the disk back into the workstation and the OS boots fine.

Rod