System panic. Keeps rebooting

[R. van Huissteden]

Hello,

Ive installed this server recently with hpux 11i and veritas. On my desk it worked fine.
After moving it to the computer room it keeps rebooting. Also in single user mode. What is the cause ande hoe do i "break this circle"?
Console output in attachement

[H.Merijn Brand (procura]

Can you boot from DVD and fsck the filesystems?

Enjoy, Have FUN! H.Merijn

[bhoopathi_1]

Hi

From the error message on the console it is clear that the problem is with the file systems

"panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????"

Try interupting the boot sequence. Enter into system maintenance mode, and run insf -e. then try doing fsck on all filesystems and mount it. If this works, then probably you can reboot the system and check if everything goes smooth.

[R. van Huissteden]

Thank you both for the quick responce. I will now go into the server room and try this.

[Eric Antunes]

Hi,

Check also those 2 threads:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1104844386841+28353475&threadId=302794

and

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1104844293649+28353475&threadId=302646

Regards,

Eric Antunes

[john korterman]

Hi,
this rather old doc describes a similar situation:
http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063229542

unfortunately, the only explantion offered is "bad root disk", so you probably have to replace it.

regards,
John K.

[H.Merijn Brand (procura]

That's why I suggested to boot from DVD

It is not unlikely that the LV is just a little bit damaged, and log-replays and/or other fsck options might be ably to fix the FS while the disk itself might still be perfectly intact

This might be very time consuming. I've once had the same on a laptop with a bad installation of Linux.

booting from a rescue disk allowed me to repair the FS, and `fix' the mount tables, so the system could be brought up again. The FS was damaged beyond that in my case, so I had to re-install some packages, but all-n-all this was still much faster that a complete reinstall of the OS from scratch

Enjoy, Have FUN! H.merijn

[Steven E. Protter]

It would appear the move did you in. Perhaps however a cable came loose during the move. A visual check for tightness and such might lead to recovery of the system without having to replace the disk and lay down the OS again.

If however the disk iteself went bad during the move you are going to have to break the circle by replacing the disk and installing the OS.

It would appear you did not complete mirroring of the OS otherwise a single disk failure would not cause this "circle"

SEP

[Sorrel G. Jakins]

You get error
WARNING: no swap device configured

if you do not have pseudo-swap enabled you will have a problem. Are you still having a problem?

[R. van Huissteden]

Procura:
Ive managed to boot from the alt bootpath.
Now i have to find out how to check the prim disk. Suggestions are welcome.
Boophati:
I did not manege to get into mainiainace mode. Do you mean the ISL prompt?
Sorrel:
How do i check this?

[Stephen Keane]

"panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????"

This indicates that the one of the following apply:

1) your autoboot file is wrong. It should not contain a H/W path unless you are doing something unusual. Unless you had external disks and plugged them in in a different order, this is unlikely.

2) the /stand/rootconf files has old contents, unlikely as you have merely moved the server.

3) Corrupt BDRA.

4) Missing /dev/console (only applies to 10.20 with JFS for root filesystem)

5) Root filesystem is corrupted beyond repair

6) Missing drivers (bad/corrupted kernel)

I suspect a cable/SCSI terminator is loose. If you have managed to boot from the secondary boot path, can you check the syslog for SCSI errors? Can you see the primary boot disk using ioscan (or from the Information Menu when booting the system)?

[Sorrel G. Jakins]

You can look in /usr/conf/master.d/core-hpux and see if swapmem_on is set to 1.

[Sanjay_6]

Hi,

Chec kthe boot string on the primary disk,

lifcp /dev/rdsk/cxtydz:AUTO -

There /dev/dsk/cxtydz is the primary boot disk. the boot string should be,

hpux (0;)/stand/vmunix
or
hpux

If this is not the string, then can you post your lif boot string.

Hope this helps.

regds