メインコンテンツへスキップ

システムの再初期化後にローカルディスクが見つかりません

Views:
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
HW
Last Updated:

環境

AFF-A250

問題

  • すべてのデータを移動および削除
  • (4)  Clean configuration and initialize all disksHAペアを再利用するために を開始しました
  • 手順の実行中にノードが停止し、次のエラーメッセージが表示されます。
[localhost:mgr.boot.unequalDist:error]: Warning: Unequal number of disks will be used for auto-partitioning of the root aggregate on the local system and HA partner. The local system will use 7 disks but the HA partner will use 0 disks. To correct this situation, boot both controllers into maintenance mode and remove the ownership of all disks.
FWU 2nd trigger point
FWU has no post firmware update action registered.
fm_run0: no local disks found & OFW channel is not up.
  • メンテナンスモードでFAILED と表示されるすべてのドライブ
*> disk show -v
Local System ID: 123456789
DISK   OWNER      POOL  SERIAL NUMBER...
----   -----     -----  -------------...
0n.0   FAILED     Block        ...
...                      
0n.23  FAILED     Block          
  • unfail の試行が失敗し、次のメッセージが表示されます。 
*> disk unfail 0n.0
[localhost:nse.op.failed:error]: Control failure on self-encrypting drive 0n.0; security provider: Locking, authority: User1, during operation "opal_lock_unlock_data_band_sm".
Failure bytes for unfail were not written due to error 12;                                
[localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0n.0; status security unknown key (0xe).
[localhost:disk.init.failure.error:error]: Drive 0n.0 failed initialization due to error 11, sense code(7 20 2 86).   
If failure area has reached its capacity, it may be cleared by reloading disk firmware.                 
If the disk has been previously failed by RAID, the disk may need to be removed from                   
the failed disk registry.                                                  
with:                                                             
*> disk encrypt show 0n.0                                                  
Disk    Data Key ID                            Locked?                   
---------- ---------------------------------------------------------------- -------                   
0n.0    000000000000000002000000000001004ABCDEFGHIJKLMNOPQRSTUVWXYZ12345 Yes                      
Note: When not in advanced privilege, the output above might be stale for drives                     
owned by the HA partner unless it has been taken over by this node.                            

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.