December 16, 20178 yr Hi, I've recently (~2 weeks ago) replaced a drive in my array. Over the last couple of days, after a few days away (where I had the server powered down) - on reboot, it's showing the new drive as disabled. I did a smart test, and it showed no errors. When I first discovered this I googled the error (afraid I don't recall what it was at the time, stupid I know) but the suggestion was there was a loose or faulty cable - I've replaced this and still get the errors in the log attached. I've started in maintenance mode and checking the filesystem just in case. Just to be clear, the new drive was rebuilt successfully and running fine for about a week or so until power down (clean) and only developed this issue on boot after my return from a work trip. It's connected to the same motherboard port as always. unraid_log.txt
December 16, 20178 yr Author 3 minutes ago, johnnie.black said: Post the complete diagnostics: Tools -> Diagnostics Diagnostics attached. dl-net-diagnostics-20171216-1119.zip
December 16, 20178 yr There are 27 CRC errors for that disk, that's a lot for a relatively new disk, you likely have a bad SATA cable, replace it and rebuild.
December 16, 20178 yr Before rebuilding make sure the emulated disk mounts and contents look correct.
December 16, 20178 yr Author Thanks, I'll do that. It's strange since it went through a full preclear and rebuild and no issues prior to this.
Archived
This topic is now archived and is closed to further replies.