darias

My guess is something wrong with the latest update of this Docker (7 days ago). I reverted back to the last update (2 months ago) and it's working again. If you want to try this, edit the Docker and change the repository to be: linuxserver/dokuwiki:2018-04-22c-ls41 No warranties, expressed or implied!

This morning I discovered that my parity drive is now showing 31,000+ errors in the Main WebUI. So, my uneducated guess is my new parity drive may be failing/failed? I found my syslog is full of: Tower kernel: md: disk0 read error, sector=3641072456 Oh, and I now see SMART for the disk shows: 197 Current pending sector 0x0032 200 200 000 Old age Always - 26 198 Offline uncorrectable 0x0030 200 200 000 Old age Offline - 26 Can I just get a confirmation that all I need to do is remove and replace the parity drive, and the rebuild will be automatic? I have a pre-cleared drive ready to go already. Is this just a matter of changing the drive assignment through the WebUI? Thanks, Dave tower-diagnostics-20161203-0909.zip

Interestingly, now that I have done a parity check, I cannot recreate the issue. I've tried copying files to all disks discretely, as well as to the array, and I am not seeing the issue. I will test some more tomorrow. Thanks for all the help. Dave

Thanks for the reply. For the copies, I'm going from a directory in /mnt/cache to a directory in /mnt/user. Would it be wise to try to copy direct to each disk (/mnt/diskN)? I will kick off a parity check. To be honest, I can't recall what "normal" speed would be for my system, so I can report back with the results. Thanks for the note on the drive. I have a precleared drive ready to go. Dave

I rebooted the server this morning, and was able to replicate the issues again. I copied a ~700MB file from my cache drive to the array, which took approximately 30 minutes. I did this on the server, with mc, so this is not a network issue. During this copy, I had a video playing on a remote Kodi system, which again suffered from stuttering and buffering. I'm attaching logs from during and after the transfer, in case they may show something between the two. Thanks! Dave tower-diagnostics-20161201-1150_AfterXfer.zip tower-diagnostics-20161201-1126_DuringXfer.zip

I'll go for a reboot tonight, now that a pre-clear is complete. Thanks, Dave

Greetings! I have been experiencing extremely slow writes and reads from my unRAID system, I believe after completing a parity swap. I had to replace a failing data disk, and in the process moved to a larger parity drive (from 2TB to 3TB). Ever since, it seems that when a file is being written to the array, write speeds are slow, and reads are also affected (i.e. playing videos via Kodi results in pausing and stopping). As of this morning, a mover job has been trying to move approximately 80GB from cache to the array. From looking at the syslog, it looks like some writes take a few minutes, while others take 30+ minutes, for files that should be similar in size. I've attached a diagnostics archive from early this morning. I am running unRAID 6.1.4. Any help is appreciated. I cannot figure out anything other than the array writes being the issue, but no obvious cause. Thanks, Dave UPDATE: The parity drive ended up being a shucked WD Green sold as new by a 3rd-party Amazon seller. After replacing it with a new drive, I have not experienced any more issues. Thanks johnnie.black for the support! tower-diagnostics-20161129-0514.zip