10 More Discussions You Might Find Interesting
1. Solaris
i booted into maintenance mode
boot -- -s
from the console
I got the
Root password for system maintenance (control-d to bypass)
I did control -d
and then logged in
it told me that I was booting into boot -s
but after I did a control -d and logged in
who -r shows
... (9 Replies)
Discussion started by: goya
9 Replies
2. Solaris
:confused:
when i tried to look the status of DNS-client, it is in maintenance mode.....
Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE...
:wall: (2 Replies)
Discussion started by: vamshigvk475
2 Replies
3. Solaris
I have seen similar threads on this issue, but I have not seen a fix. Basically I am getting a lot of rcp bind errors. Below find the output of "svcs -xv". not sure where to begin:
# svcs -xv
svc:/network/rpc/bind:default (RPC bindings)
State: maintenance since Fri May 25 14:13:18 2012... (14 Replies)
Discussion started by: brownwrap
14 Replies
4. Solaris
Hi Guys,
I have a sunblade 1500. I booted the system and it booted to maintenance mode. How can I fix this?
Thanks lots (8 Replies)
Discussion started by: cjashu
8 Replies
5. Solaris
Hi Guys,
Virtual Machine - Solaris 10 ssh service is in maintenance mode, when i tried to disable it it got disabled but when i enabling it ( svcadm enable ssh) it is coming in maintenance mode......
Pls help (10 Replies)
Discussion started by: saurabh84g
10 Replies
6. Solaris
I have a Solaris 10 SunFire v880 machine and I'm having trouble with Samba.
Samba has worked on this machine but since the machine has been re-booted Samba has not worked.
Machine details are:
cat /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008... (2 Replies)
Discussion started by: KenLynch
2 Replies
7. Solaris
Hi,
I have installed Hudson on a Solaris 11 server, using the installation instructions available at Paul Oswald: Hudson Solaris SMF Manifest.
When I perform svcs -l hudson, I get:
fmri svc:/application/hudson:default
name Hudson Continuous Build Server
enabled true... (4 Replies)
Discussion started by: JVerstry
4 Replies
8. Solaris
Hello All,
On solaris 10 server i could see the FTP service is in maintenance mode always :mad:
Could some assist?
svcs -xv
svc:/network/nfs/nlockmgr:default (NFS lock manager)
State: maintenance since Tue 28 Jul 2009 11:47:55 AM BST
Reason: Restarting too quickly.
See: Sun... (5 Replies)
Discussion started by: bullz26
5 Replies
9. Solaris
I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode.
I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
Discussion started by: cheetobandito
9 Replies
10. HP-UX
hi,
i figured why i need to boot in MMB,some of which are missing or corrupt LABEL (LIF labeL ,i guess) on the boot disk.
To explicitly corrupt this entry i think a simple dd will work.
ok let me elaborate this issue:
i need to check this functionality.
so i have one LVM boot disk
and one... (0 Replies)
Discussion started by: mxms755
0 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)