Leaderboard

@limetech , @jonp , @eschultz How does one disable the display of user Avatars on forum posts? Why would I ever want to do that you ask? It's because I'm noticing extremely annoying ANIMATED avatars used by new users that I find extremely distracting to the point of them ruining the forum experience.

Dontlookoverthere over on the unRAID subreddit figured out how to get the plugin running again with a simple edit to the plg: https://www.reddit.com/r/unRAID/comments/7wjpus/preclear_working_on_641/ Caveat emptor and all that. I'm testing it on a drive in my server presently, it seems to be working properly. ohlin5 in the same post has provided an installable version that works with 6.4.1 and should maintain backwards compatiblity here: https://raw.githubusercontent.com/dohlin/unRAID-plugins/master/plugins/preclear.disk.plg

I understand where you are coming from, but your concerns are largely unfounded. 1. Flash drives as license media aren't particularly prone to failure, since unraid doesn't actually run off the drive. Great care has been taken to reduce writes to the flash to an absolute minimum, and reads aren't done often, most read activity is at boot when the OS is read from the USB and loaded into RAM. I'd say average life expectancy of a quality USB key for unraid is over 5 years. I personally have a couple that are older and still running fine. I realize that doesn't help if your key fails, but statistically it's not a big concern. 2. When the flash drive fails, and you no longer wish to run unraid for whatever reason, your data is quite safe. Any decently technical person could spin up a server using totally free software and get access to all the array data in a very short period of time, basically as long as it takes to install and set up practically any linux OS. 3. Limetech has been in this arena for MANY years, and has expanded operations greatly in the last 4 years. During that time they have always been more than fair to their customers, it feels more like a family than a tech company. As a newcomer, it's not possible to see this from the current state, you really just have to experience it over time. Every policy decision that could have been made differently have come down on the side of keeping the majority of customers happy, after discussion on the forum. 4. I can't point to a post, and maybe it wasn't stated publicly on the forum, but I'm pretty sure I remember Tom saying in the past that if the company ceases operation, he would release the licensing and code into the public domain. Maybe @limetech will comment, but that's how I see things after being around here for 10 years.

@gfjardim any interest in a bounty to restore the preclear functionality within current Unraid? The patched Joe L. Script works, but this plugin is sublime.

This isn't correct, unless your drawer is 80°C warm - every 10°C halves the retention time but starting from a quite significant number of years at room temperature. The majority of products you buy and have around you have their firmware stored on MLC flash. Your DVD player, amplifier, mobile phone, ... aren't considered unreliable after 1 year. Temperature matters a lot - but your flash drive will not have to suffer the same temperatures as some devices in vehicles. Said by an engineer who develop hardware with flash-based firmware and file systems for use in infrastructure and with 10+ years expected lifetime in the field. And not just having 10+ years of expected lifetime - lots of the equipment have already been out for 10+ years with the software in MLC flash. I obviously have to spend time with the actual flash memory datasheets when selecting what components are selected for the next generation hardware since I can't rely on personal guesses. For normal use, it isn't retention but number of erase cycles that counts, and how well the flash controller spreads the wear. Anyway - best is to buy small and old flash drives of known brands to reduce the probability of TLC flash.

It appears that life has interfered with @gfjardim 's ability to be to support this plugin at the present time. He does occasionally log into the forum but it has been sometime since he has posted anything. So it appears that if you want to use this plugin with the most recent versions of unRAID you are going to have to patch the plugin's .plg file before installing it or use the link for the updated file that was posted up on Reddit by a user (ohlin5 ) who folked it over on github. Of course, the $64 question is-- will he continue to maintain it. (Granted this last round of problems was caused when the version number of gcc because of changes to it but we can probably expect more of these types of problems.) So each of us are going to have to pick what he/she wants to do as there are a minimum of four ways to go that I can think of right off the top of my head. (No, I am not going to post them as there will be immediately several posts with another one or two ways in each!) Oh, one more thing. Could someone download both versions and run the Linux command that lists the differences between these two files to make sure that the change documented is the only one! (I would do it but I have forgotten the command...)

*If* it was indeed CA that crashed your server, then it's only ever happened for you. CA is arguably the most stable and bug free of any plugin for unRaid. Far far more likely that you have bad memory, power supply, etc and that it was a coincidence.

You can use midnight commander (mc on the console), it will show a progress bar with ETA.

unRAID only connects to LImetech for a trial license. An unRAID installation using USB with an purchased .key file does not require to have an external internet connection in order to fully function. So once you have a key set up, it will continue to work regardless. Wriiting to USB is not frequent. The software installs to RAM and runs from there. There are files on the USB that describe the server configuration, disks, shares, etc, and they get updated when you make changes. Small changes are made when you start and stop the server, so that it knows whether the filing systems were shut down cleanly or not. Other writes are typically for plugins that you may install and they may have their own write behavior, athough some will primarily be writing to shares or perhaps to a cache drive. I take your points regarding data retention and SLC vs MLC, TLC, etc. In my experience, (40 years with EPROMS, 20+ years using flash) leakage issues are rare, and are mostly a high temperate / high usage issue. Yes, there are wearout mechanisms, but the frequency of writes in a typical unRAID sytem is really quite low. I don't have hard data, but a significant number of the failures reported on the forums are mechanical in origin - sticks being physically broken. Hint, use a very short stick, or if available, an internal USB socket. Lastly, since the disks in the server are directly readable by pretty much any modern Linux system as @jonathanm pointed out, I see this as a non issue. So long as I have my data in 5 years or so, that is too far away for me to worry about whether my sever is going to use unRAID or something else. Having said that, if unRAID still works, the chances are high that I will still be using it.

Dang it, sniped!

Excellent, I knew it was probably a simple patch to get this going. Thanks for testing. Sometime when I get time I will upgrade to 6.4.1 and give it a try.

Doesn't seem to. Tmux is probably being used in order to show the progress window (that's the only reason I can imagine that it's needed). And I'm running a preclear right now - and it's being used and outputting progress: root@Phatstore:~# uname -a Linux Phatstore 4.14.16-unRAID #1 SMP PREEMPT Wed Jan 31 08:51:39 PST 2018 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux root@Phatstore:~# ps axu | grep tmux root 17733 0.0 0.0 27864 6304 ? Ss 11:28 0:06 /usr/bin/tmux new-session -d -x 140 -y 200 -s preclear_disk_5VP8L3B3 root 27355 0.0 0.0 9764 2108 pts/3 S+ 13:33 0:00 grep tmux Included is a screenshot showing tmux installed by preclear_disk in nerd tools, and the current progress report.

Scripts nowadays should really make use of the built-in notifications system. This provides notifications not only by email, but several mobile agents and the browser too.

That is what creates the previous folder, you can still downgrade following the instructions I posted above.

Take the Plex-Docker from Linuxserver.io I use this too - thats the best supported one. An assigning is not necessary - the docker will do this automaticly. You can install it over the app tab at the unraid-GUI

I was dealing with a similar decision this past week (Ryzen 7 vs i7-8700). I ended up going with the 8700 since I could pass the integrated GPU to the plex docker for transcoding. After getting it running and seeing how well plex runs with hardware acceleration (leaving the CPU for other tasks), I feel like I made the right choice.

To point #2 this assumes the user has a second system that is compatible with the software, and they want to run that system for an extended period of time (presumably without restarting it, etc). There is some advantage to doing a preclear on an unRAID system, especially if the intention is to add the drive to the array if it passes testing.

If you have a share you can access - drop the file there and then move using your preferred method of moving files. That should work. Additionally - those files are entirely text so you can certainly cut and paste the info directly into your preferred text editor (like nano, vi, etc mentioned above) and save it in the location you want it.

@Twisted - Just seeing this thread. The write verification failure is not something to ignore. Drives should never ever allow data to be returned that is different than what was written to it. And here we have a case that zeroes were written to the disk and the very next read it is returning something else. In theory it is remotely remotely possible, but we are so close to the 0% probability that you should not assume it was normal in some way. In the real world, this never happens. Memory error comes to mind first. Looks like you ran a 6 hour test, I'd run at least 24 hours. The other thing that can cause (in theory anyway) is cables that are run tightly bundled. This can cause the signal to get changed and data can be different than what drive returned. Again - very rare but in theory could happen. Other thoughts include bad cache memory in the drive or controller. I've never heard of such a problem, but something freaky like this could cause data errors leaving the drive. I understand you changed the cables and port, and got a successful preclear. I'm not sure one good preclear would do it for me. I'd run at least several. But I'd go back to the port and try to induce it to fail again there. YOU REALLY WANT A REPEATABLE FAILURE SCENARIO, only then do you have a way to know the problem is fixed. Otherwise you can will ignore that port forever but never really know if it had anything to do with the problem. I would suggest installing some type of checksum collection and testing protocol. There is a plugin that you might look into to collect and check these. If you get a seemingly random checksum failure, that would alert you to an unresolved issue.

Yes there is. Once you have it setup, open cloud commander in your browser of choice. Then click the cog at the bottom of the page (or hit F10). In there enable the toggle box for auth and fill in the required fields.

Any way that the text limit could increase on the Docker / VM section of the Dashboard page? "Transmissio" is the only one of my apps overrunning the limit width: 94px; word-wrap: break-word; In the CSS (Dashboard:352) div.Panel Changing either width to be 100px or removing word-wrap resolves this. But I've had enough of manual CSS tweaks on unRAID, I'll end up breaking something Would any major compat. issues be caused by altering either of those values for the next unRAID release?

I did a quick look into this plugin. The main reason why it isn't working is because of this: https://github.com/gfjardim/unRAID-plugins/blob/900452f0a7c4e2541839a83bbb347eccda0de2f0/plugins/preclear.disk.plg#L394-L406 case $gcc_version in '7.2.0') download_install ncurses-6.0-x86_64-3.txz c04358fd7d7cb0b5ca67f215871f3692 download_install libevent-2.1.8-x86_64-1.txz 9ba9d61dcd90d45719d27b9e7a111913 download_install tmux-2.5-x86_64-1.txz a48783401331620b7c7e5d7af58f53db download_install utempter-1.1.6-x86_64-2.txz aed1f39d4a5acddb225b542145e0eeaf ;; '5.3.0'|'5.4.0'|'7.1.0') download_install libevent-2.0.22-x86_64-1.txz 7a755ece3e378f244a3c327369e7f2ac download_install tmux-2.2-x86_64-2.txz a268019858c88d5f2f702d9fc182a37c download_install ncurses-5.9-x86_64-4.txz c2d2b01f021dc2f4752c4fff02f65fd5 download_install utempter-1.1.6-x86_64-2.txz aed1f39d4a5acddb225b542145e0eeaf ;; From my research, this code needs to be updated to include 7.3.0 and it appears that the file that needs to be added to the list of packages located here: https://github.com/gfjardim/unRAID-plugins/tree/master/source/packages is tmux-2.6-x86_64-1.txz Forgot to mention tmux-2.6-x86_64-1.txz can be downloaded from here --> http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/ap/ I currently too busy with current work commitments to try this out and I am currently running 6.4.0 to test this out, but if somebody likes to hack things, this is what I would try. You would pretty much need to download the tmux-2.6-x86_64-1.txz and unzip it into the correct directory to try this.

Inside Crashplan, you have the folder /storage (you need to scroll down). Do you see it?

Are you changing it in the Qbt WEBUI settings or the container? Edit: I found I had the same issue as you, but was able to figure it out. With the base settings, any time you change the port in the QBT interface, it will reset to 8080 when rebooting the docker. To fix this, you need 2 changes from the default config. Remove the original 8080:8080 port map create a new one 6666:6666 (whatever your new port is) add a new variable Key: WEBUI_PORT Value: 6666 (again, whatever your new port is) apply this and your UI should now work on the new port. However, clicking WEBUI on your docker in the UnRaid UI will yield a webpage opening with :8080 which won't load. I'm still trying to figure out how to change the default webpage since it seems hardcoded to 8080. Hopefully this helps you or anyone else trying to change their port! edit: I figured out that I had the view on basic. Switched it to advanced, and I can change the default launch URL as well. That should fix all the issues for everyone. Woot!