• [6.10.0-rc4] NVMe device name changed after upgrading


    JorgeB
    • Solved Minor

    Just upgraded one of my main servers from v6.9.2 to rc4 and one of the NVMe devices changed name and is "wrong", there's an extra underscore:

     

    image.png.a454b7b6a543cbd423c06350dc9b9571.png

     

    No big deal I though, just reset the pool and it will use the new name, but it doesn't take, after resetting the pool and starting the array the device mounts but it continues to show the device as "new", note the blue icon:

     

    image.thumb.png.5dbf64cefbd48d0acd8c4b443871768c.png

     

    And after stopping the array:

     

    image.thumb.png.da336ebcb7162f8ff65f0fa47e3ddf98.png

     

    So I need to reset the pool every time I stop the array, this doesn't happen with the other NVMe devices and if I go back top v6.9.2 this NVMe device name goes back to how it was.

     

     

     

    tower1-diagnostics-20220423-1417.zip

     




    User Feedback

    Recommended Comments



    12 hours ago, limetech said:

    it means you'll have to edit your cfg files to remove that extra underscore...

     

    That's fine, and hopefully worth the trouble to prevent similar issues when it goes stable and more users update.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.