08-19-2009
Quote:
Originally Posted by
aixpank
I know the reason of failing.
If you would share your knowledge with us, we might be able to help you recovering your system without restoring from backups - since it is apparently NOT a failed disk?
Anyways, you should be able to restore a plain rootvg onto your spare disk and than import the 'old' rootvg under another name / VGID ... AIX will rename the logical volumes but if you recreate the empty mountpoints, you should be able to mount the filesystems manually.
Kind regards
zxmaus
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Sun server 4
Getting message /: write failed, file system full.
Okay so the problem seems obvious. The file system is full.
This server is used for DNS and DHCP on a T1 connected WAN. I can't get it to quit displaying the same message as above, even when powered down and restarted.
So... (1 Reply)
Discussion started by: lancest
1 Replies
2. SCO
I am helping a company recover a system that is SCO OS 5.0.5 - they have their backup media, cd copies of SCO, but they do not have their license keys to install and SCO is being difficult in validating their license.
Does anyone have an install license key for 5.0.5 that they would be willing... (1 Reply)
Discussion started by: ggraham
1 Replies
3. AIX
1. creating information file (/image.data) for rootvg ok!
2. creating tape boot image
bosboot : dd failed to copy /dev/rmt1.1.
bosboot: WARNING! bosboot failed - do not attempt to boot device
mksysb: Attempt to create a bootable tape failed:
bosboot -d /dev/rmt1.1 -a failed... (1 Reply)
Discussion started by: fla22
1 Replies
4. Filesystems, Disks and Memory
Is it possible that recovering a disk with jffs2 file system ? (1 Reply)
Discussion started by: s. murat
1 Replies
5. IP Networking
As we are facing issue with this server connection. The error is:
The system function gethostbyname() failed to find the client's host name.
how can i check if the server "server1" is able to resolve the client hostname (hosts / dns)?
i can ping the client from server.
any... (1 Reply)
Discussion started by: jinslick25
1 Replies
6. Solaris
Hi
I would like to know one thing while recovering from corrupt /etc/system file.
For that we have to do at ok> boot -a
when system ask for system file we give /dev/null. Could any one tell me what /dev/null value will do in this case.
Regards (1 Reply)
Discussion started by: sb200
1 Replies
7. UNIX for Advanced & Expert Users
Hi Experts,
I have a code like this.
=====
#include....
int main()
{
int count = 0;
while(1){
printf("\n Interation number is: %d \n ",count);
rv = system(" test.sh > log.txt " );
if (-1 == rv)
{
printf("Could not generate static log: error... (12 Replies)
Discussion started by: binnyjeshan
12 Replies
8. Solaris
Hey guys,
I'm attempting to migrate us to a new box. First problem I had was the change in architecture going from sun4u to sun4v, we have a Sun M5000 and are moving to a Fujitsu M10-4. I figured out how to make the flash archive work between architectures.
Now I appear to be running into an... (2 Replies)
Discussion started by: kaledragule
2 Replies
9. Solaris
I have an oldish Solaris 10 system (SunFire x4240), which due to a recent heating event in the server room, lost it's system disk.
I have rsync backups of all the other (data) disks, but apparently I do not have a backup of /. :-( I can start the machine up in failsafe mode, but running fsck on... (4 Replies)
Discussion started by: jj5406
4 Replies
10. Infrastructure Monitoring
Hello Team,
I am getting below error on nagios to monitor windows Server 2012.
Failed to read from eventlog: 31: A device attached to the system is not functioning.
basically we are monitoring Eventlog file for server reboot or unexpected shutdown. Could you please help here. What could be... (0 Replies)
Discussion started by: ghpradeep
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)