ONTAP Discussions

localhost:disk.encryptAccessErr:error After power outage

CSTOCKDA
2,357 Views

Hello All,

 

8.2.4P1

 

I have an old 7 mode system that just has a power outage. Since coming up we get the following messages over and over again:

 

Oct 29 08:08:59 [localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0b.00.6; status security protocol reply fail (0xc).

Oct 29 08:08:59 [localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0a.00.11; status security protocol reply fail (0xc).

Oct 29 08:08:59 [localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0b.00.10; status security protocol reply fail (0xc).

Oct 29 08:08:59 [localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0a.00.9; status security protocol reply fail (0xc).

Oct 29 08:08:59 [localhost:disk.encryptAccessErr:error]: Unable to restore data access on encrypting disk 0b.00.8; status security protocol reply fail (0xc).

 

The keys have successfully loaded and been put back as we have the error message "kmip_init successfully loaded 2 kets from XX XX XX XX

 

We noticed when going into maintenance mode, there are no disks found in aggr, physically sees them in sysconfig -v and storage show disk -p but not the SN or ownership.

 

It looks like the disks cannot be recovered, has anyone had this before ?

The fact that we have rebooted and re-entered the information for the KMIP server must mean that it cannot be that.

 

 

1 ACCEPTED SOLUTION

Mjizzini
2,244 Views

I think the keys are not the right ones.  check the server, find the right key or if it is a virtual server,  try to revert the Kmip server to before the outage time...

 

You can try to set the bootargs to skip the communication with the external key manager(s) and set the authentication key and passphrase

How to boot NSE node when External Key Servers are down or unreachable

View solution in original post

1 REPLY 1

Mjizzini
2,245 Views

I think the keys are not the right ones.  check the server, find the right key or if it is a virtual server,  try to revert the Kmip server to before the outage time...

 

You can try to set the bootargs to skip the communication with the external key manager(s) and set the authentication key and passphrase

How to boot NSE node when External Key Servers are down or unreachable

Public