Skip to main content
NetApp Knowledge Base

Element upgrade fails when primary slice cannot move off of node because secondary does not exist

  1. Last updated
  2. Save as PDF
Views:
126
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
solidfire
Last Updated:

Applies to

NetApp Element software

Issue

  • The upgrade of a node running Element software cannot proceed if all the primary slices cannot be moved to their secondary slice hosted on a different node.  
  • sfinstall failure message in /var/log/sf-master.info on mNode

sfinstall[20600]: Not moving slice: slice_id: 23623 primary: 50 live_secondaries: [] db_version: 24 unknown_state: True
sfinstall[20600]: Unable to move all primaries, 1 unhealthy volumes.sfinstall[20600]: Please rerun the upgrade script and if the issue persists contact your technical support engineer.
sfinstall[20600]: Setting state=[FinishFailure] percent=[None] message=[Failure] details=None

 

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.