Arch Linux

fatong

Member

Registered: 2024-02-08

Posts: 8

Unable to mount /dev/nvme0n1p3, critical medium error (bad superblock)

Yesterday I did a full system update pacman -Syu before I logged off. Today I wake up to my system borked.

I'm able to mount the boot partition /dev/nvme0n1p1, but not my root partition /dev/nvme0n1p3.

Output from dmesg <https://0x0.st/XX4S.txt>.

Output from fsck /dev/nvme0n1p3 <https://0x0.st/XX4Q.txt>.

Last edited by fatong (2024-05-03 14:51:54)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,647

Re: Unable to mount /dev/nvme0n1p3, critical medium error (bad superblock)

fsck → ddrescue

you can't fix a filesystem if the device itself is faulty

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,993

Re: Unable to mount /dev/nvme0n1p3, critical medium error (bad superblock)

https://0x0.st/XX4Q.txt just says "fsck from util-linux 2.39.1"

[    7.495210] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[    7.495241] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[    7.519524] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[    7.519549] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    7.519574] Buffer I/O error on dev nvme0n1, logical block 29305184, async page read
[    7.524013] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[    7.524047] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[    7.550942] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[    7.550971] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    7.550999] Buffer I/O error on dev nvme0n1p3, logical block 26719584, async page read
[   10.692872] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   10.692890] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   10.717186] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   10.717205] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[   10.717220] Buffer I/O error on dev nvme0n1p3, logical block 26719584, async page read
[   45.625718] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   45.625742] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   45.650066] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   45.650081] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[   45.650095] Buffer I/O error on dev nvme0n1p3, logical block 26719584, async page read
[   47.877613] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   47.878073] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   47.901985] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   47.902719] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[   47.903219] Buffer I/O error on dev nvme0n1, logical block 29305184, async page read
[   47.909596] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   47.910116] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   47.933966] nvme0n1: Read(0x2) @ LBA 234441472, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) MORE 
[   47.934557] critical medium error, dev nvme0n1, sector 234441472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[   47.934946] Buffer I/O error on dev nvme0n1p3, logical block 26719584, async page read

https://wiki.archlinux.org/title/Solid_ … leshooting
"nvme_core.default_ps_max_latency_us=0 iommu=soft" - if the error doesn't go away w/ that, the device might actually be fried - or maybe just badly seated in the slot?

---

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

fatong

Member

Registered: 2024-02-08

Posts: 8

Re: Unable to mount /dev/nvme0n1p3, critical medium error (bad superblock)

Sorry for the late response.

> https://0x0.st/XX4Q.txt just says "fsck from util-linux 2.39.1"

My bad, did not realize the output wouldn't be included.

Tried booting with the kernel parameters "nvme_core.default_ps_max_latency_us=0 iommu=soft" - and I still get the same error. I also tried re-seated the drive just to be sure, but the drive is dead.

I will try to salvage as much data as possible with ddrescue and switch to my secondary drive in the meantime.

Thanks everyone!