Sponsored Content
Operating Systems Solaris Hardware RAID not recognize the new disk [Sun T6320] Post 302598649 by hicksd8 on Wednesday 15th of February 2012 04:39:02 AM
Old 02-15-2012
You need to ensure that the swapped disk has at least the same, if not more, LBA's than the disk its going to mirror. Many times I have seen what appears to be the same model of disk with different LBA's.

If the disk has even one less LBA than the one being mirrored then the controller will refuse to do it (even though the disk can be physically seen by the system).
 

9 More Discussions You Might Find Interesting

1. Solaris

Hardware RAID

I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies

2. Solaris

Sun T5120 hardware RAID question

Hi everyone I've just purchased a Sun T5120 server with 2 internal disks. I've configured hardware RAID (mirror) and as a result the device tree in Solaris only contains 1 hard drive. My question is, how would I know when one of the drives become faulty? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

3. Solaris

Add new disk to Sun StorEdge 3310 RAID

HI guys. Bit of a noob so bear with me. I have 2 new disks I want to add to my StorEdge 3310 but am getting lost in the steps. We have another 3310 (JBOD) that I was able to plug the disks into and they instantly showed up. Did a few minor commands after (drvconfig, devfsadm etc..) and I was... (4 Replies)
Discussion started by: jamie_collins
4 Replies

4. Hardware

Sun Blade T6320 memory configuration

Can you mix DIMMs in a T6320 (sparc) blade? I have read/heard that the DIMMs in a memory bay must be identical but can you have different size DIMMs installed in the blade? For instance, can you have 1 4GB DIMM in bay 0, 2 2GB DIMMs in bay 1, 4 1 GB DIMMs in bay 2 and 2 2GB DIMMs in bay 3 for a... (0 Replies)
Discussion started by: bluescreen
0 Replies

5. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

6. Hardware

Hardware RAID on Sun T2000 Server

Hi All I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command. Following is the hardware RAID output. root@oracledatabaseserver / $ raidctl RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies

7. Solaris

Solaris recognize HW Raid ??

Hardware: HP P2000 HP DL380 G7 with Solaris Software: Solaris 10 05/08 I had made a Hardware raid on P2000 and install solaris on G7, The raid card controller is working fine. How can I make the raid works on OS?? "raidclt" is getting nothing :wall::wall: Thanks (11 Replies)
Discussion started by: stanley1024
11 Replies

8. Hardware

Sun T3-1 hardware RAID

Hi all I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS. The documentation doesn't make it clear if: 1. The... (6 Replies)
Discussion started by: soliberus
6 Replies

9. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies
vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME
vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation SYNOPSIS
/etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b] [-t tasktag] {daname|dmname} DESCRIPTION
The vxbrk_rootmir command creates a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the broken-off mirror into a completely separate root disk that is suitable for booting by itself. Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks. A valid root mirror disk should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained. The given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror. If so, the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk. If the specified disk is not a valid root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur- rent VxVM root disk. After the mirroring operation is complete, the mirror is then broken off, and regenerated into a unique VxVM root disk. OPTIONS
-b Uses the setboot command to set the alternate boot disk to the specified disk. If the -v option is also specified, information is displayed about the current setboot settings. -g diskgroup Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created if it does not already exist. If the disk group already exists, the broken-off mirror is added to it. If this option is not specified, the disk group of the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk group to prevent the mirror from being automatically imported. -t tasktag Marks any tasks that are registered to track the progress of an operation with the specified tag, tasktag. This option is passed to vxrootmir if it is necessary first to mirror the specified disk that is to be broken off. -v Displays verbose output, including timestamps for operations that are in progress. This option is passed to vxrootmir if it is neces- sary first to mirror the specified disk that is to be broken off. ARGUMENTS
daname Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as the broken off mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0 VxVM vxbrk_rootmir INFO V-5-2-4023 17:47: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4025 17:47: DA c4t15d0s2, DM rootdisk06 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4052 17:47: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 17:47: Breaking off root mirror on DA c4t15d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 17:47: Setting broken off mirror on c4t15d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 17:47: Preparing disk c4t15d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 17:47: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 17:47: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 17:48: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 17:48: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 17:48: Alternate: 0/2/1/0.8.0.255.2.5.0 VxVM vxbrk_rootmir INFO V-5-2-4042 17:48: Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 17:48: Disk c4t15d0s2 is now a broken off root disk The next example shows the command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be called to mirror the root disk first: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0 VxVM vxbrk_rootmir INFO V-5-2-4023 16:25: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk VxVM vxrootmir INFO V-5-2-2501 16:25: Gathering information on the current VxVM root configuration VxVM vxrootmir INFO V-5-2-2441 16:25: Checking specified disk(s) for usability VxVM vxrootmir INFO V-5-2-2566 16:25: Preparing disk c5t5d0 as a VxVM root disk VxVM vxrootmir INFO V-5-2-3766 16:25: Disk c5t5d0 is now EFI partitioned disk c5t5d0s2 VxVM vxrootmir INFO V-5-2-2410 16:25: Adding disk c5t5d0s2 to brkdg as DM rootdisk03 VxVM vxrootmir INFO V-5-2-1646 16:25: Mirroring all volumes on root disk VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol VxVM vxrootmir INFO V-5-2-1616 16:40: Disk c5t5d0s2 is now a mirrored root disk VxVM vxbrk_rootmir INFO V-5-2-4052 16:40: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 16:40: Breaking off root mirror on DA c5t5d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 16:40: Setting broken off mirror on c5t5d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 16:40: Preparing disk c5t5d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 16:41: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 16:41: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 16:41: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 16:41: Alternate: 0/2/1/0.8.0.255.2.0.0 VxVM vxbrk_rootmir INFO V-5-2-4042 16:41: Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 16:41: Disk c5t5d0s2 is now a broken off root disk SEE ALSO
vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 11:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy