acurcione

Last stupid question. Now that I found the mount and selected it, all my drives are spun up. Will they all stay up for as long as it takes to back up or will unused drives spin down? Cause if they’re for no to stay up I don’t think it’s going to be a good idea to backup 7TB online. I know it’s going to take quite a while. Or or should I be backing this up at the disk level instead of one huge share? Honestly not sure.

Wow. I feel like an idiot. I didn’t even notice the scroll bar on directory listing. Thanks for that. All good now.

I just installed this so I can backup my media, but can’t seem to see my media directory in the GUI. I see the root contents and directories, but nothing else. I have /storage mapped I the app to /mnt/user/Media, but I don’t see it in the GUI either. What am I doing wrong here? and I have successfully backed up flash and config so I know that’s working at least.

I've been using cache_dirs for some time now and thought it was working properly until today. I went to pull up my main media directory which houses pretty much everything and Windows Explorer just hung there for a few seconds before showing the directory at the top level. I had unRAID up in the browser and sure enough all 4 of my drives spun up just to get a listing. On unRAID 6.3.2 and cache_dirs 2.1.1. I don't see anything in the logs to indicate a problem. Anyone care to shed some light? Settings attached.

Hello????? Is anyone out there? This is still happening. *** Shutting down runit daemon (PID 22)... XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" after 2120 requests (2120 known processed) with 0 events remaining. ./run: line 20: 39 Killed $JAVACOMMON $SRV_JAVA_OPTS -classpath "$TARGETDIR/lib/com.backup42.desktop.jar:$TARGETDIR/lang" com.backup42.service.CPService > /config/log/engine_output.log 2> /config/log/engine_error.log Is the developer anywhere around????

I keep getting a fatal error of some kind and then Crashplan just terminates. This has happened 3 or 4 times now. This is the error from the log: crashplan ** Shutting down runit daemon (PID 23)... XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" after 2120 requests (2120 known processed) with 0 events remaining. ./run: line 20: 37 Killed $JAVACOMMON $SRV_JAVA_OPTS -classpath "$TARGETDIR/lib/com.backup42.desktop.jar:$TARGETDIR/lang" com.backup42.service.CPService > /config/log/engine_output.log 2> /config/log/engine_error.log *** Killing all processes... I looked for the engine_error.log file mentioned in there hoping it would show more, but it's completely empty and has a date from December last year so it doesn't look like anything was written to it. Anyone care to point me in the right direction?

You've already said that so you're one of the lucky ones. Can we get the developer to chime in here or do we need to reach out on GitHub? Sent from my iPad using Tapatalk

No, you were correct. For me and at least a few others in the thread, Crashplan won't autostart in the docker. It throws that error every time. However starting it manually works every time.

Hmm. Well why would some people have the same issue with the same error? I don't know of a way to add that package. Sent from my iPad using Tapatalk

This has been asked several times and I don't see any answer. Autostart doesn't work with Crashplan. Logs point to this: openbox-xdg-autostart requires PyXDG to be installed What needs to be done to fix this?

So after I posted this I rebooted the thing and ran a single preclear. It finished successfully so the mystery deepens. I still have new memory that should arrive today and since this would be the second unexplained incident, I'll go ahead and swap it. Then test the hell out of it. And I should probably run another preclear cycle once that's all done just to be extra sure, but that might be overkill.

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

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

This was an option left in by Joe to satisfy users who still felt it accomplished something for them, but it is difficult to see the rationale for that. User shares are a file system maintained entirely in memory, so caching them is just making an extra copy of the file system elements in the same RAM. That seems like a waste of RAM, with no benefit. The idea behind Cache_dirs is to keep in memory those file system elements that are constantly being requested from disk, so that the disk does not have to keep spinning up. I would set this to NO and free up some memory. Well I guess I completely misunderstood the purpose of this. The only thing anyone should be accessing are user shares. If the entire user share(s) in memory, then why does it take so long to pull up when it's accessed (at least the first time)? Isn't that the point of this plugin? I mean if your right then I totally did this wrong and should remove the "Media" inclusion AND change that setting to no. But again, this is still confusing based on your comment. Sent from my iPad using Tapatalk

Not sure I'm the best to answer, but since I only recently installed this I'll give it a shot. I'm pretty much using the default settings, although I'm expressly only including one user share where all my media is. Here are my settings: Folder caching function: enabled Wait until array is online: yes Force disks busy: no Suspend during Mover process: yes Scan user shares: yes Minimum interval between folder scans (sec): blank Maximum interval between folder scans (sec): blank Maximum scan level depth: 4 Excluded folders (separated by comma): blank Included folders (separated by comma): Media User defined options: blank Hope this helps. My array is behaving normally and isn't spinning up when it shouldn't.

Wow. I looked at that thread several times and I totally missed that. You description certainly sounds correct and that's how I'm running it so it should be fine. I am still noticing a long delay the first time accessing he shares though so I wasn't sure it was actually cached yet. Sent from my iPad using Tapatalk