Cannot access Nvme SSD

Dragomy · 2025-03-15 11:30:44

Hello, this is regarding a friend's system; he couldn't access his drive on Windows anymore, and since he wanted to switch anyway, he decided to do it now.

Now on Arch, the NVMe is still not accessible. I first thought it might just be the typical file system or partition problem, but it seems to be a bit deeper.

First lsblk, the partition is seen with 1.8T the drive itself as 0B, normally it shows the complete size.

sudo lsblk
NAME                   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS

nvme0n1                259:4    0     0B  0 disk 
`-nvme0n1p1            259:5    0   1.8T  0 part

He then tried gdisk which showed this:

sudo gdisk /dev/nvme0n1
GPT fdisk (gdisk) version 1.0.10

Problem reading disk in BasicMBRData::ReadMBRData()!
Warning! Read error 22; strange behavior now likely!
Warning! Read error 22; strange behavior now likely!
Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************

Disk is too small to hold GPT data (0 sectors)! Aborting!

sudo smartctl -a /dev/nvme0n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.13.7-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output error

So I searched for this
Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output error
and the only thing that seemed to go in the right direction was caused by a card reader bug.
The Pc does not have a card reader.

Here a bit of dmesg for good measure:

[reffex@archlinux ~]$ dmesg | grep -i nvme
dmesg: read kernel buffer failed: Operation not permitted
[reffex@archlinux ~]$ sudo dmesg | grep -i nvme
[    2.254802] nvme nvme0: pci function 0000:0c:00.0
[    2.254802] nvme nvme1: pci function 0000:0f:00.0
[    2.254817] nvme 0000:0c:00.0: enabling device (0000 -> 0002)
[    2.292628] nvme nvme1: allocated 128 MiB host memory buffer (1 segment).
[    2.294455] nvme nvme1: 12/0/0 default/read/poll queues
[    2.298044]  nvme1n1: p1 p2 p3
[    2.318501] nvme nvme0: allocated 128 MiB host memory buffer (1 segment).
[    2.320391] nvme nvme0: 12/0/0 default/read/poll queues
[    2.323619]  nvme0n1: p1
[   37.918733] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
[   37.918740] nvme nvme0: Does your device have a faulty power saving mode enabled?
[   37.918742] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
[   37.939169] nvme0n1: Read(0x2) @ LBA 3907028992, 8 blocks, Host Aborted Command (sct 0x3 / sc 0x71) 
[   37.939178] I/O error, dev nvme0n1, sector 3907028992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   37.948486] nvme 0000:0c:00.0: enabling device (0000 -> 0002)
[   37.948572] nvme nvme0: Disabling device after reset failure: -19
[   37.958791] Buffer I/O error on dev nvme0n1, logical block 488378624, async page read
[   37.961087] Buffer I/O error on dev nvme0n1p1, logical block 488378096, async page read
[   38.004318] FAT-fs (nvme1n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   46.484688] nvme nvme0: using unchecked data buffer
[   46.490485] block nvme0n1: No UUID available providing old NGUID
[   46.490511] nvme nvme0: Identify namespace failed (-5)
[   52.774074] nvme nvme0: Identify namespace failed (-5)
[  201.420237] nvme nvme0: Identify namespace failed (-5)

I really have no clue; the SSD appears to be new, so I don't think it's dying. He says gparted doesn't notice it.

Any clues?

Thank you In advance

kermit63 · 2025-03-15 11:51:08

The first thing I'll probably do is boot into the UEFI firmware and see if it is at least being detected correctly there.

Any OS you use can only rely on what the firmware tells it. If UEFI itself can't detect it properly, then it's time to really consider hardware failure. As a last resort, try removing and plugging it back in. Maybe it's not seated correctly.

Arch Linux

#1 2025-03-15 11:30:44

Cannot access Nvme SSD

#2 2025-03-15 11:51:08

Re: Cannot access Nvme SSD

Board footer