Skip to contentSkip to conversation

nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed

DISCUSSION J. Hart 1 participant 1 message Dec 18, 2022 NVMe

lore
Share & tools
lore

J. Hart

author
#0 lore raw

The following may be interesting to note:

This afternoon I also tried an fsck check on the smaller partition /dev/nvme0n1p2 (the 64MB one). I made sure it was not mounted and repeatedly ran fsck on it without anything else between runs. The results would alternate between reporting no damage, and reporting damage present. Both occurrences were frequent.

J. Hart

Quoted 2 lines

I have done an fsck check on the /dev/nvme0n1p3 file system after the rsync invocation referenced earlier. In the first run I found errors which fsck should have repaired if I understand correctly. In repeating the fsck invocation immediately afterwards, I found errors again each time. This was done using the replacement Samsung nvme ssd (Samsung 970 EVO Plus 500G).