9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I don't know if I am asking this correctly, but I have a hard drive with some bad sectors and it appears that some of the data is corrupt. I am having allot of trouble copying the data to a new drive. The issue is not in copying files, but that the new drive to which files are copied is not acting... (17 Replies)
Discussion started by: LMHmedchem
17 Replies
2. HP-UX
Hallo Friends,
I have application X running on hpux 11.11 and oracle 9i release 2. I recently had a hardware failure on disk /dev/dsk/c2t0d0
Below is the systemlog file :
root@a7dmc:/var/adm/syslog > /opt/resmon/bin/resdata -R 155713541 -r /storage/events/enclosures/gazemon/0_1_1_0.0.0... (11 Replies)
Discussion started by: kekanap
11 Replies
3. Solaris
Not too familiar with VxVM. We have a Device c1t0d0, disk rootdg01, group rootdg that was paired with Device c1t1d0, disk mirror_1, group rootdg.
c1t0d0 has failed.
When we get a replacement for c1t0d0 can we just run vxdiskadm and choose choice #5 to "replace a failed or removed disk" ?
... (9 Replies)
Discussion started by: pzxkys
9 Replies
4. Solaris
I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies
5. Solaris
hi guys,
i was doing a fresh installation of vxvm 4.0 on solaris 8 Sun enterprise 3500 and when i ran vxinstall command it gave me option of appdg and appdg02 to be encapsulated . I wanted to encapsulate rootdg. i wrongly encapsulated appdg. is there any work around for this ?
your response... (5 Replies)
Discussion started by: ishila
5 Replies
6. UNIX for Dummies Questions & Answers
Hmm, how to ask this without sounding too malicious...
How might one go about causing a disk corruption in OS X specifically or via the command line in UNIX in general?
Doesnt matter the severity of the problem, I just want to scare the person a little, then fix the problem for them.
Any... (1 Reply)
Discussion started by: Yummator
1 Replies
7. UNIX for Dummies Questions & Answers
Hi guys,
For some reason a client has given us a Sun Netra T1 with Solaris 8 to administer for them. That's always good business. However, the other day we rebooted the machine and to our amazement, after doing the preliminary hardware tests, we got an error messgae saying that /etc/inittab was... (3 Replies)
Discussion started by: Ivo
3 Replies
8. Cybersecurity
Help!
SCO Unix 5.05.
A relatievely new system went down on me today. I got the dreaded error:
Out of Space on Device (1/42).
I was able to clear up some space in the /tmp directory, however, when I try to boot, the system prompts me to go into single user mode and I get the... (2 Replies)
Discussion started by: gseyforth
2 Replies
9. UNIX for Dummies Questions & Answers
Thank you livin Free for all your help. We removed a lot of spool files and report files. Which should have freed up some space.
But now I think a major problem we have is we have lost or corrupt files which are preventing us from coming up correctly. Can we load or can you copy us a directory... (1 Reply)
Discussion started by: NOT A CLUE
1 Replies
vxdarestore(1M) vxdarestore(1M)
NAME
vxdarestore - restore simple or nopriv disk access records
SYNOPSIS
/etc/vx/bin/vxdarestore
DESCRIPTION
The vxdarestore utility is used to restore persistent simple or nopriv disk access (da) records that have failed due to changing the naming
scheme used by vxconfigd from c#t#d#-based to enclosure-based.
The use of vxdarestore is required if you use the vxdiskadm command to change from the c#t#d#-based to the enclosure-based naming scheme.
As a result, some existing persistent simple or nopriv disks go into the "error" state and the VxVM objects on those disks fail.
vxdarestore may be used to restore the disk access records that have failed. The utility also recovers the VxVM objects on the failed disk
access records.
Note: vxdarestore may only be run when vxconfigd is using the enclosure-based naming scheme.
Note: You can use the command vxdisk list da_name to discover whether a disk access record is persistent. The record is non-persistent if
the flags field includes the flag autoconfig; otherwise it is persistent.
The following sections describe how to use the vxdarestore utility under various conditions.
Persistent Simple/Nopriv Disks in the rootdg Disk Group
If all persistent simple or nopriv disks in the rootdg disk group go into the "error" state, use the following procedure:
1. Use the vxdiskadm command to change back to the c#t#d# based naming scheme.
2. Either shut down and reboot the host, or run the following command:
vxconfigd -kr reset
3. If you want to use the enclosure-based naming scheme, add a non-persistent simple disk to the rootdg disk group, use vxdiskadm to
change to the enclosure-based naming scheme, and then run vxdarestore.
Note: If not all the disks in rootdg go into the error state, simply running vxdarestore restores those disks in the error state and the
objects that that they contain.
Persistent Simple/Nopriv Disks in Disk Groups other than rootdg
If all disk access records in an imported disk group consist only of persistent simple and/or nopriv disks, the disk group is put in the
"online dgdisabled" state after changing to the enclosure-based naming scheme. For such disk groups, perform the following steps:
1. Deport the disk group using the following command:
vxdg deport diskgroup
2. Run the vxdarestore command.
3. Re-import the disk group using the following command:
vxdg import diskgroup
NOTES
Use of the vxdarestore command is not required in the following cases:
o If there are no persistent simple or nopriv disk access records on an HP-UX host.
o If all devices on which simple or nopriv disks are present are not automatically configurable by VxVM. For example, third-party
drivers export devices that are not automatically configured by VxVM. VxVM objects on simple/nopriv disks created from such disks
are not affected by switching to the enclosure based naming scheme.
The vxdarestore command does not handle the following cases:
o If the enclosure-based naming scheme is in use and the vxdmpadm command is used to change the name of an enclosure, the disk access
names of all devices in that enclosure are also changed. As a result, any persistent simple/nopriv disks in the enclosure are put
into the "error" state, and VxVM objects configured on those disks fail.
o If the enclosure-based naming scheme is in use and the system is rebooted after making hardware configuration changes to the host.
This may change the disk access names and cause some persistent simple/nopriv disks to be put into the "error" state.
o If the enclosure-based naming scheme is in use, the device discovery layer claims some disks under the JBOD category, and the vxdd-
ladm rmjbod command is used to remove remove support for the JBOD category for disks from a particular vendor. As a result of the
consequent name change, disks with persistent disk access records are put into the "error" state, and VxVM objects configured on
those disks fail.
EXIT CODES
A zero exit status is returned if the operation is successful or if no actions were necessary. An exit status of 1 is returned if vxdare-
store is run while vxconfigd is using the c#t#d# naming scheme. An exit status of 2 is returned if vxconfigd is not running.
SEE ALSO
vxconfigd(1M), vxdg(1M), vxdisk(1M), vxdiskadm(1M), vxdmpadm(1M), vxintro(1M), vxreattach(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdarestore(1M)