9 More Discussions You Might Find Interesting
1. Solaris
zpool status -v
below my mirrors in Solaris 10
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c3t0d0s0 ONLINE 0 0 0
... (2 Replies)
Discussion started by: top.level
2 Replies
2. Solaris
hi am trying to get some knowledge on Solaris common trouble shooting problems..
can some one help me in getting most common issues..
and how to solve those issues.
thanks in advance (4 Replies)
Discussion started by: aravindreddy
4 Replies
3. UNIX for Dummies Questions & Answers
My current machine is a Macbook pro running Snow Leopard. I want to mess around with various *nix OSes but not in a way that threatens the current working condition of this machine. The way around this seems to be to install various operating systems on a largish flash drive, boot from that, and... (2 Replies)
Discussion started by: Zygomorph
2 Replies
4. AIX
We had a mirrored disk failed (not the rootvg), there are 3 lvs (transfer, applogs, arch) from extvg gone open/stale state.
After replaced failed disk and run cfgmgr, the new replaced disk is visible:
)
I did the following to re-mirror new disk:
# extendvg prodvg hdisk3
# lspv (got new pvid on... (2 Replies)
Discussion started by: jalite19
2 Replies
5. Solaris
Dear All,
After creating ,installing ,configuring zone in my solaris VMware .
I am not able to Ready/Boot the zone.
giving error as :
Please help me out for the same
Core part of zone.xml is as:
Anythng which I missed in configuration..
Do let me know (1 Reply)
Discussion started by: bharat_
1 Replies
6. Red Hat
Hey guys i have a machine running redhat enterprise 3.8 (i believe) and it has two hard drives that are mirrored. what would i have to do to get them to act as two seperate hard drives so i have 120gb capacity total as opposed to just 60?
also, what would i do if i just wanted to take one of... (4 Replies)
Discussion started by: pacman529
4 Replies
7. Solaris
Hi All,
I have detached a mirror and primary disk from my Solaris box.
On trying to boot from Primary disk, It boots up good.
But from my mirror disk, it is not booting and giving me the login prompt
Instead it goes to maintenance state by issuing a coredump.
Can you explain why... (9 Replies)
Discussion started by: jegaraman
9 Replies
8. UNIX for Dummies Questions & Answers
Hello experts,
I have installed solaris 10 on x86. When I try to boot I get an error
with ablue screen
login failed please try again. I am new to this o.s. It used to work
nicely before what did I do wrong?
Any guidance advice will be highly appreciated
Thanks, (5 Replies)
Discussion started by: deepak1
5 Replies
9. UNIX for Advanced & Expert Users
When i try to boot my solaris 2.6 E220R server, i get this error message
> INIT: cannot create /var/adm/utmp or /var/adm/utmpx
>INIT: failed write of utmpx entry:" "
>INIT: failed write of utmpx entry:" "
INIT Single User Mode
Press Ctrl-d for normal boot process or enter roots password... (10 Replies)
Discussion started by: lealyz
10 Replies
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)