bobokun

I realized what I did wrong, I forgot to rescan the controllers after I swapped the sata cable to connect to my motherboard rather than the SAS2008 controller which is why I was getting those errors when benchmarking.

I ended up connecting more drives into my motherboard and fewer onto the Dell H310 card instead to see if that improves the results. Is this normal behavior for drives or do you still think there is issues with my Disk4/Parity?

Are these all windows tools? Is there a way to run these using docker containers or plugins? Or should I run it in Windows VM. I've been using disk4 since before I installed my dell H310 and even with my dell H310 installed it was running fast, parity checks were fine. It's when I added two additional new drives (10TB x 2) is when the issues started happening. I'm wondering if there is an issue with my H310 controller since it is running 6 drives on it (2 SAS to sata cables, 4 sata connections on one and 2 on the other).

Sent you a PM with the debug file. Thanks

Disk4 isn't a shucked drive. I tried to replace the sata cable for disk4 and parity and connect it directly to the motherboard instead of the DELL H310 controller but now when I run diskSpeed it hangs on disk5 with the message below. Now I'm wondering if there is an issue with my H310 card or if it's my SAS to SATA cables. SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]: Scanning Disk 5 (sdd) at 9 TB (90%) - 0|9999999999|0 (64) Not sure if this helps?

How do I fix the xlmrpclib? Is this something that needs to be downloaded outside the docker? I have nerdtools plugin installed and python-2.7.15-x86_64-3.txz installed. Is there anything else additional I need to install?

Here are new diags while performing parity check. I took these diags as it slowed down to 2.7MB/S unnas-diagnostics-20190610-1813.zip

Yes I tried running it multiple times and the outcome is the same

Hi , I recently had a parity check which took a lot longer than usual. I ran a disk benchmark and found out that the drives for parity and disk4 are really slow but SMART reports seem to show that it's fine. Not sure what might be the cause of the slow parity check. It took almost double the amount of time as it normally does. Please see the attached diagnostics. unnas-diagnostics-20190530-1805.zip

Please see attached HGST_HDN728080ALE604_R6GS94LY-20190530-1805 disk4 (sde).txt WDC_WD100EMAZ-00WJTA0_JEGW7S5N-20190530-1805 parity (sdi).txt

I recently ran a benchmark after seeing my parity check take a lot longer than normal. All my drives have been precleared and are less than 1 years old. My parity especially is less than 2 months old and it's shucked so I can't simply RMA it. Is there something I can do? I'm not sure why the speeds suddenly drop so much.

Traceback (most recent call last): File "/tmp/user.scripts/tmpScripts/rtorrent Cleanup/script", line 18, in torrent_tracker_status = rtorrent.d.get_message(torrent) File "/usr/lib64/python2.7/xmlrpclib.py", line 1243, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1602, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1283, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1316, in single_request return self.parse_response(response) File "/usr/lib64/python2.7/xmlrpclib.py", line 1493, in parse_response return u.close() File "/usr/lib64/python2.7/xmlrpclib.py", line 800, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: This is the error I'm getting. I think specifically "torrent_tracker_status = rtorrent.d.get_message(torrent)"

It wasnt a particular plugin but it was a script I followed previously to make the banner dark : https://www.reddit.com/r/unRAID/comments/9l02a7/tutorial_changing_unraid_menu_bar_colors/

Changed Status to Solved

I tried that and I'm getting errors. Are you using plugin Userscripts to execute the script? At the beginning of the script did you put #!/usr/bin/python? I'm wondering if there is anything else that I missed. What version of python are you using?