ONTAP Hardware

Replaced disk from FAS2020 into FAS2040+DS4243, now what?

itadmins
8,734 Views

Good day.  Let me start by stating I do not want to save data.  This is starting from scratch.

I have moved 12 drives from a FAS2020 into a DS4243 that is ran from a FAS2040.  I thought that the drives from the 2020 were zeroed out but I was mistaken.  I can see the drives in the CLI of both controllers on 2040.  I do not see the drives if I run DISK SHOW or DISK SHOW -N.   I do see them listed when I run DISK SHOW -A (see below) but they are still listing the old 2020 filer name (sv-storage-1b or 2b).  I was not able to remove ownership because   “disk remove_ownership: Disk 0d.01.4 does not exist”. Any way to get these drives to work in the 4243 with out having to go back to the 2020 to zero out the drives? This is a repurposed design for a disk-to-disk backup solution I am working on.  Thanks!

The 0c.00.xx is the FAS 2040 disks (active/active 3 drives per controller)

The 0d.01.xx is the DS4243 with the newly added 1TB SATA drives (replaces 300GB SAS)

sv-storage-1a> disk show -a

  DISK OWNER                  POOL   SERIAL NUMBER

------------ -------------          -----  -------------

0c.00.2      sv-storage-1a((***)   )   Pool0  WD-(***)

0c.00.0      sv-storage-1a((***)   ) Pool0  WD-(***)  

0c.00.1      sv-storage-1a((***)   ) Pool0  WD-(***)  

0c.00.11     sv-storage-2a((***)   ) Pool0  WD-(***)  

0c.00.9      sv-storage-2a((***)   ) Pool0  (***)  

0c.00.10     sv-storage-2a((***)   ) Pool0  (***)  

0d.01.4      sv-storage-2b((***)   ) Pool0  (***)  

0d.01.1      sv-storage-1b((***)   ) Pool0  (***)  

0d.01.0      sv-storage-2b((***)   ) Pool0  (***)  

0d.01.7      sv-storage-1b((***)   ) Pool0  (***)  

0d.01.5      sv-storage-1b((***)   ) Pool0  (***)  

0d.01.3      sv-storage-1b((***)   ) Pool0  (***)  

0d.01.2      sv-storage-2b((***)   ) Pool0  (***)  

0d.01.10     sv-storage-2b((***)   ) Pool0  (***)  

0d.01.8      sv-storage-2b((***)   ) Pool0  (***)  

0d.01.6      sv-storage-2b((***)   ) Pool0  (***)  

0d.01.9      sv-storage-1b((***)   ) Pool0  (***)  

0d.01.11     sv-storage-1b((***)   ) Pool0  (***)  

1 ACCEPTED SOLUTION

ONLY150_321
7,217 Views

Hi,

please try to force the ownership command in advanced mode: disk remove_ownership -f 0d.01.4

View solution in original post

18 REPLIES 18
Public