Problem Booting my server

[Jeremy Smith_2]

When I try to boot up my server, it gets to a point where it says.

The volume group /dev/vg00 has successfully been changed.

Then the system just sits there and never moves.

Any ideas?

[Steve Bonds]

It is probably trying to activate another volume group and having problems. (i.e. timeouts, bad disks, software/driver problems, SCSI bus problems, etc.)

Boot to single user mode and check the system logs and diagnostic logs for possible errors. You can also try activating the other volume groups manually to see which one is having problems.

[Sanjay_6]

Hi Jeremy,

In all probability you have a defective disk on your hands. Try to boot the system in single user mode and see if it boots.

Interrupt the boot process. At the prompt type
bo pri
When asked wether you want to interact with IPL select "Y"
at the ipl prompt type hpux -is
IPL>hpux -is
Your system will boot into single user mode. Only / and /stand would be mounted at this point. Manually mount the other LV's, the list of which you'll get in /etc/fstab.

Now see what are the other volume groups mentioned. Try to see if you can activate the next volume group, say vg01
vgchange -a y /dev/vg01
If it does activate vg01, try to see if you can mount the Lv's for this VG manually. My guess is that one of the disks in one of these VG's is faulty.

Since you system stops after activating the VG01, my guess if the problem is with VG01. If it doesn't activate the VG, try to see if you can activate the VG without all its disks (without quorum), i think the command is
vgchange -a y -q n /dev/vg01.
if it activates the volume group, see if you can do a sync on that.
vgsync /dev/vg01. If there is any problem related to this VG, it will tell you at this time.

What is the model of your system and the OS ver ?.

Hope this helps.

Thanks

[Michael Tully]

Hi,

Boot the system into single user mode or with
LVM turned off, as
ISL> hpux -lm (booting with no LVM)
ISL> hpux -is (single user)

Consult your /var/adm/syslog/syslog.log file
for any hardware errors and /var/opt/resmon/log/event.log
if you have EMS monitoring. If the problem lies
within your volume groups, start with the first one, which has the next lowest minor number.

One thing you could try is to de-activate your
other volume groups by using the
'vgchange -a n /dev/vgname' command
Once the volume groups are de-activated you
should be to tell if the problem exists here.


HTH
-Michael

[Animesh Chakraborty]

Hi,
After booting in single user mode,edit /etc/lvmrc file and make AUTO_VG_ACTIVATE=0
then reboot and activate other vgs one by one to check which volume group is creating problem.

best of luck
Animesh

[Soren Morton]

There are also a couple of low-level (sbin/rc1.d) startup scripts that do not echo a message to the screen on startup. If you only have a vg00 then one of these scripts could also be hanging on an ioscan if a device is bad.

[Roberto Arias]

Hi:

Boot the server in single user.Then active the vg00 with this steps:

vgchange -a y vg00
mount -a

Now you have the comand that you need. Then check if the PV is failed. with this white paper. Is wrote in Spanis, sorry.