You are not logged in.

Pages: 1

#1 2025-04-08 19:57:26

860lacov
Member
Registered: 2020-05-02
Posts: 489

The system does not detect the drive in the NVMe enclosure.

I have an issue with an NVMe enclosure.
It is based on JHL7440 and RTL9210 chipsets.

The laptop is a Lenovo P14s with USB4, and if I am not mistaken, this port should be compatible with Thunderbolt.

When I connect the drive in the enclosure to the computer, a window appears with a message about the need for Thunderbolt authorization (KDE Plasma).
In the system settings (KDE Plasma), the device is visible as connected and authorized.

tblist shows:

Domain 0 Route 2: 0025:0001 inateck FE2029
Type: Router
Speed (Rx/Tx): 40/40 Gb/s
Authorized: Yes
Generation: Thunderbolt 3
NVM version: 67.0
sudo journalctl -xe | grep -i "thunderbolt|nvme"
[sudo] password for user jm:
Journal file /var/log/journal/ee5296cc61304500ac9ef076d73d1d33/system@0006278510ac5a0b-af48c4529c0b1b14.journal~ is truncated, ignoring file.
Apr 08 21:33:07 p14s kernel: nvme nvme0: using unchecked data buffer
Apr 08 21:33:33 p14s kernel: thunderbolt 0-0:2.1: new retimer found, vendor=0x1da0 device=0x8830
Apr 08 21:33:34 p14s kernel: thunderbolt 0-2: new device found, vendor=0x25 device=0x1
Apr 08 21:33:34 p14s kernel: thunderbolt 0-2: inateck FE2029
Apr 08 21:33:34 p14s kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Apr 08 21:33:34 p14s kernel: nvme nvme1: pci function 0000:06:00.0
Apr 08 21:33:34 p14s kernel: nvme 0000:06:00.0: enabling device (0000 -> 0002)
cat /sys/bus/thunderbolt/devices/domain0/security
user

Regarding the above, Arch Wiki states that the security level should be set to at least "secure," but I have not found such an option in the BIOS.

Offline

#2 2025-04-20 09:42:04

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

I have now another enclosure for testing.
It has asm2464PD chip.

After first connection to the laptop USB4 port there was a popup with an authorisation options (only for now or persistent).
I selected only for now and I was able to connect the drive in Dolphin. It was connected as an NVME drive.

And that was the one and only time when the drive worked as it should.

after disconnetcing and connecting enclosure again the LED on the enclosure is blinking.
lsblk showsk only internal drive.

boltctl 
 ● ASMedia 246x
   ├─ type:          peripheral
   ├─ name:          246x
   ├─ vendor:        ASMedia
   ├─ uuid:          0f534c17-3032-19dd-ffff-ffffffffffff
   ├─ generation:    USB4
   ├─ status:        authorized
   │  ├─ domain:     979e3804-b079-25e4-ffff-ffffffffffff
   │  ├─ rx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  ├─ tx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  └─ authflags:  none
   ├─ authorized:    nie, 20 kwi 2025, 09:29:41
   ├─ connected:     nie, 20 kwi 2025, 09:29:40
   └─ stored:        nie, 20 kwi 2025, 09:29:41
      ├─ policy:     iommu
      └─ key:        no

I tried everything I could find.
For example:
After:
sudo boltctl forget 0f534c17-3032-19dd-ffff-ffffffffffff
and
sudo boltctl enroll   0f534c17-3032-19dd-ffff-ffffffffffff --policy=manual

When I connect the enclosure to the laptop the green led is blinkind for a while and after few seconds it is changed to white continous light.
lsblk shows the drive in enclosure but as sda/sda1 so when I mount it it works only in 10Gbps mode (instead of 40)

I tried
sudo boltctl enroll   0f534c17-3032-19dd-ffff-ffffffffffff --policy=auto but with this setting there is blinking green led and no drive in lsblk
And when dr led is blinking boltclt shows that the drive is connected and authorized

lspci -nn | grep -i asmedia
04:00.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:2463]
05:00.0 PCI bridge [0604]: ASMedia Technology Inc. Device [1b21:2463]
sudo dmesg -wT | grep -iE 'nvme|PCI bridge'
[sudo] hasło użytkownika jm: 
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.1: PCI bridge to [bus 64]
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.2: PCI bridge to [bus 65]
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.3: PCI bridge to [bus 66]
[nie 20 kwi 10:51:33 2025] pci 0000:00:02.1: PCI bridge to [bus 01]
[nie 20 kwi 10:51:33 2025] pci 0000:00:02.2: PCI bridge to [bus 02]
[nie 20 kwi 10:51:33 2025] pci 0000:00:02.4: PCI bridge to [bus 03]
[nie 20 kwi 10:51:33 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 10:51:33 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 10:51:33 2025] pci 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.1: PCI bridge to [bus 64]
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.2: PCI bridge to [bus 65]
[nie 20 kwi 10:51:33 2025] pci 0000:00:08.3: PCI bridge to [bus 66]
[nie 20 kwi 10:51:34 2025] nvme 0000:03:00.0: platform quirk: setting simple suspend
[nie 20 kwi 10:51:34 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 10:51:34 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 10:51:34 2025] nvme nvme1: pci function 0000:03:00.0
[nie 20 kwi 10:51:34 2025] nvme nvme1: D3 entry latency set to 10 seconds
[nie 20 kwi 10:51:34 2025] nvme nvme0: missing or invalid SUBNQN field.
[nie 20 kwi 10:51:34 2025] nvme nvme0: D3 entry latency set to 8 seconds
[nie 20 kwi 10:51:34 2025] nvme nvme1: 16/0/0 default/read/poll queues
[nie 20 kwi 10:51:34 2025]  nvme1n1: p1 p2
[nie 20 kwi 10:51:34 2025] nvme nvme0: 16/0/0 default/read/poll queues
[nie 20 kwi 10:51:34 2025]  nvme0n1: p1
[nie 20 kwi 10:51:53 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 10:51:53 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 10:51:53 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 10:51:53 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 10:51:53 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 10:51:53 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 10:51:53 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 10:51:53 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 10:51:53 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 10:51:53 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 10:52:34 2025] nvme nvme1: using unchecked data buffer
[nie 20 kwi 10:58:45 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 10:58:45 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 10:58:45 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 10:58:45 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 10:58:45 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 10:58:45 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 10:58:45 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 10:58:45 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 10:58:45 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 10:58:45 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:09:16 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:09:16 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:09:16 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:09:16 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:09:16 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:09:16 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:09:16 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:09:16 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:09:16 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:09:16 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:17:25 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:17:25 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:17:25 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:17:25 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:17:25 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:17:25 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:17:25 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:17:25 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:17:25 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:17:25 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:20:10 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:20:10 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:20:10 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:20:10 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:20:10 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:20:10 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:20:10 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:20:10 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:20:10 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:20:10 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:26:23 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:26:23 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:26:23 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:26:23 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:26:23 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:26:23 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:26:23 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:26:23 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:26:23 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:26:23 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:29:05 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:29:05 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:29:05 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:29:05 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:29:05 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:29:05 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:29:05 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:29:05 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:29:05 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:29:05 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:29:41 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:29:41 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:29:41 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:29:41 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:29:41 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:29:41 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:29:41 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:29:41 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:29:41 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:29:41 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)
[nie 20 kwi 11:40:43 2025] pci 0000:04:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:40:43 2025] pci 0000:05:00.0: PCI bridge to [bus 00]
[nie 20 kwi 11:40:43 2025] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[nie 20 kwi 11:40:43 2025] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[nie 20 kwi 11:40:43 2025] pci 0000:05:00.0: PCI bridge to [bus 06]
[nie 20 kwi 11:40:43 2025] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[nie 20 kwi 11:40:43 2025] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[nie 20 kwi 11:40:43 2025] nvme 0000:06:00.0: platform quirk: setting simple suspend
[nie 20 kwi 11:40:43 2025] nvme nvme0: pci function 0000:06:00.0
[nie 20 kwi 11:40:43 2025] nvme 0000:06:00.0: enabling device (0000 -> 0002)

Offline

#3 2025-04-20 22:21:54

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

Have you at any point attempted a rescan?
https://wiki.archlinux.org/title/Thunde … registered

Run "dmesg -W", plug the device and post the tail that generates.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#4 2025-04-21 10:42:13

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

Have you at any point attempted a rescan?
https://wiki.archlinux.org/title/Thunde … registered

Run "dmesg -W", plug the device and post the tail that generates.

I tried to rescan many times.
I did:
Automatic PCI bus rescan


[  156.251266] thunderbolt 0-0:2.1: new retimer found, vendor=0x1da0 device=0x8830
[  156.366426] thunderbolt 0-2: new device found, vendor=0xb8 device=0x2463
[  156.366435] thunderbolt 0-2: ASMedia 246x
[  156.799005] pcieport 0000:00:04.1: pciehp: Slot(0): Card present
[  156.799020] pcieport 0000:00:04.1: pciehp: Slot(0): Link Up
[  156.922259] pci 0000:04:00.0: [1b21:2463] type 01 class 0x060400 PCIe Switch Upstream Port
[  156.922307] pci 0000:04:00.0: PCI bridge to [bus 00]
[  156.922323] pci 0000:04:00.0:   bridge window [io  0x0000-0x0fff]
[  156.922331] pci 0000:04:00.0:   bridge window [mem 0x00000000-0x000fffff]
[  156.922349] pci 0000:04:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[  156.922375] pci 0000:04:00.0: enabling Extended Tags
[  156.922527] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
[  156.922892] pci 0000:04:00.0: Adding to iommu group 7
[  156.924221] pci 0000:04:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[  156.924309] pci 0000:05:00.0: [1b21:2463] type 01 class 0x060400 PCIe Switch Downstream Port
[  156.924339] pci 0000:05:00.0: PCI bridge to [bus 00]
[  156.924347] pci 0000:05:00.0:   bridge window [io  0x0000-0x0fff]
[  156.924350] pci 0000:05:00.0:   bridge window [mem 0x00000000-0x000fffff]
[  156.924363] pci 0000:05:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[  156.924380] pci 0000:05:00.0: enabling Extended Tags
[  156.924481] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
[  156.924677] pci 0000:05:00.0: Adding to iommu group 7
[  156.924745] pci 0000:04:00.0: PCI bridge to [bus 05-63]
[  156.924760] pci 0000:05:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[  156.924863] pci 0000:06:00.0: [144d:a808] type 00 class 0x010802 PCIe Endpoint
[  156.924938] pci 0000:06:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[  156.925226] pci 0000:06:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:04.1 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[  156.925426] pci 0000:06:00.0: Adding to iommu group 7
[  156.927237] pci 0000:05:00.0: PCI bridge to [bus 06-63]
[  156.927252] pci_bus 0000:06: busn_res: [bus 06-63] end is updated to 06
[  156.927258] pci_bus 0000:05: busn_res: [bus 05-63] end is updated to 06
[  156.927265] pcieport 0000:00:04.1: Assigned bridge window [mem 0xc00000000-0x1bffffffff 64bit pref] to [bus 04-63] cannot fit 0x100000 required for 0000:05:00.0 bridging to [bus 06]
[  156.927268] pci 0000:05:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] to [bus 06] requires relaxed alignment rules
[  156.927270] pcieport 0000:00:04.1: Assigned bridge window [mem 0x60000000-0x77ffffff] to [bus 04-63] cannot fit 0x100000 required for 0000:05:00.0 bridging to [bus 06]
[  156.927271] pci 0000:05:00.0: bridge window [mem 0x00000000-0x000fffff] to [bus 06] requires relaxed alignment rules
[  156.927273] pcieport 0000:00:04.1: Assigned bridge window [mem 0xc00000000-0x1bffffffff 64bit pref] to [bus 04-63] cannot fit 0x100000 required for 0000:04:00.0 bridging to [bus 05-06]
[  156.927275] pci 0000:04:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] to [bus 05-06] requires relaxed alignment rules
[  156.927276] pcieport 0000:00:04.1: Assigned bridge window [mem 0x60000000-0x77ffffff] to [bus 04-63] cannot fit 0x100000 required for 0000:04:00.0 bridging to [bus 05-06]
[  156.927278] pci 0000:04:00.0: bridge window [mem 0x00000000-0x000fffff] to [bus 05-06] requires relaxed alignment rules
[  156.927283] pci 0000:04:00.0: bridge window [mem 0x60000000-0x77ffffff]: assigned
[  156.927285] pci 0000:04:00.0: bridge window [mem 0xc00000000-0x1bffffffff 64bit pref]: assigned
[  156.927287] pci 0000:04:00.0: bridge window [io  0x2000-0x5fff]: assigned
[  156.927288] pci 0000:05:00.0: bridge window [mem 0x60000000-0x77ffffff]: assigned
[  156.927290] pci 0000:05:00.0: bridge window [mem 0xc00000000-0x1bffffffff 64bit pref]: assigned
[  156.927291] pci 0000:05:00.0: bridge window [io  0x2000-0x5fff]: assigned
[  156.927293] pci 0000:06:00.0: BAR 0 [mem 0x60000000-0x60003fff 64bit]: assigned
[  156.927307] pci 0000:05:00.0: PCI bridge to [bus 06]
[  156.927310] pci 0000:05:00.0:   bridge window [io  0x2000-0x5fff]
[  156.927315] pci 0000:05:00.0:   bridge window [mem 0x60000000-0x77ffffff]
[  156.927318] pci 0000:05:00.0:   bridge window [mem 0xc00000000-0x1bffffffff 64bit pref]
[  156.927324] pci 0000:04:00.0: PCI bridge to [bus 05-06]
[  156.927327] pci 0000:04:00.0:   bridge window [io  0x2000-0x5fff]
[  156.927332] pci 0000:04:00.0:   bridge window [mem 0x60000000-0x77ffffff]
[  156.927335] pci 0000:04:00.0:   bridge window [mem 0xc00000000-0x1bffffffff 64bit pref]
[  156.927341] pcieport 0000:00:04.1: PCI bridge to [bus 04-63]
[  156.927343] pcieport 0000:00:04.1:   bridge window [io  0x2000-0x5fff]
[  156.927346] pcieport 0000:00:04.1:   bridge window [mem 0x60000000-0x77ffffff]
[  156.927348] pcieport 0000:00:04.1:   bridge window [mem 0xc00000000-0x1bffffffff 64bit pref]
[  156.927812] pcieport 0000:04:00.0: enabling device (0000 -> 0003)
[  156.927991] pcieport 0000:05:00.0: enabling device (0000 -> 0003)
[  156.928480] nvme 0000:06:00.0: platform quirk: setting simple suspend
[  156.928684] nvme nvme1: pci function 0000:06:00.0
[  156.928703] nvme 0000:06:00.0: enabling device (0000 -> 0002)
boltctl 
 ● ASMedia 246x
   ├─ type:          peripheral
   ├─ name:          246x
   ├─ vendor:        ASMedia
   ├─ uuid:          0f534c17-3032-19dd-ffff-ffffffffffff
   ├─ generation:    USB4
   ├─ status:        authorized
   │  ├─ domain:     979e3804-b079-25e4-ffff-ffffffffffff
   │  ├─ rx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  ├─ tx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  └─ authflags:  none
   ├─ authorized:    pon, 21 kwi 2025, 10:25:26
   ├─ connected:     pon, 21 kwi 2025, 10:25:26
   └─ stored:        nie, 20 kwi 2025, 22:08:33
      ├─ policy:     iommu
      └─ key:        no

And to clarify things.
I tried many things.
I removed plasma-thunderbot to config everything without the Plasma interference. Didn't help.

As you can see above, the policy is set to iommu. Tried auto - didn't help.
But when I set it to manual there is a change. Steps to to recreate:

sudo boltctl forget 0f534c17-3032-19dd-ffff-ffffffffffff
sudo boltctl enroll 0f534c17-3032-19dd-ffff-ffffffffffff --policy=manual
boltctl
ASMedia 246x
   ├─ type:          peripheral
   ├─ name:          246x
   ├─ vendor:        ASMedia
   ├─ uuid:          0f534c17-3032-19dd-ffff-ffffffffffff
   ├─ dbus path:     /org/freedesktop/bolt/devices/0f534c17_3032_19dd_ffff_ffffffffffff
   ├─ generation:    USB4
   ├─ status:        authorized
   │  ├─ domain:     979e3804-b079-25e4-ffff-ffffffffffff
   │  ├─ parent:     979e3804-b079-25e4-ffff-ffffffffffff
   │  ├─ syspath:    /sys/devices/pci0000:00/0000:00:08.3/0000:66:00.6/domain0/0-0/0-2
   │  ├─ rx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  ├─ tx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  └─ authflags:  none
   ├─ authorized:    pon, 21 kwi 2025, 10:33:59
   ├─ connected:     pon, 21 kwi 2025, 10:33:59
   └─ stored:        pon, 21 kwi 2025, 10:33:59
      ├─ policy:     manual
      └─ key:        no

With that configuration when I connec the enclosute this is what is going one:

$ sudo dmesg -W
[ 1053.034166] thunderbolt 0-0:2.1: new retimer found, vendor=0x1da0 device=0x8830
[ 1053.149529] thunderbolt 0-2: new device found, vendor=0xb8 device=0x2463
[ 1053.149537] thunderbolt 0-2: ASMedia 246x
[ 1063.162473] thunderbolt 0-0:2.1: retimer disconnected
[ 1063.162968] thunderbolt 0-2: device disconnected
[ 1066.543722] usb 7-1: new high-speed USB device number 3 using xhci_hcd
[ 1066.674660] usb 7-1: New USB device found, idVendor=174c, idProduct=2463, bcdDevice= 1.00
[ 1066.674676] usb 7-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1066.674723] usb 7-1: Product: ASM246X series
[ 1066.674730] usb 7-1: Manufacturer: ASMedia
[ 1066.674736] usb 7-1: SerialNumber: AAAABBBB0821
[ 1066.678460] scsi host0: uas
[ 1067.549299] scsi 0:0:0:0: Direct-Access     ASMT     ASM246X          0    PQ: 0 ANSI: 6
[ 1068.718858] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1068.720402] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1068.720703] sd 0:0:0:0: [sda] Write Protect is off
[ 1068.720709] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 1068.721129] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1068.721267] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 1068.721269] sd 0:0:0:0: [sda] Optimal transfer size 2097152 bytes
[ 1068.740201]  sda: sda1
[ 1068.740375] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1073.749564] usb 7-1: USB disconnect, device number 3

And when I do lsblk I can see the drive as sda/sda1
It is working but slow.

Last edited by 860lacov (2025-04-21 10:45:32)

Offline

#5 2025-04-21 20:50:54

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

I meant more like a manual rescan once the device has settled a bit.
The nvme is detected and then enabled but apparently not properly partprobed?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2025-04-22 04:09:16

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

I meant more like a manual rescan once the device has settled a bit.
The nvme is detected and then enabled but apparently not properly partprobed?

I have done a rescan many times. I don’t mean many times in a row (although that too). I tried right after connecting, a few minutes later, and also after checking with the boltctl command. In the system, it looks like the enclosure itself is visible and working, but the hard drive is not. The drive itself is functional.

P.s.
A second ago I checked the enclosure in my work.
It works with Windows laptop.

Last edited by 860lacov (2025-04-22 05:40:49)

Offline

#7 2025-04-22 08:01:15

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

The nvme is detected and then enabled but apparently not properly partprobed?

[  156.928480] nvme 0000:06:00.0: platform quirk: setting simple suspend
[  156.928684] nvme nvme1: pci function 0000:06:00.0
[  156.928703] nvme 0000:06:00.0: enabling device (0000 -> 0002)

=> https://wiki.archlinux.org/title/Solid_ … Management

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2025-04-22 08:16:29

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

The nvme is detected and then enabled but apparently not properly partprobed?

[  156.928480] nvme 0000:06:00.0: platform quirk: setting simple suspend
[  156.928684] nvme nvme1: pci function 0000:06:00.0
[  156.928703] nvme 0000:06:00.0: enabling device (0000 -> 0002)

=> https://wiki.archlinux.org/title/Solid_ … Management

nvme tool doesn't work. It works but when I do nvme list there is only my internal nvme drive.
Drive inside the enclosure is not visible for the system

Offline

#9 2025-04-22 15:22:48

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

After you get the above, 

sudo ls -l /dev/nvme*

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2025-04-22 19:35:46

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

After you get the above, 

sudo ls -l /dev/nvme*
sudo nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev  
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            S6Z2NJ0X507322N      Samsung SSD 990 PRO 2TB                  0x1          1.09  TB /   2.00  TB    512   B +  0 B   4B2QJXD7

I believe that nvme id-ctrl -H /dev/nvme0 is irrelevnt withoud second disk in nvme list

sudo ls -l /dev/nvme*
crw------- 1 root root 240, 0 04-22 21:26 /dev/nvme0
brw-rw---- 1 root disk 259, 0 04-22 21:26 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 04-22 21:26 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 04-22 21:26 /dev/nvme0n1p2

Offline

#11 2025-04-22 20:04:37

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

Does it still show up in lspci at this point?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2025-04-23 04:00:27

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

Does it still show up in lspci at this point?

Yes. And it is recognised

lspci | grep -i nvme
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
[jm@p14s ~]
$ lspci | grep -i asm
04:00.0 PCI bridge: ASMedia Technology Inc. Device 2463
05:00.0 PCI bridge: ASMedia Technology Inc. Device 2463
[jm@p14s ~]
$ lspci -s -v 03:00.0 
lspci: -s: Invalid slot number
[jm@p14s ~]
$ lspci -v -s 03:00.0 
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] (prog-if 02 [NVM Express])
        Subsystem: Samsung Electronics Co Ltd Device a801
        Flags: bus master, fast devsel, latency 0, IRQ 51, IOMMU group 16
        Memory at 78c00000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: nvme
        Kernel modules: nvme

[jm@p14s ~]
$ lspci -v -s 06:00.0 
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
        Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO
        Flags: fast devsel, IRQ 141, IOMMU group 7
        Memory at 60000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel modules: nvme

[jm@p14s ~]
$ lspci -v -s 04:00.0 
04:00.0 PCI bridge: ASMedia Technology Inc. Device 2463 (prog-if 00 [Normal decode])
        Subsystem: ASMedia Technology Inc. Device 2463
        Physical Slot: 0
        Flags: bus master, fast devsel, latency 0, IRQ 141, IOMMU group 7
        Bus: primary=04, secondary=05, subordinate=06, sec-latency=0
        I/O behind bridge: 2000-5fff [size=16K] [16-bit]
        Memory behind bridge: 60000000-77ffffff [size=384M] [32-bit]
        Prefetchable memory behind bridge: c00000000-1bffffffff [size=64G] [32-bit]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

[jm@p14s ~]
$ lspci -v -s 05:00.0 
05:00.0 PCI bridge: ASMedia Technology Inc. Device 2463 (prog-if 00 [Normal decode])
        Subsystem: ASMedia Technology Inc. Device 2463
        Flags: bus master, fast devsel, latency 0, IRQ 142, IOMMU group 7
        Bus: primary=05, secondary=06, subordinate=06, sec-latency=0
        I/O behind bridge: 2000-5fff [size=16K] [16-bit]
        Memory behind bridge: 60000000-77ffffff [size=384M] [32-bit]
        Prefetchable memory behind bridge: c00000000-1bffffffff [size=64G] [32-bit]
        Capabilities: <access denied>
        Kernel driver in use: pcieport

Last edited by 860lacov (2025-04-23 04:03:31)

Offline

#13 2025-04-23 06:40:39

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

03:00.0 seems to be the internal drive, 06:00.0 isn't operated by the nvme kernel module ("Kernel driver in use: nvme" is missing), wtf?

lspci -tvnn
modprobe -c | grep nvme

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2025-04-23 15:46:20

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

03:00.0 seems to be the internal drive, 06:00.0 isn't operated by the nvme kernel module ("Kernel driver in use: nvme" is missing), wtf?

lspci -tvnn
modprobe -c | grep nvme

Thats correct. I have Samsung 990 Pro - internal drive
970 Evo Plus - Drive in enclosure

lspci -tvnn
-[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Phoenix Root Complex [1022:14e8]
           +-00.2  Advanced Micro Devices, Inc. [AMD] Phoenix IOMMU [1022:14e9]
           +-01.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge [1022:14ea]
           +-02.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge [1022:14ea]
           +-02.1-[01]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168]
           +-02.2-[02]----00.0  Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103]
           +-02.4-[03]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] [144d:a80c]
           +-03.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge [1022:14ea]
           +-04.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge [1022:14ea]
           +-04.1-[04-63]----00.0-[05-06]----00.0-[06]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
           +-08.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge [1022:14ea]
           +-08.1-[64]--+-00.0  Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf]
           |            +-00.1  Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller [1002:1640]
           |            +-00.2  Advanced Micro Devices, Inc. [AMD] Phoenix CCP/PSP 3.0 Device [1022:15c7]
           |            +-00.3  Advanced Micro Devices, Inc. [AMD] Device [1022:15b9]
           |            +-00.4  Advanced Micro Devices, Inc. [AMD] Device [1022:15ba]
           |            +-00.5  Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2]
           |            \-00.6  Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]
           +-08.2-[65]--+-00.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Function [1022:14ec]
           |            \-00.1  Advanced Micro Devices, Inc. [AMD] AMD IPU Device [1022:1502]
           +-08.3-[66]--+-00.0  Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Function [1022:14ec]
           |            +-00.3  Advanced Micro Devices, Inc. [AMD] Device [1022:15c0]
           |            +-00.4  Advanced Micro Devices, Inc. [AMD] Device [1022:15c1]
           |            \-00.6  Advanced Micro Devices, Inc. [AMD] Pink Sardine USB4/Thunderbolt NHI controller #2 [1022:1669]
           +-14.0  Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b]
           +-14.3  Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e]
           +-18.0  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 0 [1022:14f0]
           +-18.1  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 1 [1022:14f1]
           +-18.2  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 2 [1022:14f2]
           +-18.3  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 3 [1022:14f3]
           +-18.4  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 4 [1022:14f4]
           +-18.5  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 5 [1022:14f5]
           +-18.6  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 6 [1022:14f6]
           \-18.7  Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 7 [1022:14f7]
modprobe -c | grep nvme
alias nvmet_transport_1 nvmet_rdma
alias nvmet_transport_254 nvme_loop
alias nvmet_transport_3 nvmet_tcp
alias of:N*T*Cmobileye,eyeq5_bootloader_config nvmem_rmem
alias of:N*T*Cmobileye,eyeq5_bootloader_configC* nvmem_rmem
alias of:N*T*Cnvmem_rmem nvmem_rmem
alias of:N*T*Cnvmem_rmemC* nvmem_rmem
alias of:N*T*Czii,rave_sp_eeprom nvmem_rave_sp_eeprom
alias of:N*T*Czii,rave_sp_eepromC* nvmem_rave_sp_eeprom
alias pci:v*d*sv*sd*bc01sc08i02* nvme
alias pci:v0000106Bd00002001sv*sd*bc*sc*i* nvme
alias pci:v0000106Bd00002003sv*sd*bc*sc*i* nvme
alias pci:v0000106Bd00002005sv*sd*bc*sc*i* nvme
alias pci:v000010ECd00005762sv*sd*bc*sc*i* nvme
alias pci:v000010ECd00005763sv*sd*bc*sc*i* nvme
alias pci:v000010ECd00005765sv*sd*bc*sc*i* nvme
alias pci:v00001217d00008760sv*sd*bc*sc*i* nvme
alias pci:v0000126Fd00002262sv*sd*bc*sc*i* nvme
alias pci:v0000126Fd00002263sv*sd*bc*sc*i* nvme
alias pci:v00001344d00005407sv*sd*bc*sc*i* nvme
alias pci:v00001344d00006001sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A802sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A809sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A80Bsv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A821sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A822sv*sd*bc*sc*i* nvme
alias pci:v000015B7d00002001sv*sd*bc*sc*i* nvme
alias pci:v000015B7d00005008sv*sd*bc*sc*i* nvme
alias pci:v00001987d00005012sv*sd*bc*sc*i* nvme
alias pci:v00001987d00005016sv*sd*bc*sc*i* nvme
alias pci:v00001987d00005019sv*sd*bc*sc*i* nvme
alias pci:v00001987d00005021sv*sd*bc*sc*i* nvme
alias pci:v00001B36d00000010sv*sd*bc*sc*i* nvme
alias pci:v00001B4Bd00001092sv*sd*bc*sc*i* nvme
alias pci:v00001BB1d00000100sv*sd*bc*sc*i* nvme
alias pci:v00001C58d00000003sv*sd*bc*sc*i* nvme
alias pci:v00001C58d00000023sv*sd*bc*sc*i* nvme
alias pci:v00001C5Cd00001504sv*sd*bc*sc*i* nvme
alias pci:v00001C5Cd0000174Asv*sd*bc*sc*i* nvme
alias pci:v00001C5Cd00001D59sv*sd*bc*sc*i* nvme
alias pci:v00001C5Fd00000540sv*sd*bc*sc*i* nvme
alias pci:v00001CC1d000033F8sv*sd*bc*sc*i* nvme
alias pci:v00001CC1d00005350sv*sd*bc*sc*i* nvme
alias pci:v00001CC1d00008201sv*sd*bc*sc*i* nvme
alias pci:v00001CC4d00006302sv*sd*bc*sc*i* nvme
alias pci:v00001CC4d00006303sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd00000061sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd00000065sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd00008061sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd0000CD00sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd0000CD01sv*sd*bc*sc*i* nvme
alias pci:v00001D0Fd0000CD02sv*sd*bc*sc*i* nvme
alias pci:v00001D97d00001D97sv*sd*bc*sc*i* nvme
alias pci:v00001D97d00002263sv*sd*bc*sc*i* nvme
alias pci:v00001D97d00002269sv*sd*bc*sc*i* nvme
alias pci:v00001DBEd00005216sv*sd*bc*sc*i* nvme
alias pci:v00001DBEd00005236sv*sd*bc*sc*i* nvme
alias pci:v00001E49d00000021sv*sd*bc*sc*i* nvme
alias pci:v00001E49d00000041sv*sd*bc*sc*i* nvme
alias pci:v00001E4Bd00001001sv*sd*bc*sc*i* nvme
alias pci:v00001E4Bd00001002sv*sd*bc*sc*i* nvme
alias pci:v00001E4Bd00001202sv*sd*bc*sc*i* nvme
alias pci:v00001E4Bd00001602sv*sd*bc*sc*i* nvme
alias pci:v00001F40d00001202sv*sd*bc*sc*i* nvme
alias pci:v00001F40d00005236sv*sd*bc*sc*i* nvme
alias pci:v00002646d00002262sv*sd*bc*sc*i* nvme
alias pci:v00002646d00002263sv*sd*bc*sc*i* nvme
alias pci:v00002646d00005013sv*sd*bc*sc*i* nvme
alias pci:v00002646d00005016sv*sd*bc*sc*i* nvme
alias pci:v00002646d00005018sv*sd*bc*sc*i* nvme
alias pci:v00002646d0000501Asv*sd*bc*sc*i* nvme
alias pci:v00002646d0000501Bsv*sd*bc*sc*i* nvme
alias pci:v00002646d0000501Esv*sd*bc*sc*i* nvme
alias pci:v00008086d00000953sv*sd*bc*sc*i* nvme
alias pci:v00008086d00000A53sv*sd*bc*sc*i* nvme
alias pci:v00008086d00000A54sv*sd*bc*sc*i* nvme
alias pci:v00008086d00000A55sv*sd*bc*sc*i* nvme
alias pci:v00008086d00005845sv*sd*bc*sc*i* nvme
alias pci:v00008086d0000F1A5sv*sd*bc*sc*i* nvme
alias pci:v00008086d0000F1A6sv*sd*bc*sc*i* nvme
alias pci:v0000C0A9d0000540Asv*sd*bc*sc*i* nvme
alias symbol:NVME_TARGET_PASSTHRU nvme_core
alias symbol:__SCK__tp_func_nvme_sq nvme_core
alias symbol:__SCT__tp_func_nvme_sq nvme_core
alias symbol:__nvme_check_ready nvme_core
alias symbol:__nvme_submit_sync_cmd nvme_core
alias symbol:__traceiter_nvme_sq nvme_core
alias symbol:__tracepoint_nvme_sq nvme_core
alias symbol:admin_timeout nvme_core
alias symbol:mt76_get_of_data_from_nvmem mt76
alias symbol:nvme_add_ctrl nvme_core
alias symbol:nvme_alloc_admin_tag_set nvme_core
alias symbol:nvme_alloc_io_tag_set nvme_core
alias symbol:nvme_auth_alloc_key nvme_auth
alias symbol:nvme_auth_augmented_challenge nvme_auth
alias symbol:nvme_auth_dhgroup_id nvme_auth
alias symbol:nvme_auth_dhgroup_kpp nvme_auth
alias symbol:nvme_auth_dhgroup_name nvme_auth
alias symbol:nvme_auth_digest_name nvme_auth
alias symbol:nvme_auth_extract_key nvme_auth
alias symbol:nvme_auth_free nvme_core
alias symbol:nvme_auth_free_key nvme_auth
alias symbol:nvme_auth_gen_privkey nvme_auth
alias symbol:nvme_auth_gen_pubkey nvme_auth
alias symbol:nvme_auth_gen_shared_secret nvme_auth
alias symbol:nvme_auth_generate_key nvme_auth
alias symbol:nvme_auth_get_seqnum nvme_auth
alias symbol:nvme_auth_hmac_hash_len nvme_auth
alias symbol:nvme_auth_hmac_id nvme_auth
alias symbol:nvme_auth_hmac_name nvme_auth
alias symbol:nvme_auth_init_ctrl nvme_core
alias symbol:nvme_auth_key_struct_size nvme_auth
alias symbol:nvme_auth_negotiate nvme_core
alias symbol:nvme_auth_stop nvme_core
alias symbol:nvme_auth_transform_key nvme_auth
alias symbol:nvme_auth_wait nvme_core
alias symbol:nvme_cancel_admin_tagset nvme_core
alias symbol:nvme_cancel_request nvme_core
alias symbol:nvme_cancel_tagset nvme_core
alias symbol:nvme_change_ctrl_state nvme_core
alias symbol:nvme_cleanup_cmd nvme_core
alias symbol:nvme_command_effects nvme_core
alias symbol:nvme_complete_async_event nvme_core
alias symbol:nvme_complete_batch_req nvme_core
alias symbol:nvme_complete_rq nvme_core
alias symbol:nvme_ctrl_from_file nvme_core
alias symbol:nvme_delete_ctrl nvme_core
alias symbol:nvme_delete_wq nvme_core
alias symbol:nvme_dev_attrs_group nvme_core
alias symbol:nvme_disable_ctrl nvme_core
alias symbol:nvme_enable_ctrl nvme_core
alias symbol:nvme_execute_rq nvme_core
alias symbol:nvme_fail_nonready_command nvme_core
alias symbol:nvme_fc_io_getuuid nvme_fc
alias symbol:nvme_fc_rcv_ls_req nvme_fc
alias symbol:nvme_fc_register_localport nvme_fc
alias symbol:nvme_fc_register_remoteport nvme_fc
alias symbol:nvme_fc_rescan_remoteport nvme_fc
alias symbol:nvme_fc_set_remoteport_devloss nvme_fc
alias symbol:nvme_fc_unregister_localport nvme_fc
alias symbol:nvme_fc_unregister_remoteport nvme_fc
alias symbol:nvme_find_get_ns nvme_core
alias symbol:nvme_get_admin_opcode_str nvme_core
alias symbol:nvme_get_fabrics_opcode_str nvme_core
alias symbol:nvme_get_features nvme_core
alias symbol:nvme_get_opcode_str nvme_core
alias symbol:nvme_host_path_error nvme_core
alias symbol:nvme_init_ctrl nvme_core
alias symbol:nvme_init_ctrl_finish nvme_core
alias symbol:nvme_init_request nvme_core
alias symbol:nvme_io_timeout nvme_core
alias symbol:nvme_keyring_id nvme_keyring
alias symbol:nvme_mark_namespaces_dead nvme_core
alias symbol:nvme_mpath_start_request nvme_core
alias symbol:nvme_passthru_end nvme_core
alias symbol:nvme_passthru_start nvme_core
alias symbol:nvme_put_ns nvme_core
alias symbol:nvme_quiesce_admin_queue nvme_core
alias symbol:nvme_quiesce_io_queues nvme_core
alias symbol:nvme_remove_admin_tag_set nvme_core
alias symbol:nvme_remove_io_tag_set nvme_core
alias symbol:nvme_remove_namespaces nvme_core
alias symbol:nvme_reset_ctrl nvme_core
alias symbol:nvme_reset_wq nvme_core
alias symbol:nvme_set_features nvme_core
alias symbol:nvme_set_queue_count nvme_core
alias symbol:nvme_setup_cmd nvme_core
alias symbol:nvme_start_ctrl nvme_core
alias symbol:nvme_start_freeze nvme_core
alias symbol:nvme_stop_ctrl nvme_core
alias symbol:nvme_stop_keep_alive nvme_core
alias symbol:nvme_submit_sync_cmd nvme_core
alias symbol:nvme_sync_io_queues nvme_core
alias symbol:nvme_sync_queues nvme_core
alias symbol:nvme_tls_key_lookup nvme_keyring
alias symbol:nvme_tls_psk_default nvme_keyring
alias symbol:nvme_try_sched_reset nvme_core
alias symbol:nvme_unfreeze nvme_core
alias symbol:nvme_uninit_ctrl nvme_core
alias symbol:nvme_unquiesce_admin_queue nvme_core
alias symbol:nvme_unquiesce_io_queues nvme_core
alias symbol:nvme_wait_freeze nvme_core
alias symbol:nvme_wait_freeze_timeout nvme_core
alias symbol:nvme_wait_reset nvme_core
alias symbol:nvme_wq nvme_core
alias symbol:nvmet_alloc_ctrl nvmet
alias symbol:nvmet_check_transfer_len nvmet
alias symbol:nvmet_cq_create nvmet
alias symbol:nvmet_ctrl_fatal_error nvmet
alias symbol:nvmet_ctrl_put nvmet
alias symbol:nvmet_fc_invalidate_host nvmet_fc
alias symbol:nvmet_fc_rcv_fcp_abort nvmet_fc
alias symbol:nvmet_fc_rcv_fcp_req nvmet_fc
alias symbol:nvmet_fc_rcv_ls_req nvmet_fc
alias symbol:nvmet_fc_register_targetport nvmet_fc
alias symbol:nvmet_fc_unregister_targetport nvmet_fc
alias symbol:nvmet_register_transport nvmet
alias symbol:nvmet_req_alloc_sgls nvmet
alias symbol:nvmet_req_complete nvmet
alias symbol:nvmet_req_free_sgls nvmet
alias symbol:nvmet_req_init nvmet
alias symbol:nvmet_req_transfer_len nvmet
alias symbol:nvmet_req_uninit nvmet
alias symbol:nvmet_sq_create nvmet
alias symbol:nvmet_sq_destroy nvmet
alias symbol:nvmet_sq_init nvmet
alias symbol:nvmet_unregister_transport nvmet
alias symbol:nvmet_update_cc nvmet
alias symbol:nvmet_wq nvmet
alias symbol:nvmf_connect_admin_queue nvme_fabrics
alias symbol:nvmf_connect_io_queue nvme_fabrics
alias symbol:nvmf_free_options nvme_fabrics
alias symbol:nvmf_get_address nvme_fabrics
alias symbol:nvmf_ip_options_match nvme_fabrics
alias symbol:nvmf_map_queues nvme_fabrics
alias symbol:nvmf_reg_read32 nvme_fabrics
alias symbol:nvmf_reg_read64 nvme_fabrics
alias symbol:nvmf_reg_write32 nvme_fabrics
alias symbol:nvmf_register_transport nvme_fabrics
alias symbol:nvmf_set_io_queues nvme_fabrics
alias symbol:nvmf_should_reconnect nvme_fabrics
alias symbol:nvmf_subsystem_reset nvme_fabrics
alias symbol:nvmf_unregister_transport nvme_fabrics

Last edited by 860lacov (2025-04-23 15:47:22)

Offline

#15 2025-04-23 15:57:53

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

Neither is caught by 

alias pci:v0000144Dd0000A802sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A809sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A80Bsv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A821sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A822sv*sd*bc*sc*i* nvme

But the pci id for the troublesome device shows up on google A LOT.
https://wiki.archlinux.org/title/Solid_ … leshooting - disable APST and IOMMU
Since it's a laptop I assume you cannot try to use it as internal nvme, skipping the TB/USB4 connection?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2025-04-23 16:22:54

860lacov
Member
Registered: 2020-05-02
Posts: 489

Re: The system does not detect the drive in the NVMe enclosure.

seth wrote:

Neither is caught by 

alias pci:v0000144Dd0000A802sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A809sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A80Bsv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A821sv*sd*bc*sc*i* nvme
alias pci:v0000144Dd0000A822sv*sd*bc*sc*i* nvme

But the pci id for the troublesome device shows up on google A LOT.
https://wiki.archlinux.org/title/Solid_ … leshooting - disable APST and IOMMU
Since it's a laptop I assume you cannot try to use it as internal nvme, skipping the TB/USB4 connection?

Adding kernel parameters: nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off and pcie_port_pm=off almost helped.
lsblk shows:
nvme1n1       259:3    0    0B  0 disk
but

env LANG=C sudo fdisk /dev/nvme1n1 

Welcome to fdisk (util-linux 2.41).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/nvme1n1: Invalid argument

With additional paramater iommu=off led on the enclosure is blinking for a while and then enclosure turns off. When I do echo 1 | sudo tee /sys/bus/pci/rescan
lsblk shows the drive but again as an sda/sda1 drive and not nvme

[  274.713033] thunderbolt 0-0:2.1: new retimer found, vendor=0x1da0 device=0x8830
[  274.828465] thunderbolt 0-2: new device found, vendor=0xb8 device=0x2463
[  274.828476] thunderbolt 0-2: ASMedia 246x
[  284.840349] thunderbolt 0-0:2.1: retimer disconnected
[  284.840810] thunderbolt 0-2: device disconnected
[  288.219505] usb 7-1: new high-speed USB device number 4 using xhci_hcd
[  288.353496] usb 7-1: New USB device found, idVendor=174c, idProduct=2463, bcdDevice= 1.00
[  288.353508] usb 7-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  288.353510] usb 7-1: Product: ASM246X series
[  288.353512] usb 7-1: Manufacturer: ASMedia
[  288.353513] usb 7-1: SerialNumber: AAAABBBB0821
[  288.357069] scsi host0: uas
[  289.226762] scsi 0:0:0:0: Direct-Access     ASMT     ASM246X          0    PQ: 0 ANSI: 6
[  291.741551] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  291.742897] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[  291.743182] sd 0:0:0:0: [sda] Write Protect is off
[  291.743187] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[  291.743695] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  291.743882] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[  291.743886] sd 0:0:0:0: [sda] Optimal transfer size 2097152 bytes
[  291.764112]  sda: sda1
[  291.764307] sd 0:0:0:0: [sda] Attached SCSI disk


As for using it internally, it is too much hassle. The drive is working correctly. When I connect it to a Windows laptop or use a different enclosure (USB 3), it works as it should.
Is it possible that another drive would work with this enclosure? I have another Samsung NVMe drive, the 990 Pro. It is brand new in sealed box, and I haven't opened it because I thought the enclosure might be broken.



P.S.
I just checked.
990 Pro in this enclosure work like a charm

Last edited by 860lacov (2025-04-23 20:18:54)

Offline

#17 2025-04-24 06:14:32

seth
Member
Registered: 2012-09-03
Posts: 63,481

Re: The system does not detect the drive in the NVMe enclosure.

nvme1n1       259:3    0    0B  0 disk

Shows up as zero-size, so while it's not completely falling away, it's also not working properly.

990 Pro in this enclosure work like a charm

and apparently the reason is the specific nvme.
Did you attempt a live rescan w/ APST disabled but the iommu enbaled?

Resp. https://wiki.archlinux.org/title/Solid_ … nd_support don't turn iommu off, but set it to soft (and for the amd system you may also get away w/ fullflush

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB