March 9, 20197 yr Hello all, I am having a strange issue with my parity drive. Here is what I have done so far and where I am at. Any help is appreciated. Several days ago my parity drive showed disabled and I tried bringing it back by following these steps, which i have affectionately named the Parity Waltz Stop array Remove parity Start array Stop array Add parity Start array This did not work parity immediately disabled. Next I tried stopping the array then shutting down and confirmed all drives in the BIOS, they were. Started the PC added the parity started the array. Still disabled. Over the next few days I tried these things: shutdown the PC replaced cable, and used a different power supply cable booted up and did the Parity Waltz, still disabled. Next I shut the PC down and tried a different sata port. Booted up did the Parity Waltz still disabled. Next I changed all my dockers and VMS to not auto start stopped all dockers and VMs and did the Parity Waltz still disabled. Next I did the Parity Waltz again but did not add the parity back. I shutdown unraid and re-seated EVERYTHING. Booted up did the Parity Waltz, adding the parity drive back and BINGO it started the Parity Check. I manually started the dockers and vms and went to bed. This morning parity check completed but noticed I forgot to start one of the VMs. Started the VM and BAM! parity disabled. Anybody have any idea what my next steps should be? firefly-diagnostics-20190309-1721.zip
March 9, 20197 yr Most of your syslog is errors trying to write sdb1 (cache) so parity isn't the only problem. Is parity and cache on the same controller? Same power cable?
March 9, 20197 yr Author Same controller, different power cable. I do have a dedicated controller card on the way.
March 10, 20197 yr Author For anyone keeping score I am pretty sure it is an issue with the on board controller. I have been running 8 total disk for a while using all sata ports on the motherboard with zero issue before this issue started early this week. After dorking around with several things today I finally just totally removed the parity drive (no power no sata cable) and all the errors are gone. I am even able to move the remaining drives around on the ports with no issues, but for some reason it doesn't like it when I use all eight ports now. I have a dedicated controller on the way, but living on the edge of no parity until then.
March 11, 20197 yr Author New Controller in all the cache drives moved over to it. Still not able to get parity working. As soon as I start the Windows 10 VM the parity disables. firefly-diagnostics-20190311-2204.zip
March 11, 20197 yr 9 minutes ago, NoOneAtHome said: As soon as I start the Windows 10 VM the parity disables. Can you get parity rebuilt if you don't start the VM?
March 11, 20197 yr Author Yes I just stopped the VM, did the Parity Waltz and it starts to build (21 hours). I started the VM and the parity immediately disabled. The VM does work I can VNC via the unraid UI and RDP from my desktop. I can stop the VM again and let the parity build, but in my previous tests it had the same result.
March 12, 20197 yr You are passing through the Asmedia controller to the VM, so when it starts any device connect there will drop.
Archived
This topic is now archived and is closed to further replies.