Release Notes

Table 11. Issues resolved in Storage Center 7.5.1 (continued)
Issue Functional area Description
SCOS-59479 Hardware SCv2000 Series and SC4020 storage systems running Storage Center 7.4.x
might be unable to initialize replacement batteries or charge batteries.
SCOS-62211 Live Volume and
Replication
Live Volumes might not be protected when connectivity to the tiebreaker service
is down.
SCOS-62018 Live Volume and
Replication
A storage system might experience unnecessary Live Volume backend-error
swaps caused by deduplication memory allocation failures.
SCOS-61408 Live Volume and
Replication
A non-recoverable IORP failure on a Live Volume might result in a back-end error
swap role that is initiated for peer side volume access and recovery.
SCOS-61357 Live Volume and
Replication
If the system monitor failover did not complete successfully after a controller
failover, remote disks might be unavailable and Storage Center cannot create
replications on the surviving controller.
SCOS-60819 Live Volume and
Replication
Storage Center might be unable to re-enable automatic failover on a Live Volume
if automatic failover was disabled on the Live Volume while connectivity to the
tiebreaker service was down.
SCOS-60092 Live Volume and
Replication
Auto Failover enabled Live Volumes may go offline during a Storage Center
firmware upgrade in the event of unbalanced failover during the upgrade.
SCOS-59974 Live Volume and
Replication
When an external disk is deleted from a Storage Center during cross-platform
replication, configuration changes might cause the controller to reset, but the
controller is prevented from fully initializing during the reboot.
SCOS-59299 Live Volume and
Replication
When a server running Windows 2016 Server or later is rebooted, the server
might lose access to a Live Migrated volume because of changes to the target
port group (TPG) IDs that are sent from Storage Center.
SCOS-62777 Storage Management A partially destroyed secondary storage device might cause lost space detection
to function incorrectly.
SCOS-62498 Storage Management Activating the inactive histories on the lead controller of a storage system might
result in a staggered outage that causes the controllers to deadlock during
volume activation.
SCOS-62470 Storage Management A controller might fail to boot if Remote Chap Initiators are created on every port
in the fault domain instead of just the control port.
SCOS-62131 Storage Management Copy-Mirror-Migrate (CMM) schedules might fail on source volumes that are
owned by the peer controller.
SCOS-61862 Licensing,
SupportAssist, and
Updating
If the iDRAC login credentials have been changed on an SC5020 or SC5020F
storage system that is running Storage Center 7.4.20 or being updated to
Storage Center 7.4.20, the storage system controllers might fail to boot.
SCOS-61592 Storage Management A controller might reset when a snapshot attach is performed on a view volume
after the size of the parent volume is expanded.
SCOS-61082 Storage Management A controller might reset because of a segmentation fault caused by a corruption
of the CA IP Object List.
SCOS-61042 Storage Management A controller might reset with a signal for memory access violation when a
secondary storage object is activated, failed over during activation, and then
deactivated.
SCOS-60805 Storage Management Distributed Spare Optimizer might fail to run if it is enabled on a storage system
during a Storage Center update.
SCOS-60788 Storage Management During a system restripe cycle, Storage Center might encounter a loop that
selects a pagepool device to prune as excess, prunes the device, and then re-
creates the device after it is pruned.
SCOS-60784 Storage Management In rare cases, two progression cycles might run simultaneously after controller
failover.
SCOS-60780 Storage Management In rare cases, data progression might stall due to a missed data progression
completion.
7