02-13-2020
Also, from your original post, it shows that c1t0d0 is the disk being rebuilt (RESYNCING) and c1t1d0 is running OK.
10 More Discussions You Might Find Interesting
1. Solaris
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
Discussion started by: BOFH
2 Replies
2. Solaris
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies
3. Solaris
Hi,
Can anyone suggest me any USB Hard Disk Drive which I can connect to Sun Fire V890 and take backup at a quick speed. A test with SolidState USB Hard Drive for backup work was taking writing at 2GB per hour for a 75GB backup.
Regards,
Tushar Kathe (1 Reply)
Discussion started by: tushar_kathe
1 Replies
4. Solaris
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies
5. Solaris
Hello,
I am seeing error messages in V440 (OS = solaris 8). I have copied here :
The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day..
I... (5 Replies)
Discussion started by: upengan78
5 Replies
6. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
8. Solaris
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies
9. Solaris
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies
10. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
LEARN ABOUT HPUX
vxunreloc
vxunreloc(1M) vxunreloc(1M)
NAME
vxunreloc - move a hot-relocated subdisk back to its original disk
SYNOPSIS
/etc/vx/bin/vxunreloc [-f] [-g diskgroup] [-n dm_name] [-t tasktag] dm_name
DESCRIPTION
The Veritas Volume Manager (VxVM) hot-relocation feature can detect an I/O failure in a subdisk, relocate the subdisk, and recover the plex
associated with the subdisk. vxunreloc lets you reverse the process and move the hot-relocated subdisks back onto a disk that was replaced
after a disk failure.
dm_name specifies the disk where the hot-relocated subdisks originally resided. The -n option moves the subdisks to a different disk from
where VxVM originally relocated them. For example, when disk03 fails, all the subdisks residing on it are hot-relocated to other disks.
After the disk is repaired, it is added back to the disk group using a different name, for example, disk05. If you wanted to move all the
hot-relocated subdisks back to the repaired disk, you would enter:
/etc/vx/bin/vxunreloc -n disk05 disk03
When vxunreloc moves the hot-relocated subdisks, it moves them to their original offsets. However, if there was a subdisk that occupied
part or all of the area on the destination disk, vxunreloc prints an error message and exits. In this situation, you can use the -f option
to unrelocate the subdisks to a specified disk, but not to their original offsets.
OPTIONS
-f Unrelocates a subdisk to a different offset if unrelocating to the original offset is not possible.
-g diskgroup
Unrelocates a subdisk from the specified disk group. If this option is not specified, the default disk group is determined using
the rules given in the vxdg(1M) manual page.
-n dm_name
Specifies a new disk name to relocate to a disk with a different name.
-t tasktag
Specifies a tag to pass to the underlying utility.
SUBDISK RECORD FIELDS
orig_dmname
When a subdisk is hot-relocated, its original disk media name is stored in the orig_dmname field. When you run the vxunreloc
command to move the subdisk back to the original disk (or to a new disk), this field is cleared. Before you run the vxunreloc
command, you can do a search on this field to determine the subdisks that originated from a failed disk. For example, the fol-
lowing command lists all the subdisks that were hot-relocated from mydg01 in the disk group mydg. Note that you must prefix the
field name with "sd_" for the command to work.
vxprint -g mydg -se 'sd_orig_dmname="mydg01"'
orig_dmoffset
When a subdisk is hot-relocated, its offset into the original disk is stored in the orig_dmoffset field. When you run vxunreloc
to move the subdisk to the original disk, or to a new disk, this field is zeroed. The following command lists a hot-relocated
subdisk which originally resided at disk10 at offset 1000. Again note that you must prefix the field names with "sd_" for the
command to work.
vxprint -g dg01 -se 'sd_orig_dmname="disk10"
&& sd_orig_dmoffset=1000'
EXIT CODES
If the operation fails, vxunreloc exits with a non-zero status. A non-zero exit code is not a complete indicator of the problems encoun-
tered, but rather denotes the first condition that prevented further execution of the utility.
See vxintro(1M) for a list of standard exit codes.
SEE ALSO
vxassist(1M), vxintro(1M), vxmake(1M), vxprint(1M), vxrelocd(1M), vxsd(1M), vxsparecheck(1M)
VxVM 5.0.31.1 24 Mar 2008 vxunreloc(1M)