dtempleton

I’ve been out of the country and away from my server since version 6.3.5. I set it up this week and find it still works (one drive failure and a new one preclearing now. The GUI suggests updating to 6.5.3 while CA update requires 6.9+ I have 2 parity drives, 8 data drives and an SSD cache drive. My goal is to run SAB etc, have family backups, and run a PLEX server. My question is whether there is a logical path to updating UnRAID. How can I tell if my hardware supports the newer versions? Is it rational to just stay at 6.3 or am I missing so much that’s silly? I do miss having a working CA to set up a Docker. thanks! Dennis

These are gone on NewEgg but are on the BestBuy website for $139.99 https://www.bestbuy.com/site/seagate-backup-plus-hub-8tb-external-usb-3-0-desktop-hard-drive-black/5450025.p?skuId=5450025

OK, what's the recourse? I'm trying to preclear 2 8 tb drives mounted through USB and get the same 'no space left on device" error. I have 4 gb of memory. Is this an impossible scenario? I've had preclear falures on smaller drives fail also when mounted via USB. When this happens it brings down the entire server. This did not occur when the drives were mounted via SATA along with the array drives, but I'm out of SATA ports and the new drives are still in their shells. Is there a way to enable preclear to work on a USB mounted drive without this error? Thanks

I'm on 6.4.5 and I've noticed lately that when I reboot the server it is very slow to have the WebGUI come up. Today I used the powerdown -r command via ssh (after the reboot button did nothing). It took 30 seconds for SSH to close, and about 4 minutes for the array to come up; I can see this via SSH. That's fine. Now almost an hour later the WebGUI is still not up. I notice that docker -ps gives an error that no docker is found. From recent experience, the WebGUI will be up tomorrow as if nothing had happened. This is not how UnRAID used to be, the GUI came up in about 5-10 minutes and the dockers too. Looking at the syslog it appears that a lot of plugins are being updated (e.g. fixcommonproblems). I would rather do this when I want to, not automatically. Is there something else holding this up? I want to get a preclear going before bed, and this is preventing it. Thanks Dennis Syslog 20171129

+1 for an integrated Docker-compose

Hi all; I'm interested in getting financial data from Interactive Brokers via their API running in a headless docker. I have found a repository that has done this, and they instruct to build this on your server. https://github.com/ryankennedyio/ib-docker.git At this point I realize that with Community Applications and unRAID repos that I have been totally ignorant of how dockers get built. I think I can get the folder onto my server and build it but I'm not sure how to specify the build via the 'add container' page. Note that to function, there is a file that needs to be modified with a specific user account information into a file called docker-compose.yml So here are my questions: Does anyone want to add this to their repository for unRAID? If I build it myself, can I specify the docker file on the server from the GUI? I've looked at the noob guides but they are all oriented towards using CA and repositories. Is there a noob guide for building one from a repository like ryankennedy's on git? Thanks Dennis

No, I don't but it will be on the list to (re)install. As I said I was out of country for a couple of years and did minimal upkeep to the server (6.1) that just kept pluggin... Thanks

The answer to my issue is a conflict with our friend gfjardim's Unassigned Devices; my copy is dated 2015 and I no longer use it. Observant UnRaiders will have seen this alert: I note that some other conflict (not cache_dirs) is causing the slow reboot (i.e. 16 minutes instead of 4). I might figure that out, but will next install the plugins I want from scratch... too many go back to 6.0.0... Thanks for everyone who tried to help. Dennis

I suspect this is on the right track. I renamed my plugins folder and rebooted, and the webGUI works as expected. Just now I restored half the plugins and rebooted to see which is the culprit. Likely I should just make a list of those I want and install from scratch; there are things there I don't recognize. Parenthetically, for those old enough to remember Mac OS 7.5 and earlier, this was an at least annual routine to identify system extension conflicts. Ah, the bad old days. I'll report my findings, but I suspect as you said, it is a non-updated and non-reporting plugin. Thanks Dennis

Thanks, itimpi, that makes sense. Unfortunately (or maybe fortunately) I do not have System Buttons installed or any other Dynamix addins (at least not that I recall, or show up in the plugins or apps page). That leaves me with a base system that fails with system errors: Tower emhttp: error: cmdStop: missing csrf_token Tower root: error: webGui/include/Boot.php: missing csrf_token and prevents me from stopping the array or rebooting. I can't recall if there is a way to reboot with 'extensions off' so I can see if it might be an unsuspected add-on. I'll look today. Dennis

Thanks, Squid, but I'm still a little confused. "System Buttons" is a routine within Dynamix WebGUI? I don't see it as a tool or an app. I also don't know about 'Active Streams' but it sounds like it could be useful. Without the function of Dynamix I don't see a means of having the server on but the array unmounted,or 'officially' being able to restart the server. I might place this basic functionality at a somewhat higher priority than making the server a gaming platform. I will appreciate when @bonienl can update this builtin function. I've followed the debate about whether we will need or use the powerdown script in future. The reboot button has never been reliable in my experience. For two years I maintained my server remotely from 5000 miles away using powerdown via ssh (and an occasional call to a friend to push the reset button). They will take my powerdown script away from me when they pry it from my cold, dead fingers. Thanks again, Dennis

I'm having what might be the same issue. On 6.3.2 I could not stop the array (gave: Tower emhttp: error: cmdStop: missing csrf_token) and could not reboot from the Main web GUI window (gave: Tower root: error: webGui/include/Boot.php: missing csrf_token). Actually the reboot button killed the webGUI and I had to reboot from the terminal using powerdown -r. I saw this thread and the suggestions that some app was not up to date. I updated all of the apps (mostly CA components) and saw the UnRAID 6.3.3 update, so I updated that too and rebooted from terminal with powerdown -r. The server is now up and running but I still cannot stop the array or reboot from the web GUI, getting the same error codes above that I had before on 6.3.2. I don't see any non-updated apps or plugins. I do not have any clients attached to the server. The only thing I think might interface with this is the powerdown script which I understand is on its way out, but is the only way I can reboot the server remotely. I've attached the diagnostics.zip file. The syslog after reboot (and trying to stop the array) is at the end TIA for advice Dennis Apr 22 16:43:37 Tower emhttp: shcmd (94): /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php |& logger Apr 22 16:43:38 Tower ntpd[1506]: Listen normally on 3 docker0 172.17.0.1:xxx Apr 22 16:43:38 Tower ntpd[1506]: new interface(s) found: waking up resolver Apr 22 16:43:41 Tower root: Updating templates... Apr 22 16:43:41 Tower root: Warning: file_get_contents(): Filename cannot be empty in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 146 Apr 22 16:43:50 Tower root: Updating info... Done. Apr 22 16:43:50 Tower emhttp: nothing to sync Apr 22 16:43:50 Tower rc.unRAID[16297][16298]: Processing /etc/rc.d/rc.unRAID.d/ start scripts. Apr 22 16:45:41 Tower kernel: mdcmd (45): spindown 6 <<<attempted stop array>>> Apr 22 16:47:06 Tower emhttp: error: cmdStop: missing csrf_token Apr 22 16:47:10 Tower kernel: mdcmd (46): spindown 7 Apr 22 16:47:19 Tower kernel: mdcmd (47): spindown 1 tower-diagnostics-20170422-1644.zip

Regarding TMM: I thought it might be a Java version issue, since the TMM home page says that it requires "at least 1.7." TMM won't run on my Mac (10.10) since that is 1.61 (IIRC). I looked into the TMM volume, though, and the Java version is 1.8, I think it's a subversion 121. I also tried deleting my TMM config directory, and it just made a new one and still didn't work. I can't parse the error that 'TMM has tried 5 times to download...' with a brand new config directory. Maybe it's just hyperbole, like when I tell my kids "I've told you a million times..." I know Kodi and Plex will scrape (actually for TV I just let Sick Beard do its thing), but for movies the matching algorithm and metadata that comes from TMM is the best for me, and the setup is pretty simple; I do it about fortnightly and it's a time to make sure all the files are clean and usable. Dennis

Regarding TMM, I have the same issue, and I append a log from a failed session Thanks, it has been very useful to me, thanks for all the work you have done for us. Dennis TMM_log.txt

I'm used to using PHPMyAdmin to scan and search MySQL databases when I used MAMP. PHP doesn't seem to be installed in the mariadb docker. What do folks use to look at their databases beyond the command line? My client is a Mac. Thanks

Not unraid related, but while Carbon Copy Cloner is good, SuperDuper is excellent for making a bootable local backup. Mine runs every night and writes and then unmounts "Backintosh" so that if a local boot drive fails you have your work as of last night at 10 PM. Not a replacement for time machine, but a real arse saver. D

Hi; I installed and ran this plugin to successfully clear a disk, which I set aside as a backup. I have another to preclear, and (without rebooting the server) I plugged into the same slot. Opening the preclear plugin page, the drive is detected as sdk, and the correct serial number is presented for the new drive. however, the report says "preclear finished successfully" which relates to the previous drive. I can't figure out what to do to re-initialize a new preclear. I haven't resorted to rebooting the server or reinstalling the plugin, but have tried just about everything else, clicking every link like a self-educating monkey. This doesn't happen very often, of course, but am I missing a switch to run preclear again? Thanks Dennis

Yes, deleting the docker.img was the fastest solution, but it's still not clear what was wrong with the previous docker.img . mine was on my cache drive, not an unassigned device. I did take the opportunity to clean up my docker install by editing the run command. A tidy solution to get scripts stored off the image is to include the command: --entrypoint=\"/container/path/script.sh\" command. I doubt that the quotes need to be escaped.

Only partial joy here. Tried to update from 6.0 (have been out of the country) using the update button on the plugins page, then pushing the 'reboot' button in the webGUI. Failed to start in 45 minutes. Docker process seems to be running but not working (syslog attached shows a hang in docker start). All of this is in the syslog (fourth). A series of restarts always yielded a stable situation in which Docker would not stay open. I suspect that the issue is that my docker.img is 32 gb when there is reference in the syslog to 'max' being 30. A rebuilt (and empty) docker.img is 30 GB, see below. Finally, I renamed my docker.img and rebooted with no mountable image. Docker starts, but the tab in the webGUI is obviously empty. An unpopulated docker.img is created where the old one was. Now I'm facing rebuilding my docker. Most of the containers I can just re-download but a couple are those I have modified. I have backups of everything, but am unsure where I can access those changed containers. For example I modified a Handbrake container to auto-start some scripts to transcode files automatically. I have the scripts, but can't recall which handbrake I used and what start scripts were modified. Your advice will be appreciated Fourth_syslog.txt

I access my server almost exclusively by SSH including SSHfs (works great). Recently I logged to the Main server page and was surprised that one of my drives had died; of course the Parity drive meant that everything kept serving as usual, and was easily recovered with a spare drive. I have no idea how long that drive had been down; it could have been 3-4 weeks, but in the meantime I was logged in via SSH probably 15 times. My request is that when a drive dies or some other dire event happens, that a message be generated that is presented with every login via the terminal. That way I know to go to the manager page and look to see what's wrong. Dennis

This is a report about some unusual activity that I have found using the needo's sabnzbd docker and UnRaid 6.0. I know there are other flavors of both Docker and UnRaid now, but I have not been able to update my server as I am living overseas and managing a server back in the US. (that's another story). Several months ago I commented about some issues I had, and I think other people, about this container crashing for some reason, perhaps overlap with the mover or some kind of memory leak. In my instance it can be prevented by restarting the container every 20 gb or so of downloads. (That thread was https://lime-technology.com/forum/index.php?topic=39510.0 which is marked as 'solved' but nothing in that thread fixes my issues). What makes this interesting is that when this docker crashes it brings down the whole of UnRaid 6.0. (The symptom is that sabnzbd is unresponsive, and the UnRaid GUI becomes unresponsive when I try docker stop sabnzbd or docker kill sabnzbd either via ssh or the web gui. Files seem to be still served). When I mentioned this earlier, Tom, or Jon, or someone said that should not happen, since containers are insulated, and should not impact the system if they crash. Well, when this container crashes it does bring down UnRaid, repeatedly. I can sometimes stop the array and use powerdown -r to restart. I've had some success in entering the container and killing the sabnzbd processes, but often I have to call a neighbor to come and push the restart button... Today, while trying to recover from a system-impacting crash of the sabnzbd docker, I first entered the offending container to kill the sabnzbd process(es) with kill -9 ###. Subsequently I accidentally ran ps -A | grep sabnzbd instead of docker exec -it ps... and I saw a process IN UNRAID running titled sabnzbdplus (defunct). I managed to restart the server and then did some testing. In a fresh restart of UnRaid this sabnzbdplus process doesn't exist in UnRaid, of course. When I start needo's sabnzbd container, the 'sabnzbdplus' process shows up in in UnRaid, and of course the container has several processes with similar name. Closing the container removes the sabnzbdplus process in UnRaid, unlike when the container crashes and the process shows (defunct). Somehow the container is starting a process within the UnRaid system, which it seems should NEVER happen. For my own purposes I will install another sabnzbd container, but it would be interesting to see what it is in needo's container that is causing the sabnzbdplus process to be started in the UnRaid system OUTSIDE OF the Docker container. I'm afraid that it might indicate a security gap where a malignant or poorly-designed container could bring down the system, or run a malignant process that originates within the container. Perhaps this is not a problem with the new Docker or the new UnRaid, but I am not in a position to test that. I'll have my current system running for a few more months if there is some test I could do. I'll try to alert Tom or whoever is running the show these days to this issue. Thanks Dennis p.s. here's a snapshot of what's going on in my system, needo's sabnzbd running fine. root@Tower:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f9cbe66e92e9 pinion/docker-handbrake-cli:latest "/sbin/my_init" 9 months ago Up 2 hours 192.168.1.###:####->8080/tcp handbrake 4253f8009ce3 needo/sabnzbd:latest "/sbin/my_init" 9 months ago Up About an hour 192.168.1.###:####->8080/tcp sabnzbd 53d2a5a61879 needo/sickbeard:latest "/sbin/my_init" 12 months ago Up 6 hours 192.168.1.###:####->8081/tcp SickBeard 41b1419bc93a hurricane/ubooquity:latest "/start.sh" 12 months ago Up 6 hours 192.168.1.###:####->8085/tcp Ubooquity 50bdc3d944e6 needo/couchpotato:latest "/sbin/my_init" 12 months ago Up 6 hours 192.168.1.###:####->5050/tcp CouchPotato root@Tower:~# ps -Af | grep sabnzbd root 22402 22397 0 13:43 ? 00:00:00 runsv sabnzbd nobody 22404 22402 37 13:43 ? 00:29:42 /usr/bin/python -OO /usr/bin/sabnzbdplus --config-file /config --server 0.0.0.0:8080 root 30779 1975 0 15:02 pts/0 00:00:00 grep sabnzbd root@Tower:~# ls /usr/bin/sab* /bin/ls: cannot access /usr/bin/sab*: No such file or directory

I was looking for low priced 4TB and found this on Amazon: http://www.amazon.com/Seagate-Portable-External-Storage-STDR4000100/dp/B00ZTRXFBA/ref=sr_1_1?s=pc&ie=UTF8&qid=1457807387&sr=1-1&keywords=4+tb+seagate#Ask It appears that it is a 2.5" drive inside a USB3 case without power supply. It surprises me that there is a 4 TB drive in a 2.5 inch format, and I wondered if this is an option for the Unraid server, maybe for archive data. I do have three unused 2.5" bays...

Thanks very much, I renamed the mover.cron for the time being. D Unless you also update_cron renaming it will have no effect since it has already been put in cron. And it will get recreated on boot. Thanks, yes I did update, and will just live with the recreate on boot.

Thanks very much, I renamed the mover.cron for the time being. D

Stopping the Mover can be important when the mover is associated with a serious bad consequence, such as in this thread: http://lime-technology.com/forum/index.php?topic=39510 I am suffering from that issue, that brings my machine down every week or so, and by reports of others, it is related to Mover overlapping with a process in some Docker containers. I'd like to disable Mover and have it run manually until this gets resolved. The UI seems to allow us to specify exactly when the mover should run automatically, but not *if* it should run automatically. "Why should we need to?" Because sometimes we need to. Sorry. Grumpy over my fifth hard reboot in a month. Dennis