Why gridisks are not automatically created after replacing a diskdrive in a cellserver?
if the firmware version and cellserver's image versions are different.then automatic creation of celldisk and griddisk will get failed. because of that we may not be able to add the disks to the asm diskgroups.
1.1 How to check if the firmware is same across all the disks
cellcli -e list physicaldisk detail => will hep us to check if any of the disk's firmware differet from others.
name: 27:0
deviceId: 15
diskType: HardDisk
enclosureDeviceId: 27
errMediaCount: 0
errOtherCount: 0
foreignState: false
id: E0QXXB
luns: 0_0
makeModel: "SEAGATE ST360057SSUN600G"
physicalFirmware: 0705 physicalInsertTime: 2010-06-30T15:42:20-04:00
physicalInterface: sas
physicalSerial: E0QXXB
physicalSize: 558.9109999993816G
slotNumber: 0
status: normal
name: 27:1
deviceId: 16
diskType: HardDisk
enclosureDeviceId: 27
errMediaCount: 0
errOtherCount: 0
foreignState: false
id: E0QYFR
luns: 0_1
makeModel: "SEAGATE ST360057SSUN600G"
physicalFirmware: 0705 physicalInsertTime: 2010-06-30T15:42:21-04:00
physicalInterface: sas
physicalSerial: E0QYFR
physicalSize: 558.9109999993816G
slotNumber: 1
status: normal
name: 27:2
deviceId: 29
diskType: HardDisk
enclosureDeviceId: 27
errMediaCount: 0
errOtherCount: 0
foreignState: false
id: E0NAK9
makeModel: "SEAGATE ST360057SSUN600G"
physicalFirmware: 0805 physicalInterface: sas
physicalSerial: E0NAK9
physicalSize: 558.9109999993816G
slotNumber: 2
status: normal
name: 27:2
deviceId: 17
diskType: HardDisk
enclosureDeviceId: 27
errMediaCount: 47
errOtherCount: 1
foreignState: false
id: E0QQGD
luns: 0_2
makeModel: "SEAGATE ST360057SSUN600G"
physicalFirmware: 0705
physicalInsertTime: 2010-06-30T15:42:22-04:00
physicalInterface: sas
2 How to reconfigure the disk which was not configured properly due to firmware mismatch.
2.1 Run any of the below command to find the problematic disk drive. The firmware state shows "unconfigured(good)"
( MegaCli64 is available under /opt/MegaRAID/MegaCli folder)
MegaCli64 -CfgDsply -a0|grep 'Firmware state:'
Firmware state: Unconfigured(good), Spun Up
or
MegaCli64 -Pdlist -aAll | grep "Slot\|Firmware"
Slot Number: 0
Firmware state: Online
Slot Number: 1
Firmware state: Online
Slot Number: 2
Firmware state: Unconfigured(good), Spun Up Slot Number: 3
Firmware state: Online
Slot Number: 4
Firmware state: Online
Slot Number: 5
Firmware state: Online
Slot Number: 6
Firmware state: Online
Slot Number: 7
Firmware state: Online
Slot Number: 8
Firmware state: Online
Slot Number: 9
Firmware state: Online
Slot Number: 10
Firmware state: Online
Slot Number: 11
Firmware state: Online
of
2.2 identify the device id and slot number for the problematic drive
MegaCli64 -Pdlist -aAll | more
Enclosure Device ID: 27
Slot Number: 2
Device Id: 29
Sequence Number: 1
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS
Raw Size: 558.911 GB [0x45dd2fb0 Sectors]
Non Coerced Size: 558.411 GB [0x45cd2fb0 Sectors]
Coerced Size: 557.861 GB [0x45bb9000 Sectors]
Firmware state: Unconfigured(good), Spun UpSAS Address(0): 0x5000c50039e700f1
SAS Address(1): 0x0
Connected Port Number: 0(path0)
Inquiry Data: SEAGATE ST360057SSUN600G0805 E0NAK9
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Foreign State: None
Device Speed: 6.0Gb/s
Link Speed: 3.0Gb/s
Media Type: Hard Disk Device
Drive: Not Certified
2.3 Configure the diskdrive
./MegaCli64 -CfgLdAdd -R0 [27:2] WB NORA Direct NoCachedBadBBU -strpsz1024 -a0
Adapter 0: Created VD 11
Adapter 0: Configured the Adapter!!
Exit Code: 0x00
2.4 listout the status
MegaCli64 -Pdlist -aAll | grep "Slot\|Firmware"
Slot Number: 0
Firmware state: Online
Slot Number: 1
Firmware state: Online
Slot Number: 2
Firmware state: Online
Slot Number: 3
Firmware state: Online
Slot Number: 4
Firmware state: Online
Slot Number: 5
Firmware state: Online
Slot Number: 6
Firmware state: Online
Slot Number: 7
Firmware state: Online
Slot Number: 8
Firmware state: Online
Slot Number: 9
Firmware state: Online
Slot Number: 10
Firmware state: Online
Slot Number: 11
Firmware state: Online
2.5 drop the celldisk.
cellcli -e drop celldisk CD_02_nyjdvop02cel04 force
2.6 list the lun
cellcli -e list lun
2.7 Verify the size of the exisiting disks.so that we can make use of it for new griddisk creation
cellcli -e list griddisk CELL_DISK_NAME detail
name: CELL_DISK_NAME
availableTo:
cellDisk: CELL_DISK_NAME
comment:
creationTime: 2010-08-12T11:40:16-04:00
diskType: HardDisk
errorCount: 0
id: 0000012a-66f5-73f6-0000-000000000000
offset: 32M
size: 220G
status: active
2.8 Drop the problematic celldisk
cellcli -e drop celldisk CELL_DISK_NAME force
2.9 create new celldisk
cellcli -e create celldisk CELL_DISK_NMAE lun=0_2
2.10 Create grid disk
cellcli -e create griddisk GRID_DISK_NAME celldisk=CELL_DISK_NAME, size=220G
2.11 Add the disks to the DG
verify if the disks are candidate
select name,path,header_status,mount_status from v$asm_disk where path like '%griddisk%';
alter diskgroup diskgroupname add disk '0/xxx/xxxxx';
2.12 ALL done
Dear Friends, The content in this blog are purely based on my own opinion ,it is not reflecting any of my current or previous employers materials or official documents. All my posts here are not warranted to be free of errors. Please use at your own risk and after thorough testing in your environment. If you feel that i am violating any of the company's policies or documents, kindly mail me at jeyaseelan.hi@gmail.com,I am happy to take out those content from this blog.
Subscribe to:
Post Comments (Atom)
-
We may not be able to disable the logtransport when the database is in maximum availabilty mode. We may get the below error DGMGRL...
-
Error Messages: We may get the following error messages while doing ASM operations ORA-15137: The ASM cluster is in rolling patch state....
-
MIRA - Multi Instance Redo Apply - 12cR2 onwards/18C With Oracle 12c Release 2, We can enable Multi Instance Redo apply ( MIR...
No comments:
Post a Comment