trurl

While I'm a little late to the party, if your script only needs to run either hourly, daily, weekly, or monthly, then all you have to do is toss the script into /etc/cron.daily (or hourly, etc). The script will then show up by the scheduler plugin (and have the start time easily adjustable), and you don't need to muck around with cron jobs But I think if you take that approach, you will have to move your script there with a command in go or it won't be there next boot.

OK, then maybe I'm missing something super obvious.... Where do I view/edit jobs used with the Schedules plug-in? So if I want to add a cron job, do I then just add it to the Go file so that it's added to cron? I'm likely missing something here, sorry.. The schedules plugin handles the built-in cron entries for hourly, daily, weekly and monthly jobs. These are separate from the custom cron jobs which a plugin or user can define. OK I think I get it... Let me approach this another way since I have already mucked up this thread. I will stop acting like I think I know what I'm doing, as it just makes this worse and confusing (thank you for the responses so far!)... So... What is the best way to schedule a script to run to backup apps, or copy whatever, on a timed basis? I assumed this was now able to be handled by Schedules, which I was wrong. Add to go script? Create the script. Create a .cron file that calls the script, exactly as discussed in the bonienl post which you yourself quoted above. Reboot or update_cron. Done.

So since you don't have any mapping for /mnt/user/music the container has no access. The only thing the container has access to is /mnt/cache/appdata/sync/, which it sees at /config. Get it?

...is mapped to what exactly? And is that the only volume mapping you have for this container? If so, that is the problem since that is the only folder the container will have access to. Do you have any other working dockers? Probably better post a screenshot that shows both the container volumes and host paths for this docker.

What are your volume mappings for this docker?

I see 2 dockers for ownCloud in AppStore (Community Applications).

Rather than allowing users to move pages around, I think it would be a good idea to just put Users under Settings and leave it there since it is seldom used.

I am using System Stats. It would probably make sense to move it to Tools though.

I moved Users into Settings even though I was not having any problem with the layout. Users definitely doesn't deserve a spot at the top. I wonder if the people having layout problems are also using Dynamix System Buttons which uses up some space. I am not using it.

Used the plugin with the fast post-read and notifications enabled version from host site listed. Shows as ver. 1.115c, plugin worked great as has been the case, and pre clear of three new 4TB drives were successful also. 10 hours quicker for each drive than ones done in the past, however I never received any notifications. I had set for both the web GUI pop ups and email. i tried the 25%, end of each step, and end of cycle and never got anything. My notifications are working fine for unraid. Is something broke or did i not do something correctly in setting it up? According to your sig you are not running 6.1.x. This is likely the problem, and you should upgrade anyway. Nobody can support 6.0rc6

Sorry I keep asking Noob questions, I understand the concept of using checksums but have never actually messed with it before. Just to be 100% clear, if I want to have detection and repair (of minor) corruption, I'd choose par2 as my format? Are there Pros/Cons for the different checksum formats? How big is the file they generate (in general), and where exactly are they stored with in the folder scanned? Some of this might be answered by downloading your plugin... par2 is not a checksum. It is one or more additional files that allow missing or corrupt files to be reconstructed. Par2 is used extensively with usenet binaries (NZBs) and the applications that download them, such as SABnzbd, NZBGet. Something like how parity allows a disk to be reconstructed, but much different in the details.

Perfect score

Don't see what exactly post #3 has to do with 4K alignment, since "align" doesn't appear anywhere on the first page of this thread. I can see how you might use the ideas in post #3 after you have aligned a disk. You need to spell out in much greater detail exactly what you are thinking about doing.

Alignment has no effect on drives > 2.2TB.

See here. Then go to Windows Control Panel - Credential Manager and delete any unRAID credentials to they can be renegotiated.

Since you say you are using screen and not the preclear plugin, what does it look like in your screen sessions?

I/O is cached in memory until memory is used up, then it has to wait on the disk. That accounts for the burst at the beginning. Writing to the parity array is always slower than the drives because it must first read the disk to be written and read parity, calculate the change that would be made to parity by the data to be written, write parity and write data. So, 2 reads and 2 writes when writing to the parity array.

Looks OK but I would probably do another preclear cycle. I like to see all zeros on mine.

You can put a .cron file anywhere under /boot/config/plugins/dynamix and it will be added to crontab for you when you boot. See some of the built-in .cron files there for examples.

I think you can just fill in the drivers without actually doing the detect if you know what they are. Maybe search for your motherboard here and google.

If it happens again, take a look on the Dashboard under System Status for the numbers labeled flash : log : docker. Possibly the "no space" device is the log.

Most likely what happened was your plex docker updated when it was started after the reboot, and it is plex that is broken. Probably would have happened even if you did not update unRAID and merely rebooted or restarted the docker. Nothing to do with 6.1.4.

With unRAID 32bit v5 it was definitely possible to run out of memory preclearing. Not sure if it still an issue with 64bit v6. I'm not aware of anyone trying as many as you are suggesting so you may just have to try it and see. Can't imagine you really need all of them at once though so you might go with fewer at one time. Unless you break it by running too many you should be able to use your server for other things while preclearing, such as loading data to the drives already precleared so maybe not that important to do it all at once anyway.

Is it working or not?

There may be a new version of sensors-detect. Unfortunately the www.lm-sensors.org is refusing connections for some reason.