- Closed
Hi.
The NVME controller cache sems like its malfunctioning and so i'm posting a report, as requested.
I'm also going to post everything that has led up to this.
So ... I upgraded recently to 6.11.0 from 6.10.3. Apparently had no issues, so i upgraded right away to 6.11.1, finished the upgrade and then to visit my mother (2/3 days). When i came back, i had the W11 VM paused. Worried, first thing i did was check the logs and the state of the cache drive, and by instinct, backed up everything from the cache on the array. That was the right call ...
Later i found out the cache was corrupted. Very odd, but it could happen. Formatted the drive, restored the files, but the errors kept appearing. However i started to notice ... things. Like how the corrupted files "moved". Suddenly, the cache upped the unrecoverable sectors from 45 to 225.... So i decided something drastic (and desperate).
I had a W11 VM with a nvme passthrough, and that nvme has the same capacity as the cache.
So now i'm trying to fix things with it, hence the bug report.
Previous Cache: Samsung EVO 860 (500Gb)
New Cache: Samsung PRO 970 (500Gb)
As for the diagnostics, its attached. However keep in mind that VMs and Dockers are off (i'm still trying to restore the cache).
Post Scriptum: i even booted the VM from the array (i know, i was desperate to get my data off the 970). I didn't notice this error then, but it was giving me problems as well, so i'm wondering if it even is affecting the passthrough. Had no issues on 6.10.3.