Skip to main content
NetApp Knowledge Base

E-series can not login by System manager with Data could not be loaded from the storage array

  1. Last updated
  2. Save as PDF
Views:
29
Visibility:
Public
Votes:
0
Category:
e-series-santricity-storage-manager
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • SANtricity System Manager

Issue

    • The customer reported that the WebUI (System Manager) for the NetApp E-series storage system was inaccessible via both management IPs. 
      The error displayed was:

    Data could not be loaded from the storage array. One possible cause is the object on which you were performing the operation no longer exists. Other possible causes include network issues, inability to communicate with the controller, or loss of power to the storage array.

    clipboard_51319cd3-5fea-4e86-8538-81a0f2faaaab.png

    • Attempts to restart web services and controllers do not restore access.
    • And stagger reboot do not restore access


    - The WEB-SERVER-TRACE.LOG in both controllers report many "The connection to the device has failed.", ClusterManager and ObjectBundle cannot become available due to timeout

    2026-04-08 05:43:20,765 WARN [ActiveMQ Task-1] o.a.a.t.f.FailoverTransport [FailoverTransport.java:1109] [requestId=0, deviceId=N/A] Failed to connect to [nio://dom0-alt:61616] after: 1 attempt(s) with Connection refused, continuing to retry.
    2026-04-08 05:43:20,777 INFO [Storage Device NIO Selector Thread: sam device selector] c.n.e.a.d.StorageDevice [StorageDevice.java:1657] [requestId=0, deviceId=N/A] Error connecting to device 1 to validate password
    java.net.ConnectException: Connection refused
     at java.base/sun.nio.ch.Net.pollConnect(Native Method)
     at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
     at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
     at devmgr.api.rpc.NIORPCClient.handleConnectSocketSignal(NIORPCClient.java:445)
     ... 3 common frames omitted
    Wrapped by: com.ni.eseries.aa.devicemgt.model.exceptions.SanModelException: The connection to the device has failed.
     at com.ni.eseries.aa.devicemgt.model.exceptions.SanModelException.mkDevlibException(SanModelException.java:299)
     at com.ni.eseries.aa.devicemgt.connection.DeviceConnectionPool$1.onComplete(DeviceConnectionPool.java:189)
     at com.ni.eseries.aa.devicemgt.task.Task.onError(Task.java:103)
     at com.ni.eseries.aa.devicemgt.task.TaskController$1.onError(TaskController.java:148)
     at com.ni.eseries.aa.devicemgt.task.NioCallbackToTaskCallbackAdapter.onError(NioCallbackToTaskCallbackAdapter.java:37)
     at devmgr.api.rpc.NIORPCClient.handleConnectSocketSignal(NIORPCClient.java:461)
     at devmgr.api.rpc.SelectManager.checkChannels(SelectManager.java:116)
     at devmgr.api.rpc.SelectManager.monitor(SelectManager.java:83)
     at java.base/java.lang.Thread.run(Unknown Source)
    2026-04-08 05:43:20,875 INFO [PrioritizedBlockingPool-1] c.n.e.a.d.StorageDevice [StorageDevice.java:427] [requestId=0, deviceId=N/A] Adding 1 into the storage system database....2026-04-08 05:54:47,480 INFO [NonBlockingPool-1] c.n.e.a.d.c.FTClient [FTClient.java:330] [requestId=0, deviceId=N/A] Device 1: Controller: null: Retries exceeded for Procedure getChangeState, last error: The connection to the device has failed.
    2026-04-08 05:54:52,362 ERROR [PrioritizedBlockingPool-5] c.n.e.a.d.AutoDriveFwUpgradeManager [AutoDriveFwUpgradeManager.java:254] [requestId=0, deviceId=N/A] Timed out waiting for ClusterManager to become healthy, continuing.
    Caller+0  at com.ni.eseries.aa.devicemgt.AutoDriveFwUpgradeManager.waitForFullBoot(AutoDriveFwUpgradeManager.java:254)
    Caller+1  at com.ni.eseries.aa.devicemgt.AutoDriveFwUpgradeManager.lambda$processStartOfDay$0(AutoDriveFwUpgradeManager.java:80)
    Caller+2  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
    Caller+3  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    Caller+4  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    ....2026-04-08 05:58:52,455 ERROR [PrioritizedBlockingPool-5] c.n.e.a.d.AutoDriveFwUpgradeManager [AutoDriveFwUpgradeManager.java:403] [requestId=0, deviceId=N/A] Timed out waiting for an ObjectBundle to become available
    Caller+0  at com.ni.eseries.aa.devicemgt.AutoDriveFwUpgradeManager.getObjectBundle(AutoDriveFwUpgradeManager.java:403)
    Caller+1  at com.ni.eseries.aa.devicemgt.AutoDriveFwUpgradeManager.getAllDrives(AutoDriveFwUpgradeManager.java:380)
    Caller+2  at com.ni.eseries.aa.devicemgt.AutoDriveFwUpgradeManager.lambda$processStartOfDay$0(AutoDriveFwUpgradeManager.java:88)
    Caller+3  at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
    Caller+4  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    Sign in to view the entire content of this KB article.

    New to NetApp?

    Learn more about our award-winning Support

    NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.