Mounting issue vxfs file system

Wednesday, October 10, 2012 at 7:43 AM | Posted by Elumalai M
node# mount /u001
vxfs mount: /dev/vx/dsk/rootdg/vol1 is corrupted. needs checking

 We have tried the fsck, but was not successful. We are unable to mount the filesystem /local
node#

 Solution:
format >> analyze >> read to fix the block 5125 error of disk c3t2d0.

 #fsck -F vxfs -y /dev/vx/rdsk/rootdg/vol1
#mount /local

Posted In | 0 comments |

Oneway mirror Need Maintenance state and connectivity lost issue in Storage

at 7:38 AM | Posted by Elumalai M

If you encounter onway mirror issue with Storage disk. If the disk status is okay but problem to clear the Need maintenance state and to avoid this problem in future the below is the solution.

Configuration and the submirror status:
d8: Mirror
Submirror 2: d28
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 1715358144 blocks


d28: Submirror of d8

State: Needs maintenance

Invoke: after replacing "Maintenance" components:
metareplace d8 c2t0d1s0
Size: 1715365632 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c2t0d1s0 0 No Last Erred

# umount /local
# umount /test2
If the file systems cannot be unmounted then you will have to reboot into single user mode before continuing with the below commands.

# fsck -F ufs -y /dev/md/rdsk/d215
# fsck -F ufs -y /dev/md/rdsk/d230

# metaclear d215
# metaclear d230

# metaclear -rf d8

# metainit d8 1 1 c2t0d1s0
# metainit d215 -p d9 -o 87666101 -b 743486015 -o 853202938 -b 76379648 -o 930764284 -b 182452224 -o 1117410814 -b 85983232
# metainit d230 -p d9 -o 46833323 -b 3774156 -o 843685879 -b 3807232


# mount /local
# mount /test2


d8: Mirror
Submirror 2: d28
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 1715358144 blocks


d28: Submirror of d8
State: Okay
Size: 1715365632 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c2t0d1s7 0 No Okay

Posted In | 0 comments |

Soft Partition error and recover

Friday, July 13, 2012 at 7:18 AM | Posted by Elumalai M
Error State:

 d304: Soft Partition

 Component: d7
State: Errored
Size: 6291456 blocks
Extent Start Block Block count
0 104867779 6291456

 Action to clear the Error:
# metarecover d20 -p -m



20: Soft Partition metadb configuration is valid
WARNING: You are about to overwrite portions of 20 with soft partition metadata. The extent headers will be written to match the existing metadb configuration. If the device was not previously setup with this configuration, data loss may result.
Are you sure you want to do this (yes/no)? yes
d20: Soft Partitions recovered from metadb # metastat d304
d304: Soft Partition
Component: 20
State: Okay
Size: 6291456 blocks
Extent Start Block Block count
0 104867779 6291456


d20: Mirror
Submirror 0: d17
State: Okay
Submirror 1: d27
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 286678272 blocks

d17: Submirror of d20
State: Okay
Size: 286678272 blocks
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase State Hot Spare
c1t2d0s0 0 No Okay
c1t3d0s0 10176 No Okay

d27: Submirror of d20
State: Okay
Size: 286678272 blocks
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase State Hot Spare
c1t4d0s0 0 No Okay
c1t5d0s0 10176 No Okay

 #

Posted In | 0 comments |

Error Message: metainit: node: "d74": unit not found

Thursday, February 23, 2012 at 2:15 AM | Posted by Elumalai M
node:/root# metainit -s nfsdg d74 -p d80 100g
metainit: node: "d74": unit not found
node:/root#
Identify the devfsadm process ID and kill it.
node:/root# ps -ef grep -i devfsadm
root 3099 1472 0 10:38:14 pts/1 0:00 grep -i devfsadm
root 15066 1 0 11:25:41 ? 58:46 /usr/lib/devfsadm/devfsadmd
node:/root# kill -9 15066
node:/root#
Now try it should work now
node:/# metainit -s nfsdg d74 -p d80 100g
d74: Soft Partition is setup
node:/#

Posted In , | 0 comments |

Migrating Solaris 8 physical server to Solaris zone

Thursday, February 16, 2012 at 4:20 AM | Posted by Elumalai M
Step1:
Preparation:
Solaris 10 with latest updated versionDownload and install the Solaris 8 Migration
SUNWs8brandr Solaris 8 Migration Assistant: solaris8 brand support (Root)SUNWs8brandu Solaris 8 Migration Assistant: solaris8 brand support (Usr)SUNWs8p2v Solaris 8 p2v Tool
Step2: Create the Flash Archive of solaris 8 server:
node# flarcreate -S -n solaris8 solaris8.flar
Step3: Set up a Solaris 8 zone
node# zonecfg -z solaris8solaris8: No such zone configuredUse 'create' to begin configuring a new zone.zonecfg:solaris8-system> create -t SUNWsolaris8zonecfg:solaris8> set zonepath=/export/solaris8zonecfg:solaris8> add netzonecfg:solaris8:net> set address=192.168.1.155/24zonecfg:solaris8:net> set physical=bge0zonecfg:solaris8:net> endzonecfg:solaris8> commitzonecfg:solaris8> exit
Step4: Install Solaris 8 zone using flar-archive

node# zoneadm -z solaris8 install -u -a /export/solaris8.flarLog File: /var/tmp/solaris8.install.13597.logSource: /export/solaris8.flarInstalling: This may take several minutes…Postprocessing: This may take several minutes…WARNING: zone did not finish booting.
Result: Installation completed successfully.Log File: /export/solaris8/root/var/log/solaris8.install.13597.log

Step5:
node #uname -aSunOS solaris8 5.8 Generic_Virtual sun4u sparc SUNW,Sun-Fire-V490

| 0 comments |

Failed root disk replacement in SVM

Wednesday, December 21, 2011 at 4:46 AM | Posted by Elumalai M
Step1: Backup of the current SDS configuration:
[root]# metastat -p >> /etc/lvm/md.tab
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

Posted In | 0 comments |

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

Tuesday, December 6, 2011 at 4:29 AM | Posted by Elumalai M
PROBLEM OVERVIEW
Defective Battery
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?
Write cache should be disabled prior to replacing battery to prevent data loss if power event occurs before replacement battery is charged

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE
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

Posted In | 0 comments |

Subscribe to: Posts (Atom)

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