• [6.7.x] Unable to Detect 2 NVME Drives (same model)


    drkCrix
    • Urgent

    I am having this issue with 2 Adata XPG GAMMIX S5 256GB drives.  Both are seen in the BIOS but I see the following during system start up.

     

    Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2018-05.com.example:nvme:nvm-subsystem-OUI00E04C).

    Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: Removing after probe failure status: -22

     

    Further digging I came across this *NEW* https://lkml.org/lkml/2019/7/15/57

     

    Date:  Mon, 15 Jul 2019 00:11:49 -0700

    From:  Misha Nasledov <>

    Subject:  [PATCH] NVME: ignore subnqn for ADATA SX6000LNP

     

    The ADATA SX6000LNP NVMe SSDs have the same subnqn and, due to this, a system with more than one of these SSDs will only have one usable.

    [ 0.942706] nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2018-05.com.example:nvme:nvm-subsystem-OUI00E04C).

    [ 0.943017] nvme nvme1: Removing after probe failure status: -22

    # lspci | grep Non-Volatile

    02:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5762] (rev 01)

    71:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5762] (rev 01)

     

    There are no firmware updates available from the vendor, unfortunately. Applying the NVME_QUIRK_IGNORE_DEV_SUBNQN quirk for these SSDs resolves the issue, and they all work after this patch:

    # nvme list

    /dev/nvme0n1 2J1120050420 ADATA SX6000LNP [...]

    /dev/nvme1n1 2J1120050540 ADATA SX6000LNP [...]

     

    Signed-off-by: Misha Nasledov <[email protected]>

    ---

    drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c

    index 189352081994..762ae6927689 100644

    --- a/drivers/nvme/host/pci.c

    +++ b/drivers/nvme/host/pci.c

    @@ -3005,6 +3005,8 @@ static const struct pci_device_id nvme_id_table[] = {

                           { PCI_VDEVICE(INTEL, 0x5845), /* Qemu emulated controller */

                                           .driver_data = NVME_QUIRK_IDENTIFY_CNS |

                                                                           NVME_QUIRK_DISABLE_WRITE_ZEROES, },

                        + { PCI_DEVICE(0x10ec, 0x5762), /* ADATA SX6000LNP */

                                         + .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN, },

                           { PCI_DEVICE(0x1bb1, 0x0100), /* Seagate Nytro Flash Storage */

                                            .driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, },

                           { PCI_DEVICE(0x1c58, 0x0003), /* HGST adapter */

    --

    Misha Nasledov <[email protected]> GPG: A063 B99A 2BD3 2D48 F2D7 8E68 0F27 4D21 948F 8F06

     

     

    and this (specific for the Adata drives that use the Realtek Controller) If I need to get more info please let me know

     

    Running  lspci | grep Non-Volatile

     

    I get


    01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5762 (rev 01)
    23:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5762 (rev 01)

     

    In a nut shell, if the system has 2 similar drives that don't have a unique NQN the system assumes its a duplicate and doesn't use it.

     

    Cheers,

     

    Chris

     

     




    User Feedback

    Recommended Comments

    There are no comments to display.



    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.