juspifool

Thank you for this plugin!

Finished the rebuild overnight. So far the logs look a lot cleaner after moving the drives off of the Marvell controller and disabling it. Thanks for the help!

I'm attaching the proper diagnotics but after moving the sata cables and disabling the Marvell controller the drive showed back up. I am currently doing a read-check of the array. tower-diagnostics-20180709-0908.zip

Thanks for the quick reply. I'll be sure to grab diagnostics after I boot it back up. I'll also move the drives off of that controller.

One of my WD Red Pros has disabled itself for the 2nd time in a month. The first time I ran an extended SMART test and everything passed. It just failed again this morning so I was hoping to have someone look over the the logs before I take any additional actions. Thanks in advance! tower-syslog-20180709-0815.zip

I ended up moving my parity drive off of the Marvell port. Everything went well after that. Thanks for the suggestion!

Not sure how that happened. I am at 23% on my latest parity sync. Once that either finishes or fails I will upload the correct SMART report. -Mark

All 3 WD drives completed their SMART test without any issues. Attaching the reports. tower-smart-20170216-0752.zip tower-smart-20170216-0755.zip tower-smart-20170216-0758.zip

It definitely made it further into the parity check this time but still failed. I'm going to replace the SATA cable for the drive but was hoping someone could take a look at the new diagnostics file and let me know if there is anything else I should check. -Mark tower-diagnostics-20170216-0704.zip

Thanks for the check. I opened the case and disconnected/reconnected all the drives to be sure the cables were properly engaged. I can now see SMART reports for all WD drives and am currently running a parity rebuild. -Mark

I recently upgraded my server with a new motherboard, CPUs, and ram. Previous to that I upgraded to a 6TB parity drive. This morning I noticed that my parity drive was disabled so I stopped the array, removed it, started the array, stopped the array, added it back, and finally started the array to do a parity rebuild. That lasted a couple minutes then it was disabled again. Looking for suggestions on what to check next. OS: Unraid 6.3.1 Mobo: ASRock Rack EP2C602-4L/D16 CPU: 2x Xeon E5-2670s Partity Drive: WD Red Pro 6TB I've also attached the diagnostics file from the server. Thanks, Mark tower-diagnostics-20170215-1629.zip

I was able to get the drive mounted. I pre-cleared it again, formatted, and let it do a data rebuild. Looks like I lost all the data on the drive (which I didn't have backed up ) but it is back in the array. Thanks for all the help.

I believe this is due to my motherboard treating 2 of the SATA ports as IDE ports. One of my drives is actually an IDE drive so the fact that there are three makes sense to me. Would it be better to remove those two drives from the on-board ports and put them on the AOC-SASLP-MV8 instead?

Completed the rebuild and the drive was still not mounted. I ran the following as suggested: root@Tower:~# fdisk -lu /dev/sde Disk /dev/sde: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 64 2930277167 1465138552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# Looking at the results I am guessing this drive isn't correctly partitioned but can anyone confirm?

It's off and running. I'll update with the status once it completes.