Disk is seen as partner by both Controllers after replacement.

[#1]

Hello All

I have just replaced a failed disk (5c.23.11) in one of our FAS6210. The disk was owned by controller 1 at the time. Once the disk was replaced after a minute are so, the amber led comes on and the disk cannot be seen in the cLi (disk show, vol status -s / -f etc). Logged onto system manager and it shows as a partner disk on both controllers? There were 2 failed disks at the time. The first replaced ok. I have also tried 3 new disks.

NetApp Release 8.2.3P3 7-Mode

BIR-NETAPP01> disk show 1c.23.11                    -------------------->> (now labled as 1c.23.11)
DISK OWNER POOL SERIAL NUMBER HOME DR HOME

BIR-NETAPP01> disk show -n
disk show: No unassigned disks

BIR-NETAPP01> vol status -f

Broken disks (empty)

Has anyone see this before?

Cheers

[#2]

Hi,

Before proceeding with the following commands, make sure that the disk in question is not currently in a RAID group. If it is, copy the disk to a spare disk with the following command:

:::> storage disk replace -disk <CDOT disk ID > -replacement <CDOT disk ID of spare disk>  -action start

Disable autoassign

Remove disk ownership 

Check if disk is unassigned.

Now assign owner to the unassigned drive manually

Turn on autoassign

[#3]

Hi, sorry to say, this did not resolve the issue.

[#4]

Hi Darren,

Have you tried to check whether the disk is visible at all in a sysconfig -a on either node?

If the disk is present there, try using the disk show -a to see if it shows up and what the owning serial number is.

It could be the disk is a refurbished one where the disk ownership was not removed fully.

/Xander

[#5]

I've not run into this specifically but maybe just start by removing the disk ownership from the "offending" disk and then assigning it directly to the correct node:

https://library.netapp.com/ecmdocs/ECMP1368859/html/GUID-84934533-63CA-4A73-82DB-31BBF768C1E8.html

Good luck,

Chris

[#6]

@xandervanegmond Many thanks, as you stated, the disk was a refurb and still had assignment to its old Filer. Using disk assign -f sorted the issue.

Cheers