Unsolved
This post is more than 5 years old
18 Posts
0
1138
CX4-120 showing FRU signature failure error 0x7a6
We have a CX4-120 and we replaced a 2 TB failed drive with PN 005049061PWR with revision A3FB/2159. The drive was in the rebuliding state for more than 4 days and in the 4th day, the Hostspare drive failed.
Below is the event that I found in the log which was pointing to the drive that was just replaced and followed by the usual disk drive failure event on the Hotspare drive.
0x7a6 Internal information only. Drive removed, seen by peer SP. Removed either physically, via software or a fru signature failure.
As per the above message, We suspected the replaced drive revision compatibility with the existing drives which were with PN 005049058 with revision A34E/1534
When we replaced the drive again with a different PN and when we reseated the Hotspare, the Hotspare drive came healthy and the replaced started rebuilding. The drive is rebuliding very slowly though.
As per the compatibility matrix, the PN 005049061PWR is compatible.
Is there any other reason why this issue would have happened? Or is there any incompatibilty with the drive PN and the revision?
Regards,
Sheron1
224 Posts
0
March 6th, 2015 09:00
Prassi,
The drives you used to replace the faulted ones, are they new drives or taken from another array or something?
This alert you mentioned, which drive caused this event, the original one that failed or the hotspare or the new one you replaced with?
The rebuilding does not depend on the size of the drive, it depends on the size of the RG.
Please check the compatibility of the drive as I do not have the access to it at the moment.
To understand what went you can check the events history.
Regards,
Sheron.
Raj10
37 Posts
0
March 8th, 2015 11:00
Hi Prassi,
I checked the compatibility of part # 005049061PWR with CX4 arrays and its compatible.
As far as the alert "0x7a6 Internal information only. Drive removed, seen by peer SP. Removed either physically, via software or a fru signature failure." is concerned, it's generates when a drive fault happens. It's normal.
Also, the drive part number mentioned is SATA drive which is 7.2K RPM and rebuilding being slow mentioned depends on lot of things like how many drives are there in faulted Raid Group, size of the lun etc.
If you want a more detailed health check on the array, you can generate fresh set of sp collects and open a service request to perform a health check on the array.
Regards,
Rajendra