05-17-2005
Maybe you should post some more info - your original question wasn't very informative as far as the many things you have going on. You stated everything was identical and then afterwards mentioned VxVM - is the root partition controlled by Veritas? What do you mean by storage is involved? You stated you were moving "the disk".
Post the OS and version
Post the Veritas VM version
Post the hardware information
Post any other relevant information on what you are trying to accomplish.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command).
When try to mount I am getting, I got the error:
mount: /dev/dsk/c1t1d0s6 is not this fstype.
I... (3 Replies)
Discussion started by: sunshine
3 Replies
2. Shell Programming and Scripting
I have a file --> file1.txt
i need to copy this file to another server using FTP....the 2 servers are server1 and server2..may i know how to write a script that can do this?
thanks in advance! Im a newbie to this... (4 Replies)
Discussion started by: forevercalz
4 Replies
3. Solaris
Hi,
df -h display:
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% /
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
swap 1.0G 152K 1.0G 1% /var/run
swap 1.1G 24M 1.0G 3% /tmp
/dev/dsk/c1t0d0s3 57G 13G 43G 24%... (4 Replies)
Discussion started by: lamoul
4 Replies
4. Red Hat
Hi, we have a root-server with 2 Disks, each 750 gb / centos 5.1
we would like to have 4 mirrored data, and 1 mirrored boot-filesystem
what do you think is the best solution, I would like to use linux lvm for a raid1-mirror, but I was told the system wont boot in case of a disk failure
... (4 Replies)
Discussion started by: funksen
4 Replies
5. Solaris
Hi,
The disks of my servers are getting full and I need to move the /export/home partition on to a new set of disks. I already have 2 mirrored disks and have added 2 more and mirrored them after creating the filesystem on them.
Do I just need to edit the /etc/vfstab and point the /export/home... (1 Reply)
Discussion started by: run_time_error
1 Replies
6. 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
7. UNIX for Dummies Questions & Answers
Hi,
I have server with 2 active disk, but disk 1 contain big part of os is falling,
how can i move everything to disk 2 and then remove the disk 1?
Thanks (4 Replies)
Discussion started by: prpkrk
4 Replies
8. Linux
Hi
We have RHEL 7.3 running from local disk and we want to move it to storage.
I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies
9. Solaris
We have in a couple of occasions moved root disk & flashcard in netra 240 to new identical hardware instead of replacing mb in dead server. Flashcard is to preserve mac adresses and mainly hostid for license stuff. Works without doing anything other than poweron & boot.
Now we have a similar... (5 Replies)
Discussion started by: stockhes
5 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)