Troubleshooting - D-Link DSN-500 Software User's Manual

Problem Symptom
Software upgrade
appears to complete
quickly, but upgrade
is not performed;
error message on the
serial diagnostic
console:
*** Error reading
from socket.
Battery Failure
message in the
Event History Log
Power Supply Failure
message in the
Event History Log
Slower data transfer
performance than
expected

Troubleshooting

128 Chapter 10
Description and Probable Cause
If you have a firewall enabled, port 21 that
is used by the software upgrade process
may be blocked.
The battery backup module failed or fell
below the allowable minimum charge
level.
A power cable could have been
disconnected from the power supply unit
or the AC power receptacle, or the power
supply unit may have failed.
Mismatch of network configuration among
your host servers, network switches and
the xStack Storage system.
Other background tasks (such as Parity
volume initialization or a volume scan)
may be running.
Incorrect battery policy setting or a failed
battery.
Recommended Corrective Actions
Temporarily disable your Windows Firewall on your
host system so you can perform the software upgrade,
then re-enable the firewall after the software upgrade
has completed successfully. For more information,
see section 9.3.
For DSN-1100/2100/3200/3400 systems, verify that
the battery is properly connected to the controller.
For DSN-5000 series systems, replace the controller
module.
Check all power cable connections.
Contact D-Link Technical Support to request an RMA
for a replacement power supply.
Verify that all network connections are configured to
run at 1 Gbps, and that the MTU sizes are consistent
between the storage array and your network
infrastructure.
If the Volume type is Parity, wait until the initialization
process and other background tasks have completed.
Verify that the System Battery Policy is set to
Write-Back mode. Check if either Battery has failed,
as the default Battery Policy will switch from
Write-Back to Write-Through.
When using redundant controllers, if the Battery in
Controller-1 is "charging", this will force Controller-0
into Write-Through mode even though its Battery is
fully charged.
Verify that a battery failure has not occurred, or
replace the battery or controller module if it has failed.