Nvme not detected

Issues & Assistance
1

I have added a PCIe m.2 adapter card containing a 4 TB m.2 memory drive in a PCI3e 3.0 x16 slot (slot number 6 by the Dell motherboard diagram https://www.dell.com/community/en/conversations/precision-fixed-workstations/t5810-not-detecting-nvme-m2-in-bios-or-win10/647f9983f4ccf8a8dece1aaa) in my Dell T5810. Nothing shows in the slot in the BIOS and of course, not in the OS either. I tried this drive in another 3.0 slot to no avail either. In reading on the Dell forums, changing SATA from RAID set to AHCI solved this for some, but I tried it to no avail. This does not seem to be related to UEFI vs Legacy boot as far as I can tell. I am using Legacy boot (both of my drives are btrfs) so changing to UEFI simply stops all of my existing drives from being bootable. This motherboard does not support booting from nvme (unless using something like Clover EFI), but it should allow for the memory drive to be detected. I saw some posts about kernel parameter nvme_load=YES to get drives to show in gparted, but I am reluctant to mess with that, unsure it has anything to do with the issue. Any assistance or ideas appreciated.
Thanks

Barry

╭─bmirtsching@DellT5810 in ~ took 1ms
╰─λ garuda-inxi
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "",
LC_ALL = (unset),
LC_ADDRESS = "en_US.UTF-8",
LC_NAME = "en_US.UTF-8",
LC_MONETARY = "en_US.UTF-8",
LC_PAPER = "en_US.UTF-8",
LC_IDENTIFICATION = "en_US.UTF-8",
LC_TELEPHONE = "en_US.UTF-8",
LC_MEASUREMENT = "en_US.UTF-8",
LC_TIME = "en_US.UTF-8",
LC_NUMERIC = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:
Kernel: 6.10.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=73b3631e-3dec-4209-9c71-4928bd70fb46 rw rootflags=subvol=@
quiet rd.luks.uuid=a8e40cc9-41be-4434-8bf9-423936703f72
rd.luks.uuid=f79a930f-07d4-4043-878d-b926518407cc
resume=/dev/mapper/luks-f79a930f-07d4-4043-878d-b926518407cc loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Dell product: Precision Tower 5810 v: N/A
serial: <superuser required> Chassis: type: 7 serial: <superuser required>
Mobo: Dell model: 0K240Y v: A01 serial: <superuser required> part-nu: 0617
uuid: <superuser required> UEFI-[Legacy]: Dell v: A34 date: 10/19/2020
CPU:
Info: model: Intel Xeon E5-2687W v4 bits: 64 type: MT MCP arch: Broadwell
level: v3 note: check built: 2015-18 process: Intel 14nm family: 6
model-id: 0x4F (79) stepping: 1 microcode: 0xB000040
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 3 MiB desc: 12x256 KiB
L3: 30 MiB desc: 1x30 MiB
Speed (MHz): avg: 3318 high: 3500 min/max: 1200/3500 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3198 2: 3193 3: 3500
4: 3500 5: 3243 6: 3193 7: 3500 8: 3193 9: 3500 10: 3500 11: 3500 12: 2167
13: 3500 14: 3500 15: 3500 16: 3293 17: 3193 18: 3191 19: 3194 20: 3500
21: 3500 22: 3500 23: 3380 24: 3194 bogomips: 143666
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
bus-ID: 05:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 3440x1440 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.4-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 18.1.8 DRM 3.57 6.10.2-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.1.4-arch1.2
device-ID: 1002:73df surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel C610/X99 series HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8d20 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 1102:0012 class-ID: 0403
Device-4: SteelSeries ApS Arctis 1 Wireless
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-5:4 chip-ID: 1038:12b3 class-ID: 0300
API: ALSA v: k6.10.2-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel
port: f020 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 1.03 TiB used: 975.98 GiB (92.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: THNSNJ128GCSU
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0101 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HDS721010KLA330
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: A9CA scheme: GPT
Partition:
ID-1: / raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 50.37 GiB (59.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-2: /home raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 50.37 GiB (59.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-3: /var/log raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 50.37 GiB (59.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-4: /var/tmp raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 50.37 GiB (59.4%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.4 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-f79a930f-07d4-4043-878d-b926518407cc
ID-2: swap-2 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A sodimm: SODIMM C gpu: amdgpu
temp: 54.0 C mem: 52.0 C
Fan Speeds (rpm): cpu: 1003 gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 4.41 GiB (14.1%)
Processes: 470 Power: uptime: 14m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2211 libs: 611
tools: gnome-software,octopi,paru Compilers: clang: 18.1.8 gcc: 14.1.1
Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-07-08
Last full system update: 2024-08-03
Is partially upgraded:   Yes
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:
2

Fix it first.

3

Had that issue earlier with conflicts during the update. Now resolved. Did the update, but still nothing as far as nvme visible.

╭─bmirtsching@DellT5810 in repo: glibc-eac on  master [?] via C v14.2.1-gcc as 🧙 took 2ms
╰─λ garuda-inxi
System:
Kernel: 6.10.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=73b3631e-3dec-4209-9c71-4928bd70fb46 rw rootflags=subvol=@
quiet rd.luks.uuid=a8e40cc9-41be-4434-8bf9-423936703f72
rd.luks.uuid=f79a930f-07d4-4043-878d-b926518407cc
resume=/dev/mapper/luks-f79a930f-07d4-4043-878d-b926518407cc loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Dell product: Precision Tower 5810 v: N/A
serial: <superuser required> Chassis: type: 7 serial: <superuser required>
Mobo: Dell model: 0K240Y v: A01 serial: <superuser required> part-nu: 0617
uuid: <superuser required> UEFI-[Legacy]: Dell v: A34 date: 10/19/2020
CPU:
Info: model: Intel Xeon E5-2687W v4 bits: 64 type: MT MCP arch: Broadwell
level: v3 note: check built: 2015-18 process: Intel 14nm family: 6
model-id: 0x4F (79) stepping: 1 microcode: 0xB000040
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 3 MiB desc: 12x256 KiB
L3: 30 MiB desc: 1x30 MiB
Speed (MHz): avg: 3358 high: 3500 min/max: 1200/3500 scaling:
driver: intel_cpufreq governor: performance cores: 1: 2596 2: 3500 3: 3500
4: 3500 5: 3500 6: 3500 7: 3500 8: 3500 9: 3500 10: 3500 11: 3500 12: 3500
13: 3500 14: 3500 15: 3500 16: 3199 17: 3500 18: 3500 19: 3500 20: 3500
21: 3500 22: 3230 23: 1580 24: 3500 bogomips: 143675
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Tul / PowerColor driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
bus-ID: 05:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 3440x1440 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 18.1.8 DRM 3.57 6.10.2-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.1.5-arch1.1
device-ID: 1002:73df surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel C610/X99 series HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8d20 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 1102:0012 class-ID: 0403
Device-4: SteelSeries ApS Arctis 1 Wireless
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 3-5:4 chip-ID: 1038:12b3 class-ID: 0300
API: ALSA v: k6.10.2-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel
port: f020 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 1.03 TiB used: 980.3 GiB (93.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: THNSNJ128GCSU
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0101 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HDS721010KLA330
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: A9CA scheme: GPT
Partition:
ID-1: / raw-size: 84.84 GiB size: 84.84 GiB (100.00%) used: 54.7 GiB (64.5%)
fs: btrfs dev: /dev/dm-1 maj-min: 254:1
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-2: /home raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 54.7 GiB (64.5%) fs: btrfs dev: /dev/dm-1 maj-min: 254:1
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-3: /var/log raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 54.7 GiB (64.5%) fs: btrfs dev: /dev/dm-1 maj-min: 254:1
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
ID-4: /var/tmp raw-size: 84.84 GiB size: 84.84 GiB (100.00%)
used: 54.7 GiB (64.5%) fs: btrfs dev: /dev/dm-1 maj-min: 254:1
mapped: luks-a8e40cc9-41be-4434-8bf9-423936703f72
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.4 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-0 maj-min: 254:0
mapped: luks-f79a930f-07d4-4043-878d-b926518407cc
ID-2: swap-2 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 54.0 C mobo: N/A sodimm: SODIMM C gpu: amdgpu
temp: 58.0 C mem: 54.0 C
Fan Speeds (rpm): cpu: 1004 gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 5.18 GiB (16.6%)
Processes: 531 Power: uptime: 28m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2215 libs: 611
tools: gnome-software,octopi,paru Compilers: clang: 18.1.8 gcc: 14.2.1
Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-07-08
Last full system update: 2024-08-04 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:
4

Are you sure this is not a hardware related problem? I have had things like this go wrong with my computer as well. Did you try removing all the drives, and I mean all of them, and just leave your NVMe in it to see if it would show up in your BIOS?

Next thing on the list, if it does show up after everything is disconnected, will you be booting Garuda off of that drive?

Also, is putting your NVMe in an external USB 3 enclosure a potential option at least just to test it out to see if it works and hasn’t failed on you? If it works in a USB caddy, you should then at least see it in gparted

5

Will try to disconnect the boot drive ssd and check bios. This m.2 is in a pcie adapter card made by Dell specifically for t5810. The adapter is new. T5810 does not support booting from pcie nvme according to Dell info. I only plan to use it for storage. Thus, in BIOS it does not show up in a list of bootable devices. In looking at the slot occupany seen in BIOS, the adapter/m.2 is not showing, says “empty”. That has me suspicious of the m.2 and your suggestion of cheching it in a usb caddy seems like a good one. If the memory is faulty, shouldn’t lspci or lshw show the adapter in the pci slot?

6

If you take the M.2 slot out and put it in a USB enclosure, something will show up in the lsusb command either the drive or the enclosure module.

The other thing is, could the TS810 card itself be faulty? If you are booted up in Garuda, try doing an lspci and see if it’s listed. Either way, try the USB route just to see what you get as well.

At the hardware level, it’s hard to say. Maybe the microprocessor in it can talk to the PCI bus, but something on the drive interface end could be faulty. Semi-conductor parts can do funny things some time, maybe the interface components could be faulty. What you need to do is check each component step by step.

7

I have a nvme usb caddy coming today to test. Nothing showed up in bios when disconnecting othwr drives. If this memory doesnt show in the new device, I’ll be returning for refund. If it shows then the Dell adapter is probably going back. Either way, your help much appreciated.

2 Likes
8

Hey anytime, let everyone know the details when you get this fixed if this post isn’t closed off by then. I’m interested in knowing more

2 Likes
9

Of course the usb nvme caddy was detected by lsblk immediately after it was plugged in and I could then partition with partition manager. Thanks. The Dell adapter is clearly defective.

1 Like
10

One other thing that someone might want to know (if reading this in the future): The USB to PCIe M.2 external adapter (caddy) would not stay on consistently during a write session when powered off of the USB port on the Dell. Others have noted this issue on other systems. I found that the average power consumption for the m.2 memory card is about 5 watts, which is probably more than the USB could put out consistently. This was solved by buying a USB powered hub (5V power input). No issues at all with it after that.

11

My rule of thumb for hubs even if they’re just going to be use for flash drives, keyboard and mouse dongles always get a powered one. Not a good idea to draw power from the system cause every little bit is hard on the PSU.

1 Like
12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.