06-06-2013 08:04 AM
Hi Support
We have a two node VCS cluster,one node is down & not able to boot,we locally up the cluster in the other node. The node which is not booting up giving the following errors,I have mentioned the last few lines only.OS is solaris9,platform is SF4900.
=============================================================
Rebooting with command: boot -s
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
hba0: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
hba0: Firmware v3.3.12 (ipx)
QLogic Fibre Channel Driver v4.20 Instance: 1
hba1: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
hba1: Firmware v3.3.12 (ipx)
Hardware watchdog enabled
VxVM sysboot INFO V-5-2-3390 Starting restore daemon...
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
VxVM vxconfigd ERROR V-5-1-0 Segmentation violation
/etc/rcS.d/S25vxvm-sysboot: egettxt: not found
VxVM sysboot NOTICE V-5-2-3388 Halting system...
syncing file systems... done
NOTICE:
==========================================================
with thanks & regards
Arup
Solved! Go to Solution.
06-08-2013 08:51 PM
Hi stinsong/rsharma1 Thanks for your inputs.
Would like to inform that the issue got resolved,yes the problem was a severe one,there was lot of playing with /etc/vfstab & /etc/system by the customer which were not known to us. After booting from the cdrom with single user mode,all are rectified & now the system working fine.
regards...Arup
06-07-2013 01:42 AM
could you login to the system and disable boot-time startup for the complete stack?
from the error above, i feel the VxVM is failing, and not VCS. So if you are able to login, then please start the following services
/etc/init.d/llt start
/etc/init.d/gab start
/etc/init.d/vcs start
provide output of the 'gabconfig -a' and 'hasys -state'
06-07-2013 02:00 AM
Hi arangari
Thanks for your input,we cannot be able to login to the system at all,as system is rebooting giving the above error.
regards....Arup
06-07-2013 03:25 AM
is the boot disk under vxvm? can you boot into fialsafe mode from ok prompt? [ok boot -F failsafe]
06-08-2013 08:42 PM
Hi ARUP,
The boot volume should be encapsulated by VxVM which failed at the header of the volume.
It's a little severe problem. You need to unencapsulate the rootdg volumes and make it boot. Then re-encapsulate rootdg.
The steps you could find in public web by searching for unencapsulate VxVM rootdg.
06-08-2013 08:51 PM
Hi stinsong/rsharma1 Thanks for your inputs.
Would like to inform that the issue got resolved,yes the problem was a severe one,there was lot of playing with /etc/vfstab & /etc/system by the customer which were not known to us. After booting from the cdrom with single user mode,all are rectified & now the system working fine.
regards...Arup