Intel RS25DB080 with AXXRPFKSSD2: Eeprom Key Vault Crc mismatch.

[idata]

Dear Sir:

I got the new AXXRPFKSSD2(MM:919499,TA:G28865-002) from Intel SWR few days ago.

I plug it into my Intel RS25DB080, and noticed there are some unusual messages in TTY LOG.

f/w:INTEL 23.7.0-0037、Intel RAID Web Console 2 (12.05.03.00)、Intel driver(5.2.116.64)

MegaRAID FasPath & CacheCade Pro 2.0 works fine without any problems.

But, TTY LOG:

T7: EepromInit: Family=4f, SN=769c**000000

T7: EepromInit: Family=4f, SN=8db7**000000

T7: EepromKeyVaultRead: Key Vault Crc mismatch. 09/23/12 14:47:42: EepromKeyVaultRead: Key Vault Inconsistent or not present!09/23/12 14:47:42: EepromMfcDcmd: Serial Number Invalid!

LSIGETWIN:

T9: Primary RAID Key raw data:

T9: MFC data:

T9: vendorId/deviceId=1000/005b, subVendorId/subDeviceId=8086/9265

T9: OEM=8, SubOem=0, isRaidKeySecondary=0

T9: MFC Features:

T9: clusterDisable=1, disableSAS=0, maxDisks=0, enableRaid6=1, disableWideCache=0

T9: disableRaid5=0, enableSecurity=0, enableReducedFeatureSet=0

T9: enableCTIO=0, enableSnapshot=0, enableSSC=0, enableSSCWB=0, enableCacheOffload=0

T9: MFCD: sasAddr=500605b003c592e0

T9: Secondary RAID Key raw data:

T9: MFC data:

T9: vendorId/deviceId=0000/0000, subVendorId/subDeviceId=0000/0000

T9: OEM=8, SubOem=0, isRaidKeySecondary=1

T9: MFC Features:

T9: clusterDisable=0, disableSAS=0, maxDisks=0, enableRaid6=0, disableWideCache=0

T9: disableRaid5=0, enableSecurity=0, enableReducedFeatureSet=0

T9: enableCTIO=1, enableSnapshot=0, enableSSC=1, enableSSCWB=1, enableCacheOffload=0

T9: MFCD: sasAddr=5234567890abcde0

If I remove the AXXRPFKSSD2 from RS25DB080 and reboot, those "Eeprom Key Vault Crc mismatch" messages(in red) will be disappear.

Did Intel SWR send me the wrong AXXRPFKSSD2 for RS25DB080?

Should I ignore these messages?

Or, RMA the AXXRPFKSSD2 again?

Thanks for your help.

Regards,

[idata]

morlin,

I'm checking with our RAID engineering group to see what the messages associated with your AXXRPFKSSD2 installation mean.

Regards,

John

[idata]

morlin,

The function that prints this error is being called during a Premium Feature Key command from a driver/app (not from the RAID Firmware) if a secondary raid key is present. This print is not tied to any error within the controller and can be ignored.

Regards,

John

[idata]

OK~

Thanks for your answer about this.

But still hope it can be fixed in the near future.