• NVME drive missing after upgrade to 6.11.0-rc2


    richard@backslider.net
    • Solved Minor

    Short version: Previously had 6.10.3 installed, three nvme 1TB SSDs installed, post upgrade to 6.11.0-rc2, one dropped out. Backed out to 6.10.3, all three were available.

     

    Longer version:

    This motherboard has four NVME slots, currently three are in use, two connected through the chipset. Regardless of unraid version, all three are seen by the BIOS. Post upgrade, I attempted to move around the two P31 drives, slots #2 & #4, slots #3 & #4, slots #2 & #3, regardless one or the other would not be seen by Unraid (using 6.11.0-rc2).

     

    i7 12700k

    MSI z690-A Pro

    2x16GB DDR4 3200

    NVME #1: WD SN850 1TB <-- connected to CPU

    NVME #2: Hynix P31 1TB <-- connected to chipset

    NVME #3: Hynix P31 1TB <-- connected to chipset

     

    I'm happy to do another upgrade and provide any additional logs if necessary.

    megatron-diagnostics-6.10.3.zip megatron-diagnostics-6.11.0-rc2.zip

    • Upvote 1



    User Feedback

    Recommended Comments

    Further discussion here:

    https://unix.stackexchange.com/questions/711739/globally-duplicate-ids-for-nsid

     

    This device requires a "quirk" entry, which is a set of device model-specific flags that indicate limitations of one kind or another, that the kernel has to hack around.  Usually what happens is the solution (a patch) makes it's way to Linux 'mainline' where it's tested and then it gets integrated in the Linux 'stable' patch releases.  We'll keep an eye out for this.  For the time being you will need to downgrade unfortunately.

    • Like 1
    Link to comment

    Just to drop in to say I'm having this issue too, occurring on both RC1 and RC3, downgraded and everything came back. Hopefully there's a patch coming!

     

    Intel 11700

    ASUS Prime Z590-A

    2x SK Hynix P31 1TB NVMe

    Link to comment

    I have the same the issue where one of the NVMes (cache drives) does not show in RC3.

     

    Intel 12700k

    ASRock Z690 Pro RS

    2x Team Group MP33 M.2 2280 1TB NVMe

    Link to comment
    On 8/14/2022 at 12:06 AM, VideoVibrations said:

    2x Team Group MP33

    Same model is working for me, from a working release please post the output of:

    ls -l /dev/disk/by-id/

     

     

    Link to comment
    On 8/12/2022 at 11:11 AM, alancostello said:

    Just to drop in to say I'm having this issue too, occurring on both RC1 and RC3, downgraded and everything came back. Hopefully there's a patch coming!

     

    Intel 11700

    ASUS Prime Z590-A

    2x SK Hynix P31 1TB NVMe

    Just checking in to say RC4 is working for me now, both NVMe drives showing up!

    • Like 3
    Link to comment
    36 minutes ago, alancostello said:

    Just checking in to say RC4 is working for me now, both NVMe drives showing up!

    Can confirm, working for me with RC4 as well.

    • Like 2
    Link to comment

    Thank you for re-testing.  We'll wait awhile for this user to retest before marking 'solved':

     

    On 8/13/2022 at 4:06 PM, VideoVibrations said:

    I have the same the issue where one of the NVMes (cache drives) does not show in RC3.

    Link to comment
    On 9/4/2022 at 9:18 AM, VideoVibrations said:

    Unfortunately, the issue remains on RC4.  Diagnostics are attached.

    dangertoes-diagnostics-20220904-1217.zip

     

    I couldn't find a "quirk" patch for that device, but I found a similar one:

     

    	{ PCI_DEVICE(0x10ec, 0x5762),   /* ADATA SX6000LNP */
    		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
    				NVME_QUIRK_BOGUS_NID, },

     

    so I added this quirk in next release:

     

    	{ PCI_DEVICE(0x10ec, 0x5763),
    		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
    				NVME_QUIRK_BOGUS_NID, },

     

    (Your device is 0x10ec:0x5763).  Probably should work, but suggest you test first ;)

    Link to comment
    3 hours ago, limetech said:

     

    I couldn't find a "quirk" patch for that device, but I found a similar one:

     

    	{ PCI_DEVICE(0x10ec, 0x5762),   /* ADATA SX6000LNP */
    		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
    				NVME_QUIRK_BOGUS_NID, },

     

    so I added this quirk in next release:

     

    	{ PCI_DEVICE(0x10ec, 0x5763),
    		.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
    				NVME_QUIRK_BOGUS_NID, },

     

    (Your device is 0x10ec:0x5763).  Probably should work, but suggest you test first ;)

    Wow a custom fix just for me! I feel special.

    • Haha 3
    Link to comment

    Just wanted to say that I've also got this issue on the full release of 6.11.  Currently running 2x Toshiba 2TB Enterprise drives from eBay (per their info, sample drives), and only one is showing up after a reboot.  Likely not one of the bigger issues for most, but I'll have to downgrade.  Same message in the system logs:

     

    Sep 24 22:45:52 Home kernel: nvme nvme1: globally duplicate IDs for nsid 1

    Sep 24 22:45:52 Home kernel: nvme nvme1: VID:DID 1179:0119 model:TOSHIBA CONTROLLER MODEL NUMBER SAMPLE firmware:1CZA6064

     

    Device info from lspci:

     

    05:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation Device [1179:0119]
    06:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation Device [1179:0119]

    Edited by JaredC01
    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.