EMC AX100i Release Notes - Page 12

Problem, Details, AX100SC, Hardware problems fixed in version 02.19.100.5.014 - transitioning

Page 12 highlights

Fixed problems Problem AX100SC, AX100SCi, AX100, AX100i - If the PSM LUN takes a checksum error while a single drive is degraded, then the storage system does not recover by using the third drive of the 3-way mirror.(130357) AX100SC, AX100SCi, AX100, AX100i - There are cases where a checksum error that is detected as part of a backfill pre-read on an MR3 will not be fixed. This can lead to "unexpected" checksum errors and sector reconstructed errors. (130360) AX100SC, AX100SCi, AX100, AX100i - Invalid event log messages are displayed due to memory corruption. The messages in question were Rebuild complete and Rebuild Aborted. (130418) AX100SC, AX100SCi, AX100, AX100i - A hot spare faulted while it was swapped in for a failed drive. A dual-SP panic occurred as a result of unbinding the hot spare while it was faulted. (130440) AX100SC, AX100SCi, AX100, AX100i - Rebuild not started from 0% after drive swapped. (130681) AX100SC, AX100SCi, AX100, AX100i - CMI does not specify "physically contiguous" when allocating memory, which causes DMA problems in iSCSI storage systems, and a storage-system panic can result within moments of being booted. (130897) AX100SC, AX100SCi, AX100, AX100i - Drive media errors can lead to PSM timeout panic. (129472) AX100SC, AX100SCi, AX100, AX100i - Addition of drive support for Short Stroke 250GB Hitatchi Kirufune II. Details Fixed in version: 02.19.100.5.018 Solution: Modified RAID drive to use the third mirror in this condition. Fixed in version: 02.19.100.5.018 Solution: Transition to recovery verify when a checksum error is detected in backfill data. Fixed in version: 02.19.100.5.018 Solution: Buffer size increased to 48 bytes. Fixed in version: 02.19.100.5.018 Solution: Clear the NEEDS_DB_REBUILD flag in the FRU table when the last LUN is unbound from the RAID group. This is not done in the current code base and it leads to an unnecessary database rebuild on an unbound FRU. Fixed in version: 02.19.100.5.018 Solution: Detect an invalid base FRU signature to mark the LUN as needing rebuild during an assign. Fixed in version: 02.19.100.5.018 Solution: CMIPCI driver now allocates memory from the correct memory pool. Fixed in version: 02.19.100.5.018 Solution: Modified the media error retry count and PSM timeout. Also eliminated the retry of the remapping of the same block multiple times. Fixed in version: 02.19.100.5.018 Solution: Added support for drive. Hardware problems fixed in version 02.19.100.5.014 Problem AX100SC, AX100SCi, AX100, AX100i - Incorrect part number displayed for 500 GB drive. Details Fixed in version: 02.19.100.5.014 Solution: Corrected text string for 500 GB drive part number. 12 EMC AX100-Series Integrated Management Software Release Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52

12
Fixed problems
EMC AX100-Series Integrated Management Software Release Notes
Problem
Details
AX100SC, AX100SCi, AX100, AX100i –
If the
PSM LUN takes a checksum error while a single
drive is degraded, then the storage system does
not recover by using the third drive of the 3-way
mirror.(130357)
Fixed in version
: 02.19.100.5.018
Solution
: Modified RAID drive to use the third mirror in this
condition.
AX100SC, AX100SCi, AX100, AX100i –
There
are cases where a checksum error that is detected
as part of a backfill pre-read on an MR3 will not be
fixed. This can lead to "unexpected" checksum
errors and sector reconstructed errors. (130360)
Fixed in version
: 02.19.100.5.018
Solution
: Transition to recovery verify when a checksum
error is detected in backfill data.
AX100SC, AX100SCi, AX100, AX100i –
Invalid
event log messages are displayed due to memory
corruption. The messages in question were
Rebuild complete
and
Rebuild
Aborted
. (130418)
Fixed in version
: 02.19.100.5.018
Solution
: Buffer size increased to 48 bytes.
AX100SC, AX100SCi, AX100, AX100i –
A hot
spare faulted while it was swapped in for a failed
drive. A dual-SP panic occurred as a result of
unbinding the hot spare while it was faulted.
(130440)
Fixed in version
: 02.19.100.5.018
Solution
: Clear the NEEDS_DB_REBUILD flag in the FRU
table when the last LUN is unbound from the RAID group.
This is not done in the current code base and it leads to an
unnecessary database rebuild on an unbound FRU.
AX100SC, AX100SCi, AX100, AX100i –
Rebuild
not started from 0% after drive swapped. (130681)
Fixed in version
: 02.19.100.5.018
Solution
: Detect an invalid base FRU signature to mark the
LUN as needing rebuild during an assign.
AX100SC, AX100SCi, AX100, AX100i -
CMI does
not specify "physically contiguous" when allocating
memory, which causes DMA problems in iSCSI
storage systems, and a storage-system panic can
result within moments of being booted. (130897)
Fixed in version
: 02.19.100.5.018
Solution
: CMIPCI driver now allocates memory from the
correct memory pool.
AX100SC, AX100SCi, AX100, AX100i –
Drive
media errors can lead to PSM timeout panic.
(129472)
Fixed in version
:
02.19.100.5.018
Solution
: Modified the media error retry count and PSM
timeout. Also eliminated the retry of the remapping of the
same block multiple times.
AX100SC, AX100SCi, AX100, AX100i –
Addition
of drive support for Short Stroke 250GB Hitatchi
Kirufune II.
Fixed in version
: 02.19.100.5.018
Solution
: Added support for drive.
Hardware problems fixed in version 02.19.100.5.014
Problem
Details
AX100SC, AX100SCi, AX100, AX100i –
Incorrect
part number displayed for 500 GB drive.
Fixed in version
: 02.19.100.5.014
Solution
: Corrected text string for 500 GB drive part number.