allischalmersman

Bump. Any help with this? How can I fix this problem without deleting everything and starting over? Thanks guys

Hi Guys. Sorry I guess I didnt configure my Dockers correctly. I did not set the mappings to use the cache pool and instead they created a share named appdata. As such they are keeping 2 data disks and my parity disks spun up all the time. The two dockers are CrashPlan and PlexMediaServer. How can I move the /config map to the share drive without loosing my Plex library, etc. Thanks for your help, Andrew

I did a Google search for that error message and it brought me here: https://support.code42.com/CrashPlan/4/Troubleshooting/Connections_Between_Computers Looks like there are a lot of potential causes for this. Since you can backup from your desktop to unRAID, it is unlikely the problem is with the unRAID docker. More likely an issue on one of the routers, or the firewall/antivirus software on your father's computer. I dissabled the antivirus and firewall on his computer with no effect. Would you suggest I do port forwarding on the routers? I can expirement tonight. I have his computer on my right monitor via teamviewer so I can mess around

Ok very new user here. Set up crashplan on UnRaid and successfully (I think) have the backups running for my main desktop backing up onto CrashPlan on UnRaid. Now I'm trying to allow one of my fathers computers at his house to backup onto Crashplan on my Unraid server at my house. I put my computers access code into his and both Unraid and his computer show the other as friends/ destinations, yet it says waiting for connection. I dont understand. Both see the internet, disabling firewall didnt help. I also did some searching and followed some steps to verifying ports were listening and they were. What am I doing wrong? Is it something stupid? Thanks, Andrew

Sorry guys I didnt realize posting from Tapatalk was using a different username. I can confirm that the issue is not related to files being played from just 1 disc. I am having the issue regardless of which disc is being read

Frank1940 thanks for your help. Well that was fun lol Installed AMD3870K and running at 4 cores @ 3.3 GHz..... no change still stutters Reset all network switches and router (should have done this before...)....still no change Installed Intel PRO 1000 NIC and (after disabling onboard NIC) ...... BAM my Dune HD works again! Thanks everyone!

I have seen some "drops" actually. Well since you bring up CPU performance I will try that first just for scientific purposes lol. I have a AMD dual core 2.7 GHZ I am getting ready to replace with a 4 core 3.0 GHz that is the hottest processor I can get for that socket. I may even overclock it slightly as I have a nice Noctua cooler to put on it. I will do this CPU experimenting before I try the Intel NIC card. I want performance to be as best a possible so I may still use the Intel NIC if it will increase performance. But I would like to know if the issue is exaggerated by low power CPUs. FYI I killed all the other tasks I had going on and trying to stream was very low on CPU usage yet problem still occurs. Ill let you know how the swapping goes! Thanks for your help!

Yea I referenced that thread in my original post. That was a beta version. So its still assumed to be a realtek issue? I will post back tonight with results after putting in this Intel NIC I have. What changed in V6 vs V5 that caused the realtek chips to have issues? And why does it not happen doing any other tasks? Transferring large files, etc no issues. Not trying to be a pain, just curious. Thanks!

Well I just found an Intel Pro/1000 GT adapter in my parts collection. I may throw this in the server tonight and see how it goes. All input still welcome! Thanks, Andrew

Hello. Poking my head back on here as you guys have been very helpful to me here recently. I try to read and find problems on my own but here is a question. Upon upgrading my server to V 6.1.8 from version 5 I have now discovered that my Dune HD doesnt play. Im having unusable playback issues as frequent freezing, stuttering, and audio dropout. I have had NO problems ever in the past. I have gigabit network all the way to the dune which is 100mbps itself but again, no issues ever in the past. I found this thread http://lime-technology.com/forum/index.php?topic=39350.0;nowap which describes my issue exactly but this is referecing a beta version. Is this my problem also you think? Does V6 just not work with Reatek drivers? Here is the realteck info on my motherboard. Again, no hardware changes have been made. It always worked before with no playback issues. 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards Kernel driver in use: r8169 Kernel modules: r8169 Do you think there is a high probability that this issue would be fixed by purchasing an intel NIC? I actually have an Intel NIC laying around here somehwere but im 99% sure it's 100mbps. I could use it as a test though. As always, Thanks for your help in advance!

Swapped the Samsung drive into the same bay that the Seagate successfully cleared was in. Both bays are on the same back plane. Same errors, same lack of performance.

Well upon trying to post a log and exceeding 192 KB I unziped and found my syslog was 10MB!! Seems I have had a whole bunch of errors going on all day. Guess this drive is toast? Is there anything else that you would like to see or am I correct in assuming trash the disk? Thanks! Andrew PS. Ill delete this crap after you respond so that it doesnt clog up your thread. Here is a link to the folder since it exceeds the attachment limit here. https://onedrive.live.com/redir?resid=775185346CCCDA69!2351&authkey=!AMOQL28Nd5kZUJ4&ithint=folder%2c In the syslog you will see a whole bunch of this Feb 15 17:57:38 Tower kernel: blk_update_request: critical medium error, dev sdi, sector 362150304 Feb 15 17:57:38 Tower kernel: Buffer I/O error on dev sdi, logical block 45268788, async page read Feb 15 17:57:39 Tower kernel: sd 1:0:7:0: [sdi] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 15 17:57:39 Tower kernel: sd 1:0:7:0: [sdi] Sense Key : 0x3 [current] Feb 15 17:57:39 Tower kernel: sd 1:0:7:0: [sdi] ASC=0x11 ASCQ=0x0 Feb 15 17:57:39 Tower kernel: sd 1:0:7:0: [sdi] CDB: opcode=0x28 28 00 15 95 f9 a0 00 00 08 00 Feb 15 17:57:39 Tower kernel: blk_update_request: critical medium error, dev sdi, sector 362150304 Feb 15 17:57:39 Tower kernel: Buffer I/O error on dev sdi, logical block 45268788, async page read Feb 15 17:57:41 Tower kernel: sd 1:0:7:0: [sdi] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 15 17:57:41 Tower kernel: sd 1:0:7:0: [sdi] Sense Key : 0x3 [current] Feb 15 17:57:41 Tower kernel: sd 1:0:7:0: [sdi] ASC=0x11 ASCQ=0x0 Feb 15 17:57:41 Tower kernel: sd 1:0:7:0: [sdi] CDB: opcode=0x28 28 00 15 96 04 88 00 00 08 00 Feb 15 17:57:41 Tower kernel: blk_update_request: critical medium error, dev sdi, sector 362153096 Feb 15 17:57:41 Tower kernel: Buffer I/O error on dev sdi, logical block 45269137, async page read Feb 15 17:57:43 Tower kernel: sd 1:0:7:0: [sdi] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 15 17:57:43 Tower kernel: sd 1:0:7:0: [sdi] Sense Key : 0x3 [current] Feb 15 17:57:43 Tower kernel: sd 1:0:7:0: [sdi] ASC=0x11 ASCQ=0x0 Feb 15 17:57:43 Tower kernel: sd 1:0:7:0: [sdi] CDB: opcode=0x28 28 00 15 96 04 88 00 00 08 00 https://onedrive.live.com/redir?resid=775185346CCCDA69!2351&authkey=!AMOQL28Nd5kZUJ4&ithint=folder%2c Feb 15 17:57:49 Tower kernel: sd 1:0:7:0: [sdi] Sense Key : 0x3 [current] Feb 15 17:57:49 Tower kernel: sd 1:0:7:0: [sdi] ASC=0x11 ASCQ=0x0 Feb 15 17:57:49 Tower kernel: sd 1:0:7:0: [sdi] CDB: opcode=0x28 28 00 15 96 0f 70 00 00 08 00 Feb 15 17:57:49 Tower kernel: blk_update_request: critical medium error, dev sdi, sector 362155888 Feb 15 17:57:49 Tower kernel: Buffer I/O error on dev sdi, logical block 45269486, async page read Feb 15 17:57:51 Tower kernel: sd 1:0:7:0: [sdi] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 15 17:57:51 Tower kernel: sd 1:0:7:0: [sdi] Sense Key : 0x3 [current] Feb 15 17:57:51 Tower kernel: sd 1:0:7:0: [sdi] ASC=0x11 ASCQ=0x0 Feb 15 17:57:51 Tower kernel: sd 1:0:7:0: [sdi] CDB: opcode=0x28 28 00 15 96 0f 70 00 00 08 00 Feb 15 17:57:51 Tower kernel: blk_update_request: critical medium error, dev sdi, sector 362155888 Feb 15 17:57:51 Tower kernel: Buffer I/O error on dev sdi, logical block 45269486, async page read Feb 15 17:57:53 Tower kernel: sd 1:0:7:0: [sdi] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08

Am I doing something wrong? I can only get 1 preclear to run at a time. I told the process to start on 2 drives, but it will only run on 1 or the other. The second drive stays paused. Is this some setting I have messed up? Thanks, Andrew

Ok thanks. Will do. I usually do have a hot 3 pass preclear drive ready but 2 days ago decided to make it a cache drive as I had never previously used a cache. I need to get another hot spare. Thanks!

Ok! Here is the attributes for the disk that is showing me a orange triangle on the dashboard tab. Number 187 is highlighted in yellow. # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 118 099 006 Pre-fail Always Never 174541792 3 Spin up time 0x0003 092 092 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 887 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0 7 Seek error rate 0x000f 070 060 030 Pre-fail Always Never 11828431 9 Power on hours 0x0032 066 066 000 Old age Always Never 30088 (3y, 5m, 5d, 16h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 32 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 089 089 000 Old age Always Never 11 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0 189 High fly writes 0x003a 089 089 000 Old age Always Never 11 190 Airflow temperature cel 0x0022 081 058 045 Old age Always Never 19 (0 2 22 17 0) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 11 193 Load cycle count 0x0032 055 055 000 Old age Always Never 91166 194 Temperature celsius 0x0022 019 042 000 Old age Always Never 19 (128 0 0 0 0) 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 2062h+11m+53.584s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 46156149712796 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 163771859904553 ST3000DM001-9YN166_Z1F0PM60-20160213-1027.txt

Here is the download from the Diagnostic tab. Thanks again guys! PS. I've canceled the parity sync until I hear from you guys. I don't know if its writing corrections or not. I didn't see the option to uncheck write correction. tower-diagnostics-20160213-0154.zip

I have never had any issues with Unraid or my server. Always operated correctly, never failed a parity check, nothing. I just upgraded to v6 and now immediately after starting parity sync its telling me that my parity is invalid. What the hell did I do wrong? I read the guide on the wiki step by step and did a flash drive format. All help and suggestions much appreciated. I really hope I haven't lost anything. Thanks, Andrew I am attaching the system log download as I am assuming you gurus can decifer what some of it means. I am an Unraid newb when it comes to this. Like I said Ive never had any issues before. Any and ALL help much appreciated! Andrew tower-syslog-20160213-0151.zip