ONTAP Hardware

Incorrect Disk Name

SysHsLee
2,287 Views

Hello All.

 

I had an issue with my disk replacement before and looking for cause and solution.

 

Platform: FAS8300

Version: 9.12.1P4

Disk P/N: X343A-R6

 

I have recently replaced two disk due to the failure of the disk.

I did an simple disk replacement but the spare disk name was printed like <node_name>:<disk_path>.

 

hostname::*> disk show -spare
Original Owner: hostname-node1
Checksum Compatibility: block
Usable Physical
Disk HA Shelf Bay Chan Pool Type Class RPM Size Size Owner
--------------- ------------ ---- ------ ------ ----------- ------ -------- -------- --------
1.4.21 4d 4 21 B Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node1
1.4.23 4d 4 23 B Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node1
hostname-node1:0a.03.9 0a 3 9 A Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node1
Original Owner: hostname-node2
Checksum Compatibility: block
Usable Physical
Disk HA Shelf Bay Chan Pool Type Class RPM Size Size Owner
--------------- ------------ ---- ------ ------ ----------- ------ -------- -------- --------
1.4.20 4d 4 20 A Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node2
1.4.22 4d 4 22 A Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node2
hostname-node2:4d.05.6 4d 5 6 A Pool0 SAS performance 10000 1.63TB 1.64TB hostname-node2
6 entries were displayed.

 

In command with a shellnode "sysconfig -r" I could see that its in spare disk like usual.

And also right after I assign the disk to the node the amber LED turned on so I tried the reseat job after removing the ownership.

It worked for the one disk but not for the other one. And the disk name remains the same for both disk.

 

I have looked into the KB but I don't think does are the same symptom. 

 

The link at the below is the KB that I have looked into.

https://kb.netapp.com/onprem/ontap/hardware/disk_name_incorrect_display_after_disk_replacement

https://kb.netapp.com/onprem/ontap/hardware/Amber_LED_reappears_on_a_replaced_disk_even_after_turning_off_the_fault_LED

 

Have anyone had a same issue as I did? If you did how did you solved it?

 

Best regards

Lee

 

1 ACCEPTED SOLUTION

Amador
2,151 Views

If the previous steps didn't resolve the issue a Takeover/Giveback in both directions, as mentioned in the KB, should recover the correct drive name.

View solution in original post

3 REPLIES 3

andris
2,235 Views

Did you install or update the DQP?

Is your SAS cabling healthy (MP-HA)?

When reseating a drive, please wait 60s before reinserting it.

SysHsLee
2,212 Views

MP-HA was healthy.

And yes I have waited 3 min before reinserting it.

With the DQP, I have not tried it yet.

 

Do you think there might be a problem with the disk firmware?

Amador
2,152 Views

If the previous steps didn't resolve the issue a Takeover/Giveback in both directions, as mentioned in the KB, should recover the correct drive name.

Public