Skip to main content
NetApp Knowledge Base

SG6000 continuously reboots with message "hostbyte=DID_NO_CONNECT"

  1. Last updated
  2. Save as PDF
Views:
854
Visibility:
Public
Votes:
1
Category:
storagegrid
Specialty:
sgrid
Last Updated:

​ ​

Applies to

  • NetApp StorageGrid SG6000
  • Firmware Version 11.3 

Issue

  • SG6000 is in a boot loop
  • Path loss to backend storage
  • The following events are seen in the virtual console or serial connection after each reboot loop: 

sd 16:0:0:251: [sdp] Synchronizing SCSI cache
sd 16:0:0:251: [sdp] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
scsi 16:0:0:251: rdac: Detached
sd 16:0:0:252: [sdq] Synchronizing SCSI cache
sd 16:0:0:252: [sdq] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
scsi 16:0:0:252: rdac: Detached
sd 16:0:0:253: [sdr] Synchronizing SCSI cache
sd 16:0:0:253: [sdr] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
scsi 16:0:0:253: rdac: Detached 
sd 16:0:0:254: [sds] Synchronizing SCSI cache
sd 16:0:0:254: [sds] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
scsi 16:0:0:254: rdac: Detached
mlx5_core 0000:af:00.1: Shutdown was called
mlx5_core 0000:af:00.0: Shutdown was called

 

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.