05-10-2017
What error are you getting when you fsck s4?
I understand your concern about being unable to see the c1 controller, however, you seem to be able to see all the disks on c1.
So one side of the mirror of d3 (d13 which is c1t0d0s4) has a problem and needs maintenance. I guess other mirrors on the same drive are still working so the drive itself hasn't failed and d3 should still be mount-able which is the whole point of mirroring.
Have you tried to break and remake that mirror?
10 More Discussions You Might Find Interesting
1. Solaris
I am getting the below mentioned error while trying to unistall a package from a 2.8 Solaris box. Please help..
pkgrm: ERROR: unable to determine current run-state
Removal of <PDMgr> failed (internal error).
No changes were made to the system. (1 Reply)
Discussion started by: chrisanto_2000
1 Replies
2. Filesystems, Disks and Memory
Hi,
I'm attempting to build a raid Z NAS using solaris, but I only have 4 sata ports on my MB, so I bought a Rosewill RC-211 PCIe controller (adds 2 sata II ports).
I'm new to solaris, but I understand that to add a new drive, you first run #devfsadm, which puts the files into /dev/dsk. I... (3 Replies)
Discussion started by: ciscocbee
3 Replies
3. Infrastructure Monitoring
hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient.
/etc(R)-bash-3.00$ init 6
/etc(R)-bash-3.00$ svc.startd: The system is coming down. Please wait.... (7 Replies)
Discussion started by: alienkidmj12
7 Replies
4. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
5. Solaris
hi friends, i had this problem in a Solaris 10 server
when i inserted my thumbdrive, i can't find the device file containing usb.
what should i do ? (2 Replies)
Discussion started by: Exposure
2 Replies
6. Solaris
I have inherited a solaris 10 server. I went to log into it the other day over the console connection, and after sucessfully entering the password, I was booted back to the login prompt with no errors visible.
If I enter an incorect password, the console displays 'incorrect password' and kicks... (8 Replies)
Discussion started by: Sol-nova
8 Replies
7. Solaris
Hi,
All of our servers run Solaris (currently 10, but looking to upgrade to 11). In each of our offices we have a server configured as a Primary Domain Controller via Samba to provide naming services to our Windoze users. I would like to continue with that arrangement, but I would also like... (2 Replies)
Discussion started by: wgkorb
2 Replies
8. Solaris
HI
I am unable to add printer in solaris (architecture is SUN and OS is Solaris 10) as I try to print the file it gives following error
Failed to contact service for erp-cljCP2025: not-found
Need help
Regards (7 Replies)
Discussion started by: smazshah
7 Replies
9. Solaris
Hi,
we have a sun sparc solaris 10 machine and recently there was a power failure and one of the server domain was down. So today morning i have powered up the domain and it returned me to ok prompt then i have booted the machine with disk from devalias, the system was up as normal and no error... (0 Replies)
Discussion started by: phanidhar6039
0 Replies
10. Solaris
Hello, I followed these instructions to create a Solaris 11 zone:
http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-092-s11-zones-intro-524494.html
And I am unable to ping anything from the Local Zone except for the IP address of the global zone.
My global zone has an IP... (6 Replies)
Discussion started by: unblockable
6 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)