jademonkee
Members
-
Joined
-
Last visited
Solutions
-
jademonkee's post in Parity Check notification said 0 errors, dashboard says 1331 errors - what to trust? And what to do next? was marked as the answer(likely) Final update:
The parity check finished with 1329 errors this time (I'm assuming something was overwritten between the previous check and today's).
I shutdown the server and checked the LBA card + cables. Nothing was obviously loose, but I can't say definitively.
After booting, I mounted the disks in maintenance mode and ran filesystem checks on them. No errors found. I'm also running scrubs on my two ZFS pools, just to check.
After the scrubs have completed, I will run a manual parity check with "write corrections" enabled. I have a feeling that the cause was probably the removal and reinstallation of the LBA card, as I can't think of what else could be responsible. Hopefully the errors were all in Parity and not the Array disks.
-
jademonkee's post in Ripping CDs in Windows 11 VM results in distortion; CD/DVD Drive is attached to a SATA Controller bound to VFIO - is this the best approach? was marked as the answerAlrighty! Today I installed the new drive (Toshiba SH-224FB) and ripping/listening to audio CDs works as expected (I haven't yet tested burning etc, but that all worked fine previously so I'm not expecting any problems).
So it was just a quirky hardware combination.
Hooray!
-
jademonkee's post in TRIM no longer working on Samsung 870 EVO was marked as the answerI realised shortly after posting this that I'd gotten the disk mentioned in the error confused with the name of my cache drive. I thought I'd deleted this post (Moderation Actions > delete), but I guess it didn't work.
Looks like Unassigned Devices thought that my external drive was plugged in when it wasn't (and that it needed a TRIM), so I rebooted my server and manually ran a TRIM and it worked without error.
Sorry for wasting your time.
Mods: feel free to delete this topic.
