nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FAS8080 - warranty disk can not be assigned - with "management gateway server restarted" message

Hanh

Hi,

Customer has FAS8080 firmware v9.1P14.

We replace failed disk for customer, when new disk is plugged in, command disk assign fail with these messages:

cluster1::> disk assign -disk x.y.z -pool 0 -owner cluster1-01

The management gateway server restarted. Waiting to see if the connection can be reestablished.

The connection with the management gateway server has been reestablished.

If the root cause of the interupption was a process core, you can see the core file details by issuing the following command:

system node coredump show -node local -type application -corename mgwd.* -instance

cluster1::>

Customer say that each time they issue command "disk show" for the new disk the log message management gatewary server restarted happen, but not for other disks.

We aslo download the cordump files (-type application) but can't see the contents.

The new disk is now in unassigned status.

1. How can we read the coredump file?

2. Is there a workaround to fix this "management gateway server restarted" ?

3. We have other second spare disk, and want to try take out 1st spare disk, then plug-in 2nd spare disk. Can we hot-plug out the 1st spare disk currently in unassigned status? Is there any procedure/command should be done before?

Thanks in advance.

Find more posts tagged with

Accepted answers

Ontapforrum

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.

Disk Fw:
https://mysupport.netapp.com/site/downloads/firmware/disk-drive-firmware/download/DISKDRIVE/ALL/all.zip

DQP:https://mysupport.netapp.com/site/downloads/firmware/disk-drive-firmware/download/DISKQUAL/ALL/qual_devices.zip

All comments

Ontapforrum

Disk Fw:
https://mysupport.netapp.com/site/downloads/firmware/disk-drive-firmware/download/DISKDRIVE/ALL/all.zip

DQP:https://mysupport.netapp.com/site/downloads/firmware/disk-drive-firmware/download/DISKQUAL/ALL/qual_devices.zip

Hanh

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.

Ontapforrum

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.

Hanh

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.

Hanh

Disk 3.12.4 on GUI - 2 lines - Copy.png

Ontapforrum

Try assigning the disk to the node forcefully:
Cluster1::> system node run -node <node-name>
Node> disk assign <disk> -f

HanhT

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.