So I rebooted the server yesterday and things were fine before and I thought after but when I woke up this morning, my parity drive was in the process of a read-check and had some weird numbers
Temp Reads Writes Errors
*
23,214,889,176,533
0
2558
i have no idea what's going on? THis is a fairly new drive, maybe 3 months old, 8TB, and I precleared it just fine.
I'm on the most recent beta btw
Dec 10 07:52:39 Tower emhttpd: req (6): cmdSpinup=parity&csrf_token=**************** Dec 10 07:52:39 Tower kernel: mdcmd (61): spinup 0 Dec 10 07:52:39 Tower kernel: md: do_drive_cmd: lock_bdev error: -2 Dec 10 07:57:48 Tower emhttpd: req (7): cmdSpindown=parity&csrf_token=**************** Dec 10 07:57:48 Tower emhttpd: error: mdcmd, 2631: No such file or directory (2): write