acurcione

Ah. Well, I ordered some new ram anyway. I haven't had any errors elsewhere, but it can't hurt. I'll run a very long memtest when I get them and then run preclear again. If I still have problems it's either the drive or something else as you state. I just don't want a chance for data corruption!

Wow. Ram prices sure have dropped since my build. Should I just buy new ram anyway? Honestly have nothing else to go on, but Ram was the first suggestion to my other issue as well. Figured a 3 hour passed memtest was good though.

Been running with it for 2 years and I just ran a memtest for 3 hours with no errors. How the heck do I determine if that's indeed the problem?

I didn't know this post existed so I started a new one - sorry about that. I can always remove that one if needed. Anyway, here's the post in it's entirety: I added a new drive (4TB WD Red) to the array so I can use it to do the file system swap thing so first thing I did was try to preclear it. I used the plugin this time instead of doing it on the console and I just used it with the defaults. I'm pretty sure when I first built this in 2014 I used some parameters with the preclear script, but darned if I can remember what or why. Anyway, I ran a 3 pass preclear and after 84+ hours it says it failed because it detected non-zero bytes. I have no idea what to do at this point. Should I run it again with some parameters? If so, could someone enlighten me as to what cause I can't seem to find that part anymore. Attaching the output from the preclear. It doesn't seem to allow me to paste it all in here. Also, before anyone says check RAM, I recently did a 3 hour memtest at someones suggestion for trying to determine the cause of another issue which led to me wanting to change the file system over to XFS. The memtest came back fine, BTW. Just found this, if it helps: = Post-Read in progress: 99% complete. ( 3,998,790,656,000 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:15 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,998,990,745,600 of 4,000,787,030,016 bytes read ) 67.0 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:21 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,190,835,200 of 4,000,787,030,016 bytes read ) 66.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,390,924,800 of 4,000,787,030,016 bytes read ) 65.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:32 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,591,014,400 of 4,000,787,030,016 bytes read ) 66.8 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:38 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,791,104,000 of 4,000,787,030,016 bytes read ) 67.3 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:44 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,991,193,600 of 4,000,787,030,016 bytes read ) 65.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:50 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,191,283,200 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:55 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,391,372,800 of 4,000,787,030,016 bytes read ) 66.1 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:01 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,591,462,400 of 4,000,787,030,016 bytes read ) 67.5 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:07 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 84:59:13 ========================================================================1.15 == WDCWD40EFRX-68WT0N0 WD-WCC4E7ZUZET9 == Disk /dev/sde has NOT been precleared successfully == skip=2273000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2287200 count=200 bs=1000448 returned 00008 instead of 00000 skip= 2301600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2316000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2330200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2344600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2358800 count=20 0 bs=1000448 returned 00008 instead of 00000 skip=2373200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2387400 count=200 bs=100 0448 returned 00008 instead of 00000 skip=2401800 count=200 bs=1000448 returned 00008 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 123 0 ok 31 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/usr/local/emhttp# preclear-052016.txt

IIRC all you have to do is download the ubooquity.js file and toss it into the appdata (overwrite the existing file) Thank you!

here see search tips in my sig Thanks! No idea why I only came up with 2 posts when I searched for "ubooquity". Weird.

Are you going to be updating the Ubooquity Docker with the latest version (1.9.0)? I got a message in Ubooquity about a new version available. It hasn't been available long though. Or is it simple enough to manually update it? I thought I had seen that somewhere, but haven't been able to find it this morning with searching. So if someone knows and can spell it out for me, that would be wonderful. Thanks.

Interesting. It definitely doesn't have everything in it I don't think. { "device_name": "unRAID", "listening_port" : 5555, "storage_path" : "/config/.sync", "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "webui" : { "listen" : "0.0.0.0:8888" } } When I first installed this I used an existing btsync directory from a plugin so maybe that has something to do with it. Unsure though. Also, I had actually tried initially to change the device name, but that didn't hold either so I just left it. Changes made for example, I changed options to show a few more columns (send, receive), but after reboot they disappear. I added them back this morning after reboot, but they aren't showing up in the conf file either. Thanks, can you please try the linuxserver.io btsync release and let me know if the issue still persist. I have joined the linuxserver.io team so I will be migrating and helping support their dockers. Sure. I don't see that listed when searching with Community Applications though. How do I go about getting it? And is there anything I should be aware of when changing from one to another? Anything that might go haywire? ha ha, it's not on there. Okay, I will look into fixing the issue and then I will migrate it. I'll see what is happening thanks for reporting the issue. Ok. Thanks a bunch. I'd be happy to change things if need be, just let me know. I'm a noob with Dockers at this stage!

Interesting. It definitely doesn't have everything in it I don't think. { "device_name": "unRAID", "listening_port" : 5555, "storage_path" : "/config/.sync", "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "webui" : { "listen" : "0.0.0.0:8888" } } When I first installed this I used an existing btsync directory from a plugin so maybe that has something to do with it. Unsure though. Also, I had actually tried initially to change the device name, but that didn't hold either so I just left it. Changes made for example, I changed options to show a few more columns (send, receive), but after reboot they disappear. I added them back this morning after reboot, but they aren't showing up in the conf file either. Thanks, can you please try the linuxserver.io btsync release and let me know if the issue still persist. I have joined the linuxserver.io team so I will be migrating and helping support their dockers. Sure. I don't see that listed when searching with Community Applications though. How do I go about getting it? And is there anything I should be aware of when changing from one to another? Anything that might go haywire?

Interesting. It definitely doesn't have everything in it I don't think. { "device_name": "unRAID", "listening_port" : 5555, "storage_path" : "/config/.sync", "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "webui" : { "listen" : "0.0.0.0:8888" } } When I first installed this I used an existing btsync directory from a plugin so maybe that has something to do with it. Unsure though. Also, I had actually tried initially to change the device name, but that didn't hold either so I just left it. Changes made for example, I changed options to show a few more columns (send, receive), but after reboot they disappear. I added them back this morning after reboot, but they aren't showing up in the conf file either.

Any reason why Sync wouldn't be holding on to preference changes after a reboot? I have the following mappings in the plugin: /config --> /mnt/cache/appdata/btsync/ /mnt/user/Media --> /mnt/user/Media You can see I'm pointing the config directory to the cache drive, but I get the feeling it isn't actually going there. I did see that after a reboot this morning (after unRAID update) the btsync.conf file had the proper timestamp, but after making changes to preferences in Sync it didn't change. Also, and not to rush or anything, are you working on getting it set to auto update to the latest? Thanks.

Awesome! Thanks a bunch. I appreciate all your work keeping things up to date and providing great feedback and support.

I need to update it via docker, I haven't updated it in awhile. I will try and update it shortly. I haven't really kept up with it ever since they went into a paid model, I'm looking for something free and opensource that will do something similar. Ah. Ok. Well, I happen to use it still as a free model since I only share a few folders and use it strictly to auto-backup my main media array with movies, music, tv. But if nobody is going to maintain this because of that, I may look to something else as well. I looked at syncthing, but it still seems to be a bit to early in it's development to trust several TB to. I guess there's always the other repo out there, but of course I have no idea if it's compatible with what you did or not! Ughh...

Another stupid question about BTsync - Why does the gui always say there's a new version available? And speaking of new versions, how is this thing updated in the future? Via the docker admin panel?

Nevermind. It looks like I had to remove all the folders from both sides in Sync. I have one online now and indexing. Again. Something I just don't understand since all the damn folders were already indexed!! Oh well. I'll do one at a time to make sure nothing goes completely stupid.

Well this isn't going so well. First, no matter what I do I can't get either machine to see the peers now. I even tried to turn on uPNP, but after restarting Sync that setting goes away. I have no idea if it's a port thing or not, but I'm guessing maybe. Do I need to put in a port forward on my router or something? if so, from what to what? Also, I've tried manually adding folders in on the unRAID side and that hasn't gone very well. If I manually add them I keep getting "pending approval", but the key I'm copying from the other machine has that turned off so it shouldn't even be asking. BUT I never see anything on the other end to allow me to approve. Maybe this is because of the port??? Help...

Thanks for the super fast reply! Ok so you're saying map /sync to /mnt/user/Media and then also another mapping as you stated? And yeah, I'll back that directory up. When I moved from 1.4.x to 2.x it got completely hosed because of all the changes in BTSync. I was hoping that keeping in the same family might keep that from happening, but if not so be it. Mostly I just don't want BTSync to re-index every damn thing again!

Question about BTsync. I've been running the latest BTsync as a plugin, but want to move it to a docker container. I currently have config data on my cache drive here: /appdata/btsync I'm assuming that when I configure the container and point the config directory here everything should be picked up yes? Also, in your notes you mention a sync directory: /sync : this path is where Bittorrent Sync will share files from. Is this the same as the default folder where Sync would setup new shares, if enabled? Or is it something else entirely? My default location is /mnt/user/Media. Thanks in advance. This will be the first docker container for me and I'd rather not mess it up!

Weird. Wonder why it works for some and not others. I have no idea if method 1 would log anything that might be useful. Hopefully @limetech can chime in here and give some insight.

@limetech Thank you for this! I was holding off upgrading from 5.0.5 until this came out of beta and this plugin worked perfectly. Not sure why others are having issues though. I stopped the array and backed up prior to running the commands though. Just in case! Anyway, thanks again!

I'm not any longer. I think if it shouldn't be used, the option should be removed though.

Actually, I believe that Cache_Dirs still has a benefit for these users in that it pre-caches rather than waiting for your first access. My Movies collection is still small compared to many here. However, split across three drives, there is a delay of about 20 seconds on first access. For those who can keep their system up for months on end, this is a non-issue. However, if you experience multiple power outages a day, it is a significant aggravation. So are you using it with "scan user shares" set to yes or no then?

I suspect that there are many users who have installed Cache_Dirs, but don't actually need it. If access to your files is solely through the User Share system, and you don't fall under the NFS exception mentioned by WeeboTech (learned something new today!), then you don't need Cache_Dirs. The User Share system acts as a Cache of Dirs, because it is the merger of the individual disk directories, kept in memory. And if you do access your files at times directly from the disks, but don't have any programs that poll those disk directories and you only rarely 'explore' them (with a file manager, such as Windows Explorer), then you don't strictly need Cache_Dirs either. Cache_Dirs may add some convenience though, because if you do feel like browsing through the directories of any disk, Cache_Dirs will have them in memory and the drive won't have to spin up. I recommend reading the original document on Cache_Dirs, Keep directory entries cached. It's a little dated, but still helpful. If you need to access a file, for example to play it, then you are asking for the content of the file, and that isn't cached. So the disk it is on will have to spin up, causing the delay on first access you see. Thanks Rob. Yeah, I pretty much think I don't need it based on that article. The only time I access the disks directly are when I'm being anal and double checking things. And I probably shouldn't even be doing that. Having said that, I'm a little disheartened that documentation isn't better OR at the very least setup for a newbie to get a system setup with more ease. I thought I had found that, but it seems even that walk through is outdated. It's unrelated to this though, since this isn't something covered there. After reading about it, it sounded like something everyone should have installed. Anyway, I appreciate the information and I will be uninstalling this since it seems completely unnecessary for how I'm using it. Sent from my iPad using Tapatalk

For now it's dedicated 100% to unRAID. I changed the settings anyway and things are actually OK memory wise. Also, I wasn't actually having any issues when I posted. I was just replying to the OP. But I learned something in the process so it isn't all bad. Something was going on though that I can't explain. I had rebooted this afternoon so all the drives were spun up, but when I just hopped on the server they were all still spun up, including the parity drive, but nothing was accessing the box at that point. Also checked the logs and it showed the spin down event several hours ago, but no spin up event even after I accessed the cache drive to spin it up - even though it's. SSD so in theory it should never spin down even if it shows it. I dunno what that's all about, but I haven't had any issues with drives spinning down. Sent from my iPad using Tapatalk

16GB, 806 movies, 1104 tv shows And yes, my memory is pretty well maxed out, but I figured that was normal. I'm guessing not? Sent from my iPad using Tapatalk