Hi Team,
One of my old NetApp Filers died on me and now i am left with several 1.8TB 10k SAS Disks that i want to use in another filer for Non- Production workloads.
But i am unable to use the disks in the second filer.
I don't care about the data on the disks. I just need them to be usable again.
The disks come from and encrypted filer and the second filer does not have encryption enabled.
Below outputs might help with identifying the issue.
FAS2240-Cluster::*> storage disk show -disk 1.0.18 -instance
Disk: 1.0.18
Container Type: broken
Owner/Home: HPSNETAPP-03 / HPSNETAPP-03
DR Home: -
Stack ID/Shelf/Bay: 1 / 0 / 18
LUN: 0
Array: N/A
Vendor: NETAPP
Model: X427_HCBFE1T8A10
Serial Number: 08VB22VA
UID: 5000CCA0:31141FBC:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000
BPS: 520
Physical Size: 1.64TB
Position: present
Checksum Compatibility: block
Aggregate: -
Plex: -
Paths:
LUN Initiator Side Target Side Link
Controller Initiator ID Switch Port Switch Port Acc Use Target Port TPGN Speed I/O KB/s IOPS
------------------ --------- ----- -------------------- -------------------- --- --- ----------------------- ------ ------- ------------ ------------
FAS2240-Cluster-01 0a 0 N/A N/A AO INU 5000cca031141fbe 5 6 Gb/S 0 0
Errors:
-
Apr 12 12:05:26 [FAS2240-Cluster-01:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0a.00.19; status security unknown key (0xe). Apr 12 12:05:26 [FAS2240-Cluster-01:disk.init.failure.error:error]: Disk 0a.00.19 failed initialization due to error 11.
FAS2240-Cluster::> storage encryption disk show
Disk Mode Data Key ID
-------- ---- ----------------------------------------------------------------
1.0.14 n/a n/a
1.0.15 n/a n/a
1.0.16 n/a n/a
1.0.17 n/a n/a
1.0.18 n/a n/a
1.0.19 n/a n/a
1.0.20 n/a n/a
1.0.21 n/a n/a
1.0.22 n/a n/a
1.0.23 n/a n/a
10 entries were displayed.
*> disk unfail 0a.00.2
Device 0a.00.2 was unfailed successfully.
Apr 12 12:49:09 [FAS2240-Cluster-01:disk.encryptNoSupport:error]: Detected encrypting disk 0a.00.14 but bootarg.storageencryption.support indicates that encrypting disks should not be present. 10 of 24 disks checked are encrypting disks.
If the disk has been previously failed by RAID, the disk may need to be removed from
the failed disk registry.
To see the disks in the registry:
>raid_config info showfdr
To delete a disk in the registry:
>raid_config info deletefdr
FAS2240-Cluster::*> storage disk show -broken
Original Owner: -
Checksum Compatibility: block
Drawer Usable Physical
Disk Outage Reason HA Shelf Bay /Slot Chan Pool Type RPM Size Size
--------------- ------------- --- ----- --- ------ ---- ------ ----- ------ -------- --------
1.0.14 init failed 0a 0 14 -/- B -
unknown - - 0B
1.0.15 init failed 0a 0 15 -/- B -
unknown - - 0B
1.0.16 init failed 0a 0 16 -/- B -
unknown - - 0B
1.0.17 init failed 0a 0 17 -/- B -
unknown - - 0B
1.0.18 init failed 0a 0 18 -/- B - SAS 10000 - 1.64TB
1.0.19 init failed 0a 0 19 -/- B -
unknown - - 0B
Original Owner: -
Checksum Compatibility: block
Drawer Usable Physical
Disk Outage Reason HA Shelf Bay /Slot Chan Pool Type RPM Size Size
--------------- ------------- --- ----- --- ------ ---- ------ ----- ------ -------- --------
1.0.20 init failed 0a 0 20 -/- B -
unknown - - 0B
1.0.21 init failed 0a 0 21 -/- B -
unknown - - 0B
1.0.22 init failed 0a 0 22 -/- B -
unknown - - 0B
1.0.23 init failed 0a 0 23 -/- B -
unknown - - 0B
Original Owner: FAS2240-Cluster-01
Checksum Compatibility: block
Drawer Usable Physical
Disk Outage Reason HA Shelf Bay /Slot Chan Pool Type RPM Size Size
--------------- ------------- --- ----- --- ------ ---- ------ ----- ------ -------- --------
1.0.2 failed 0a 0 2 -/- B FAILED SAS 10000 546.9GB 558.9GB
11 entries were displayed.
