Вы находитесь на странице: 1из 4

Disk (Mirrored) Replacement Procedure, for Sun

Fire X4170, X4270, X4275, X4150, X4250, X4450.


Real Scenario
#############################################
#################
Mirror d10:
Sub-mirror:d11
Disk slice: c0t0d0s0
Sub-mirror:d12 (Need Maintenance)
Disk slice: c0t1d0s0
Mirror d20:
Sub-mirror:d21
Disk slice: c0t0d0s1
Sub-mirror:d22 (Need Maintenance)
Disk slice: c0t1d0s1
Mirror d30:
Sub-mirror:d31
Disk slice: c0t0d0s3
Sub-mirror:d32 (Need Maintenance)
Disk slice: c0t1d0s3
Mirror d40:
Sub-mirror:d41
Disk slice: c0t0d0s4
Sub-mirror:d42 (Need Maintenance)
Disk slice: c0t1d0s4
Mirror d50:
Sub-mirror:d51
Disk slice: c0t0d0s5
Sub-mirror:d52 (Need Maintenance)
Disk slice: c0t1d0s5
Mirror d60:
Sub-mirror:d61
Disk slice: c0t0d0s6
Sub-mirror:d62 (Need Maintenance)
Disk slice: c0t1d0s6
Device Relocation Information:
Device
Reloc
Device ID
c0t4d0
Yes
id1,sd@f0f9092e247dabc2300055f2f000d
c0t5d0
Yes
id1,sd@f0f9092e247dabc4e000227dd000e
c0t2d0
Yes
id1,sd@f0f9092e247daa0c900066d9e000e
c0t3d0
Yes
id1,sd@f0f9092e247dabbf00000ca0b000c
c0t7d0
Yes
id1,sd@f0f9092e247dab3a1000946cd000b
c0t6d0
Yes
id1,sd@f0f9092e247dab1bb0009723c000a
c0t0d0
Yes
id1,sd@f0f9092e24a2ecf4c000359df0000
[c0t1d0 device ID was not present in the above list]

#############################################
#################

1. Detach all the sub-mirrors of the Disk1.


#

metadetach d10 d12

metadetach d20 d22

metadetach d30 d32

metadetach d40 d42

metadetach d50 d52

metadetach d60 d62

2. Clear the sub-mirrors.


#

metaclear d12

metaclear d22

metaclear d32

metaclear d42

metaclear d52

metaclear d62

3. Power down the server, and replace the disk. And put the
power back on.
4. Press Ctrl+A as soon as the system shows Press <Ctrl><A>
to enter ARCU(Adaptec RAID Configuration Utility).
5. A GUI will appear on the screen with three menus
a. Array Configuration Utility.
b. Serial Select Utility.
c. Disk Utility.
Select the Array Configuration Utility To configure the new disk to
the existing array.

6. It is needed to initialize the new disk first. To do so select the


Initialize Disk menu of Array Configuration Utilitys Main
Menu.
7. Select the new disk in between the Select drive to Initialize
using the arrow keys and press the INS or Insert key to put
it into the Selected Drive list. And press Enter. A message
warns you that initializing a drive erases array information
from it. Type Yes. This will initialize the new disk.
8. Go to the Manage Array to note down the configuration
details of the other drives, as it is required while creating a
new array.
9. Now go to the Create Array in the Main Menu. Select the
new disk in between the Select drive to create Array using
the arrow keys and press the INS or Insert key to put it into

the Selected Drive list. And press Enter. Now It will ask for
some input like
o

Array Type Select an array type from the drop-down list.


If you selected a single drive, the array type is Volume.

Array Label Type a label.

Stripe Size Type a stripe size.

Read Caching Type Y or N.

Write Caching Select an option from the list.

a. Put appropriate values in the above option, that we have note


down before previously.
b. Press Enter of select Done to complete the process.
c. If the Write Caching setting is Enable always, and if you do
not have a battery, or if the battery is not charged
sufficiently, several warnings might appear. Type Yes to
proceed, or type No to return to the Array Properties screen.
d. If the write cache is enabled, a write cache warning appears.
e. Press Enter to continue.

10.
Exit the utility by pressing Esc. And the system will
proceed to o/s booting.
11.
After the o/s is booted up. The first step that must be
taken is to update the metadevice id of the new disk. Use the
following command
#

metadevadm u /dev/dsk/c0t1d0.

(Note: if by mistake, the sub-mirrors are created and


attached with the main mirrors, before executing the above
command, all the sub-mirrors of the Disk1 will be at Need
Maintenance state after the system is rebooted.)

12.

Next copy the vtoc table of Disk0 to Disk1.


#

13.

prtvtoc /dev/rdsk/c0t0d0s2 | fmthard s - /dev/rdsk/c0t1d0s2

Create the Meta Device State Database in to Disk1.


#

metadb a f c3 c0t1d0s7

14.

Create sub-mirrors of the Disk1 slices


#

metainit d12 1 1 c0t1d0s0

metainit d22 1 1 c0t1d0s1

metainit d32 1 1 c0t1d0s3

metainit d42 1 1 c0t1d0s4

metainit d52 1 1 c0t1d0s5

metainit d62 1 1 c0t1d0s6

15.

Attach the sub-mirrors with the mirrors.


#

metattach d10 d12

metattach d20 d22

metattach d30 d32

metattach d40 d42

metattach d50 d52

metattach d60 d62

All the above x-servers uses Optional StorageTek SAS RAID 8-Port

Internal HBA, SG-XPCIESAS-R-INT-Z, Adaptec/Intel-based disk controller.


So, it is necessary to configure the new disk in the controller as a single array. If
not done so the o/s wont be able to find the new disk. And if it is add online the
system will find it but wont be able to label it, and will through huge amount of
hard errors.
So, if the Disk1 sub-mirrors are showing un-available in those above
Xservers. Please check that the device ID is showing in the metastat or
not. If not please detach and clear all the designated sub-mirrors, update
the device ID, and recreate and reattach the sub-mirrors. And after a
reboot the problem of disk unavailability will resolve, as all the mirrors will
be in Okay state. If not then there may be some problem with the disk
itself.
Device Relocation Information:
Device
Reloc Device ID
c0t4d0
Yes
id1,sd@f0f9092e247dabc2300055f2f000d
c0t5d0
Yes
id1,sd@f0f9092e247dabc4e000227dd000e
c0t2d0
Yes
id1,sd@f0f9092e247daa0c900066d9e000e
c0t3d0
Yes
id1,sd@f0f9092e247dabbf00000ca0b000c
c0t7d0
Yes
id1,sd@f0f9092e247dab3a1000946cd000b
c0t6d0
Yes
id1,sd@f0f9092e247dab1bb0009723c000a
c0t0d0
Yes
id1,sd@f0f9092e24a2ecf4c000359df0000