ONTAP Hardware
ONTAP Hardware
Solved! See The Solution
MGWD can restart for many reasons, and it usually fixes itself. You could raise a ticket with NetApp to take a look but I would suggest - Updating 'Disk Firmware' & 'DQP' (DiskQualificationPackage). As you mentioned, it happens for the NEW DISK (Swapped), I would suggest checking if Disk_FW & DQP is up-2-date, it's NDU anyway.
MGWD can restart for many reasons, and it usually fixes itself. You could raise a ticket with NetApp to take a look but I would suggest - Updating 'Disk Firmware' & 'DQP' (DiskQualificationPackage). As you mentioned, it happens for the NEW DISK (Swapped), I would suggest checking if Disk_FW & DQP is up-2-date, it's NDU anyway.
Dear Ontapforrum,
Thanks for your reply. This storage is no longer in warranty with NetApp.
I check current customer DQP is : # Datecode: 20190404
The latest DQP from your provided URL is: # Datecode: 20230501
The section for same disk type in two versions has the same information including Firmware NA01:
DriveStart
VendorId=NETAPP
ProductId=X425_SIRMN1T2A10
Firmware=NA01
CheckRevision=0
QualFlags= QDC_FAST_MP_VFY_ARW_FUA_SFA_SM QD_DISK_SUPPORTS_BCS
QualFlags= QD_PARTITIONABLE
FastZero=10000
BPS=520
VerifySize=128
RPM=K10
LastBlock=GIG1142
LBAValueBCS=8b7281ff
AZCSLastBlock=UNSUPPORTED_SIZE
AZCSLBAValue=2
WriteSameSize=0
DriveDeviceClass=DEFAULT_DEVICE
DriveSystemClass=DEFAULT_SYS
DriveEnd
There are some other disks in system has same type and firmware running without error.
Do you think Updating 'Disk Firmware' & 'DQP' is neccesary ?
Should we find other empty slot and try for new warranty disk ?
Thank you for your time.
Irrespective of whether other disks are not complaining (having same fw). I would advise you to please get the 'fw' & 'DQP' bundled installed. Once that is done, we can continue troubleshooting.
Dear Ontapforrum,
Thank you for your comments.
I just find that system show 2 lines for same disk location (see attached image).
It seems that the fail disk (1st line) information is still there after removing it. And then the new disk (2nd line) can be assinged.
How can we remove old information of old disk? If we can do that I guess we can assign owner for new disk.
Try assigning the disk to the node forcefully:
Cluster1::> system node run -node <node-name>
Node> disk assign <disk> -f
Dear Ontapforrum,
Thank you for your support.
We tried replace other failed disks and somehow the system rescan storage slots, then there is only the unassigned disk in the old disk location and no information of old failed disk any more. After that we can assign owner for warranty disk.