Skip to main content
NetApp Knowledge Base

Cannot start StorageGrid node because block device does not exist

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

Applies to

  • NetApp StorageGRID  11.3+
  • StorageGRID node deployed in docker containers on Linux host

Issue

  • StorageGRID node is not started automatically after Linux host reboots abnormally.
  • Node containers report "not-running" and can't start due to errors.
  • Cannot start StorageGrid node manually because block device does not exist.

Example output:

# storagegrid node start
ERROR: /etc/storagegrid/nodes/<node name>.conf contains errors; cannot start <node name>
Run 'storagegrid node validate <node name>' and correct any errors, then try again.
# storagegrid node validate <node name>
Confirming existence of node <node name>... PASSED
Checking configuration file /etc/storagegrid/nodes/<node name>.conf for node <node name>...
  ERROR:   <node name>: BLOCK_DEVICE_VAR_LOCAL = /dev/mapper/<node name>
           <node name>: /dev/mapper/<node name> does not exist
 

 

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.