01-10-2013
It seems that device paths were messed up, so did following.
Quote:
mv /etc/vx/array.info /etc/vx/array.info.old
mv /etc/vx/disk.info /etc/vx/disk.info.old
rm /dev/vx/dmp/*
rm /dev/vx/rdmp/*
vxconfigd -k
And that panicked my production box :-( Fortunately it was in cluster so my life was saved. After reboot, new lun was visible in VxVM as well.
10 More Discussions You Might Find Interesting
1. Solaris
All solaris rescue gurus out there ....
I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory.
The machine is (was) running Vxvm with the root volume encapsulated.
I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies
2. UNIX for Advanced & Expert Users
hi,
i have a volume on a LUN of an EMC-storage and i need to increase the
size.
i could increase the size of the LUN on the EMC, i could increase the
size of the disk for solaris, but how can i tell the veritas volume
manager that the disk is larger now?
what i've done:
1. LUN on EMC
2.... (3 Replies)
Discussion started by: pressy
3 Replies
3. Solaris
VxVM:
How to add one more disk into v08 the stripe should change from 7/128 to 8/128
v v08 - ENABLED ACTIVE 8954292224 SELECT v08-01 fsgen
pl v08-01 v08 ENABLED ACTIVE 8954292480 STRIPE 7/128 RW
sd bkpdg35-01 v08-01 bkpdg35 17216 ... (0 Replies)
Discussion started by: geoffry
0 Replies
4. Solaris
Hi, Im getting a downtime of 4 hrs to do porting of bootdisks.
Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage.
We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies
5. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
6. Solaris
Hi All,
We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear:
WARNING: Error writing ufs log state
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies
7. Solaris
hi all,
how can we check whether vxvm is installed in our system or not in solaris?
Thanks in advance
dinu (4 Replies)
Discussion started by: dinu
4 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
10. HP-UX
Hello all,
So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'`
do
rmsf -H $i
done
I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
LEARN ABOUT HPUX
vx_emerg_start
vx_emerg_start(1M) vx_emerg_start(1M)
NAME
vx_emerg_start - start Veritas Volume Manager from recovery media
SYNOPSIS
vx_emerg_start [-m] [-r root_daname] hostname
DESCRIPTION
The vx_emerg_start utility can be used to start Veritas Volume Manager (VxVM) when a system is booted from alternate media, or when a sys-
tem has been booted into Maintenance Mode Boot (MMB) mode. This allows a rootable VxVM configuration to be repaired in the event of a cat-
astrophic failure.
vx_emerg_start verifies that the /etc/vx/volboot file exists, and checks the command-line arguments against the contents of this file.
OPTIONS
-m Mounts the root file system contained on the rootvol volume after VxVM has been started. Prior to being mounted, the rootvol volume
is started and fsck is run on the root file system.
-r root_daname
Specifies the disk access name of one of the members of the root disk group that is to be imported. This option can be used to spec-
ify the appropriate root disk group when multiple generations of the same root disk group exist on the system under repair. If this
option is not specified, the desired root disk group may not be imported if multiple disk groups with the same name exist on the sys-
tem, and if one of these disk groups has a more recent timestamp.
ARGUMENTS
hostname
Specifies the system name (nodename) of the host system being repaired. This name is used to allow the desired root disk group to be
imported. It must match the name of the system being repaired, as it is unlikely to be recorded on the recovery media from which you
booted the system.
NOTES
HP-UX Maintenance Mode Boot (MMB) is intended for recovery from catastrophic failures that have prevented the target machine from booting.
If a VxVM root volume is mirrored, only one mirror is active when the system is in MMB mode. Any writes that are made to the root file sys-
tem in this mode can corrupt this file system when both mirrors are subsequently configured.
The vx_emerg_start script allows VxVM to be started while a system is in MMB mode, and marks the non-boot mirror plexes as stale. This
prevents corruption of the root volume or file system by forcing a subsequent recovery from the boot mirror to the non-boot mirrors to take
place.
USAGE
After VxVM has been started, various recovery options can be performed depending on the nature of the problem. It is recommended that you
use the vxprint command to determine the state of the configuration.
One common problem is when all the plexes of the root disk are stale as shown in the following sample output from vxprint:
v rootvol root DISABLED 393216 - ACTIVE -
pl rootvol-01 rootvol DISABLED 393216 - STALE -
sd rootdisk01-02 rootvol-01 ENABLED 393216 0 - -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
sd rootdisk02-02 rootvol-02 ENABLED 393216 0 - -
In this case, the volume can usually be repaired by using the vxvol command as shown here:
vxvol -g 4.1ROOT -f start rootvol
If the volume is mirrored, it is put in read-write-back recovery mode. As the command is run in the foreground, it does not exit until the
recovery is complete. It is then recommended that you run fsck on the root file system, and mount it, before attempting to reboot the sys-
tem:
fsck -F vxfs -o full /dev/vx/rdsk/4.1ROOT/rootvol
mkdir /tmp_mnt
mount -F vxfs /dev/vx/dsk/4.1ROOT/rootvol /tmp_mnt
SEE ALSO
fsck(1M), mkdir(1M), mount(1M), vxintro(1M), vxprint(1M), vxvol(1M)
VxVM 5.0.31.1 24 Mar 2008 vx_emerg_start(1M)