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

[J. Hart]

As I mentioned in an earlier note, I have updated the util-linux and 
e2fsprogs packages to see if that makes any difference.  The versions I 
was using were rather old.  As expected, it unfortunately did not help, 
although it was a much needed update.

I am out of things to try.

My apologies for being rather a pest about this, but I was hoping I 
wouldn't have to scrap the time and money I put into it. I'll leave you 
all undisturbed and make no more requests of you.

With Thanks for your kind attention,

J. Hart

On 12/19/22 11:45 PM, Keith Busch wrote:
> On Sun, Dec 18, 2022 at 09:08:19PM +0900, J. Hart wrote:
>> Here are some consecutive fsck runs done on /dev/nvme0n1p3:
>>
>> -bash-3.2# fsck -f -C /dev/nvme0n1p2
> 
> I'm having some trouble following some of this. You mentioned nvme0n1p3
> corruption, but then show nvme0n1p2 instead. Could you possibly relay
> your recreation steps starting from a freshly formatted nvme drive?
> Partition setup, device mappers, filesystems, mount options, etc.?