Unsolved

This post is more than 5 years old

3 Posts

2007

September 5th, 2017 08:00

Event Number a3f | Spare request failed because a hot spare is already swapped in

Hello everyone,

Recently we had a drive fail in our VNX 5300. It has since been replaced by our warranty provider. However, we are struggling to understand one of the logged messages generated by the array - specifically, we would like to know if this is to be expected during a drive failover/hot spare swap, or if it is reason for concern. The message was as follows (serial blanked for security):

This message was generated by the EMC VNX 5300 storage array because a warning, error or critical condition occurred. Please review the message for any actionable items.

Time Stamp 08/31/17 04:21:08 | Severity Critical Error | Host A-IMAGE | Event Number a3f | Storage Array APM00000000000 |

Message: Spare request failed because a hot spare is already swapped in.  You cannot proactively spare a drive that is already swapped in.

This message was generated by the EMC VNX 5300 storage array because a warning, error or critical condition occurred. Please review the message for any actionable items.

Time Stamp 08/31/17 04:21:08 | Severity Warning | Host A-IMAGE | Event Number 801 | Storage Array APM00000000000 |

Message: Soft SCSI Bus Error

This message was generated by the EMC VNX 5300 storage array because a warning, error or critical condition occurred. Please review the message for any actionable items.

Time Stamp 08/31/17 04:22:06 | Severity Warning | Host B-IMAGE | Event Number 820 | Storage Array APM00000000000 |

Message: Soft Media Error

There are about ten additional log entries in the message regarding soft media/soft SCSI bus errors.

The same array had a drive fail about three weeks prior and the hot spare operation was initiated manually; it is entirely possible that the SA (myself) missed a step in the process. I hope that is not the case, but any help understanding the source of this error would be most appreciated!

4.5K Posts

September 22nd, 2017 08:00

That error appears to be normal when the hot spare has been manually engaged. Further errors on the failed disk would attempt to swap to the hot spare, but it's already engaged, therefore the message generated.

glen

3 Posts

September 22nd, 2017 09:00

Thank you Glen!

No Events found!

Top