Jump to content
  • NVMe Cache drives inconsistent in 6.11


    bwitting
    • Annoyance

    My config contains 2x T-Create NVMe 1TB drives. I have each in its own Cache Pool. On 6.10.3, the system sees both drives, and everything works great. After upgrading to 6.11, the system will only see 1 of the 2 drives. What's odd is that if I reboot the system multiple times, which drive shows up will change. In order to verify that this is in fact a 6.11 issue, I created a new 6.10.3 flash drive, and it sees both NVMe drives every boot, and a clean 6.11 flash drive will only show one.

    Hardware:
    Ryzen 9 5950X

    Asrock X570 TACHI 

    64GB RAM


    Diagnostics attached. Let me know if any ideas as I would like to be able to upgrade to 6.11 eventually. Marking as urgent due to full system-breaking bug requiring roll-back.

    orthanc-diagnostics-20220924-2211.zip




    User Feedback

    Recommended Comments

    On 9/25/2022 at 3:38 AM, JorgeB said:

    Likely this issue, you'll need a kernel "quirck".

    Yes, looks like that is exactly what this is.  So not an Unraid issue, but an issue with the drive reporting.  I fixed the issue for myself by swapping one of the 1TB NVMe drives with another brand.  I upgraded again, and everything is working correctly.

    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.

×
×
  • Create New...