Panic at Booting

[srinivasa rao vaddadi]

Hello Experts,

For my new server rp5470 , i have modified Some Kernel Parameters as of my old server.
But while rebooting it is rebooting continously. Could anyone help me out in this issue. it is so urgent. i'm sending the error output as attachement please check it.

[Sameer_Nirmal · Accepted solution]

Hi,

Try to boot the system using old kernel
When you see this message
To discontinue, press any key within 10 seconds.
Press a key you will get ISL prompt.
type ISL > hpux /stand/vmunix.prev

Which parameters did you change?

[Steven E. Protter]

You need to boot off the old kernel as indicated and put the old kernel back into production.

It still might not boot though.

There are other possible causes.

There could have been a hardware failure, there could be a scsi cable loose. All kinds of things may have gone wrong.

Best bet though is what you did triggered it. The kernel parameters from your old system are not necessarily what you need on your new one.

SEP

[A. Clay Stephenson]

In your case after you boot from vmunix.prev, you should save your current vmunix.prev to another file. (e.g. vmunix.safe) so that when you build another kernel you don't lose the one version that does work. You broke one of the fundamental rules of kernel tuning and changed many things at once. You could analyze your dump using q4 but you would probably find to more expedient to change one or two values at a time, gen new kernels, and boot again.

[Devender Khatana]

Hi,

Apart from parameters it seems that some drivers were also removed from kernel. Was it?

Atleast the startup message indicates that. But I had similar problem in one of my R-380 around a year back without any changes.

Has it got rectified?

HTH,
Devender

[Bharat Katkar]

Hi,
The very first JOB would be to boot from the prev kernel.
1. Halt the boot at EFI shell
2. Go to ISL prompt
3. ISL> boot /stand/last_install/vmunix
Once system boots now verify the changes you have done.

I saw following error messages in the log you have attached:

-------------------------------------
Starting the STREAMS daemons-phase 1

System Panic:

linkstamp: Sun Nov 13 05:32:00 KST 2005
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x0020afd8 0x00302f38 0x003530ac
0x00461154 0x00353b60 0x001731e4
0x001f8e64
End Of Stack
-------------------------------
Yes as already told you have lost some important drivers. I think most probably they are related with DISK/FILESYSTEM/VolumeManager.
Try to recall all activities you have carried out before rebuilding the kernel.

Hope that helps.
Regards,

[Sยภเl Kย๓คг]

Hi Srini,

Boot the server with the old kernel, as described in above posts, ie /stand/vmunix.prev. Post us the parameters which u have changed along with a kmtune o/p of the current working kernel, so that we will be in a better position to help u further.

Regards,
Sunil

[vinod_25]

Hi Srini,

I found an ALERT LEVEL 12 error in the attachment. and LED status of FAULT LED is also not OK.

solution:

break the boot process after PDC
Press CTRL B and goto GSP mode
At the GSP prompt issue AC to modify the alert configuration
GSP> AC
Current Alert Display Configuration:

Automatic Display of System Alerts: Enabled
Alert Threshold: 3
Timeout: 60 seconds.

Do you want to modify this configuration? (Y/[N]) y

Automatic Display of System Alerts: Enabled

Do you want to modify it? (Y/[N]) y

Enter new Display of System Alerts ([E]nabled / [D]isabled Permanently /[T]emporarily disabled until next boot): D

New Display of System Alerts: Disabled
Confirm? (Y/[N]): y

-> Automatic Display of System Alerts will be updated.

Current Alert Threshold: 3
Do you want to modify it? (Y/[N]) n

Current Timeout (in seconds): 60
Do you want to modify it? (Y/[N]) n

-> Settings have been updated.


GSP Host Name: c3177081


Issue CO to return to console mode.
GSP> CO

and continue the boot process.

Regards,

Vinod

[srinivasa rao vaddadi]

thanku all , i have rebooted the server with vmunix.prev - good lesson for me , next time i will take backup for the old kernel parameters.