Failed root disk replacement in SVM

Wednesday, December 21, 2011 at 4:46 AM
Step1: Backup of the current SDS configuration:
[root]# metastat -p >> /etc/lvm/
removal of replicas stored on this disk
[root]# metadb -d c1t0d0s4
Step2: detach and deletion of sub mirror d11 (swap)
[root]# metadetach d1 d11 && metaclear d11
Step3: disk removal
[root]# luxadm remove_device /dev/rdsk/c1t0d0s2
WARNING!!! Please ensure that no file systems are mounted on these device(s). All data on these devices should have been backed up.
The list of devices which will be removed is:
1: Device name: /dev/rdsk/c1t0d0s2 Node WWN: 2000000c504fd050
Device Type: Disk device
Device Paths: /dev/rdsk/c1t0d0s2
Please verify the above list of devices and then enter c or to Continue or q to Quit. [Default: c]:c stopping: /dev/rdsk/c1t0d0s2.... Done
offlining: /dev/rdsk/c1t0d0s2.... Done
The drives are now off-line and spun down.
Physically remove the disk and press the Return key.
Hit after removing the device(s).
Note: Disk has to be physically removed before pressing "ENTER" when running luxadm remove_device; otherwise, picld will notify the kernel that the drive was not removed and WWN of this drive will remain in the loop -- and the FCAL subsystem may get confused, especially if recommended patches are out of date
[root]# devfsadm -C -c disk
Step4: Insertion of the new disk drive:
<<< physical insertion >>>
[root]# devfsadm -v
Step5: partitioning:[root]# prtvtoc /dev/rdsk/c1t1d0s2 fmthard -s - /dev/rdsk/c1t0d0s2
Step6: adding SDS replicas :
[root]# metadb -ac 3 c1t0d0s4
Step7: resynchronization :
[root]# metainit d11 && metattach d1 d11
[root]# for i in 0 3 6 ; do metareplace -e d$i c1t0d0s$i ; done

How to Remove and Replace a Sun Storage 3510/3511 FC Array Battery

Tuesday, December 6, 2011 at 4:29 AM
Defective Battery
Write cache should be disabled prior to replacing battery to prevent data loss if power event occurs before replacement battery is charged

Check for amber LED on battery, check CLI battery status and location (upper or lower slot). From SC CLI: sccli> show battery
Prepare array for battery replacement
1. To determine status of write cache on array, access array Main Menu from telnet.

2. Select appropriate mode and press

3. Clear any pop-up messages with + < C> Select Disable pop-ups On upper right of Main Menu, Cache Status is displayed. Value to right indicates percentage of controller cache that differs from what is saved to disk. “Clean” means all cache has been saved to disk.

4. From telnet Main Menu, Disable cache: a. Select View and edit Configuration parameters b. Select Caching Parameters . Note cache state (enabled or disabled). c. Select Write-Back Cache Enable ? > No d. Disable Write-back cache? >YesFrom sccli, Disable Cache: e. sccli -o (out-of-band) or sccli /dev/dsk/c#t#d#s2(in-band) f. Check cache parameters. From sccli> show cache-parameters g. Disable cache. sccli> set cache-parameters write-through

5. Verify write-through cache status. sccli> show cache-parameters
Note: Verify "cache" status led on Raid controller is off

6. Remove ethernet and serial cable from battery module

7. Unscrew and disengage thumbscrews and cables on battery module and use thumbscrews to pull out the battery module

8. Insert new battery module and tighten thumbscrews until finger tightWARNING: Do not force or apply excessive pressure when inserting battery module

9. Re-attach cables

10. Using CLI (sccli), check battery status and set in service datesccli> show battery-statussccli> show battery-status -usccli> show battery-status
If second battery needs to be replaced, repeat steps 6-10

11. Confirm controller redundancy. sccli >show redundancy

12. Restore write cache to original settings. To Enable Write-Back Cache a. Select View and edit Configuration parameters b. Select Caching Parameters c. Select Write-Back Cache Disabled d. Enable Write-Back Cache?--> YESsccli> set cache-parameters write-back
Note:Write cache will enable once battery can protect on-board cache. Verify battery is charging by blinking green light on battery. Battery status LED may remain amber for up to 30 minutes.

13. Verify host access

14. Restart Configuration Services agent to prevent expired battery related messages from recurring. From host, type/etc/init.d/ssagent stop/etc/init.d/ssagent start

Solaris | Powered by Blogger | Entries (RSS) | Comments (RSS) | Designed by MB Web Design | XML Coded By