I've had this issue come up twice now on one server, at first i was perplexed as i simply couldn't imagine the nvme drive causing these errors. Could it be related to the 13th gen issues?
https://i.imgur.com/l6vQFum.jpeg
Not sure. But I have recently discovered that some NVMe drives do support self-tests and I was able to start and monitor the test from smartmontools, may be worth looking in to an extended self test.