cancel
Showing results for 
Search instead for 
Did you mean: 

boot up issue

SOLVED
Go to solution
Jonathan Grymes
Frequent Advisor

boot up issue

I have an HP rx2620  running 11.31. It had a disk failure, vg02. We have replaced the disk but its not initialized/configured yet. I cant get the server to complete boot up.

 

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" is already active on this system.
Activated volume group.
Volume group "/dev/vg01" has been successfully changed.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c3t2d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Couldn't activate volume group "/dev/vg02":
Quorum not present, or some physical volume(s) are missing.

vgchange: Warning: couldn't query physical volume "/dev/dsk/c3t2d0":
The volume group is not activated
vgchange: Warning: couldn't query the list of physical volumes.
Checking vxfs file systems
UX:vxfs fsck: INFO: V-3-20913: /dev/vg00/lvol3:sanity check: root file system OK (mounted read/write)
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol4:sanity check: /dev/vg00/lvol4 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol5:sanity check: /dev/vg00/lvol5 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol6:sanity check: /dev/vg00/lvol6 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol7:sanity check: /dev/vg00/lvol7 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol8:sanity check: /dev/vg00/lvol8 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol9:sanity check: /dev/vg00/lvol9 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol10:sanity check: /dev/vg00/lvol10 OK

UX:vxfs fsck: WARNING: V-3-20916: /dev/vg00/mqcode:sanity check: /dev/vg00/mqcode needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oradata01:sanity check: /dev/vg01/oradata01 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oradata02:sanity check: /dev/vg01/oradata02 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oralogs01:sanity check: /dev/vg01/oralogs01 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oralogs02:sanity check: /dev/vg01/oralogs02 needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oraundo:sanity check: /dev/vg01/oraundo needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oratmp:sanity check: /dev/vg01/oratmp needs checking
UX:vxfs fsck: WARNING: V-3-20916: /dev/vg01/oraexp:sanity check: /dev/vg01/oraexp needs checking

UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gexhome:sanity check failed: cannot open /dev/vg02/gexhome: No such device or address
UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gexvar:sanity check failed: cannot open /dev/vg02/gexvar: No such device or address
UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gexcurrent:sanity check failed: cannot open /dev/vg02/gexcurrent: No such device or address
UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gexarchive:sanity check failed: cannot open /dev/vg02/gexarchive: No such device or address
UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gextmp:sanity check failed: cannot open /dev/vg02/gextmp: No such device or address
UX:vxfs fsck: ERROR: V-3-25742: /dev/vg02/gexrelease:sanity check failed: cannot open /dev/vg02/gexrelease: No such device or address

 

 

Boot up is hanging here:

 

Configuring HPVM AVIO Mass Storage interfaces ..................... OK
Start Trivial File Transfer Protocol daemon in standalone mode .... N/A
Configuring HP Fibre Channel FCD Mass Storage interfaces .......... OK
Configuring HP Fibre Channel FCLP Mass Storage interfaces ......... OK
Configuring HP Fibre Channel FCOC Mass Storage interfaces ......... OK
Configuring HP Fibre Channel FCQ Mass Storage interfaces .......... OK
Starting Sophos Anti-Virus daemon ................................. OK
Starting Sophos Management Agent .................................. OK
Start NFS server subsystem ........................................ N/A
..................................................................

1 REPLY
Bill Hassell
Honored Contributor
Solution

Re: boot up issue

vg02 needs fixing.

Do you know if it is mirrored?

If it is not, you'll need to remove vg02 (vgexport) and rebuild it from your backup tape.

 

The hang at NFS means that networking is not correct. The startup scripts don't respond to CTRL-C. Use CTRL-\ to abort the NFS (and possibly other network subsystems) to finish bootup.



Bill Hassell, sysadmin