NLS

Was planning to ask the same thing! I guess if you add a path in container configuration, it will be able to be seen by the server.

Very weird. When I first installed this, before reading this thread, I just changed the port (because it was occupied), started the container and it started fine, presenting me the login screen. I logged in (found the pass), then after the step that I needed to configure the server and clicked to proceed, it crashed (404!)... I went to initial page again, logged in again and now I was in dashboard, but with 0 servers defined (as my configure server step seemingly crashed). So before adding a server, I went through the other settings. I changed Admin password, made another admin etc. Also changed the port WITHIN the dashboard configuration, as it showed the original port 8000 (so is there a bug there?), to match the port I had in the container configuration (is this correct?). In any case, I tried adding a server once more. After I tried, since I had not read your instructions, I just left most settings default. - I used a server name with spaces ("Something Blah Blah"). Is this bad? - I left default path, which I cannot remember but was NOT what you show in the pic above. - I left default jar, which I think was paperclip.jar. NOTE, I haven't manually downloaded ANY server jar, as I expected this to do it automatically or something. It defaults to "paperclip.jar". - It failed again, this time with "Invalid Settings Detected: Server Path Does Not Exists". - I tried to restart the container. Well... that was the last time I saw it. ...container starts but web GUI doesn't work ever. - I removed the whole container and re-added it (again only changed port), only to find that AGAIN GUI didn't work at all! BEFORE me doing anything (but container runs). - This time the log doesn't show any login info. ...so what to do next? Remove again and do some appdata clean up first? Also (provided I get a GUI again), can you elaborate on step #3? OK EDIT: Cleaning up appdata helped. I did the steps as you listed them. This time the create server step went forward. Server started. Now to see how to actually use it (especially looking for the "launcher" part...).

Yes. No response (yet).

Yes. Doesn't detect any PWM. My motherboard is a pretty standard chipset Gigabyte Z87-HD3. I expected it would be an easy job.

Fan Control doesn't seem to detect anything on my machine. No PWM controller detected. It is a Gigabyte Z87-HD3.

I am saying it is urgent because I would like to see the status of my server that is remote and it is a bit dangerous to leave on if there is an issue. My wife hears what by the description seems like a fan "wrestling" to work and a BIOS alarm probably about this very thing. So, is there a way to monitor the fans of the system (obviously the ones that the system IS aware off, like CPU fan)?

Because it is the best.

So can someone spell out the instructions? Do I need the trailing slash? EDIT: Well I found how... I don't remember the choice "directory" before... Is it a 6.9.1 thing?

I don't remember, I suspect no. (because IIRC I followed the rough instructions I googled) Stupid thing is that I deleted the docker file, although I should probably have just renamed it - I was too sure it would work.

I already did something like that and it didn't work. When I pointed to a folder instead of the img file, it just turned red (that it doesn't exist).

Subject says it all.

For me it worked without moving anything. Maybe a newer update also performed the move OR works from both locations. My problem is different. I cannot update any more. I wonder if my repository is wrong? (linuxserver/qbittorrent)

I think you are not aware of the issue we were discussing in the previous pages.

Nobody???

1) So to let the system update to latest image, I need to manually move some files? Right? What is the original repository? 2) Correct UMASK is 011? Why not 000? I thought this is the mask other unRAID file transactions use.

OK I reverted too. Also added UMASK_SET variable and hope it fixes the wrong security attributes of new torrents. Let's hope it updates properly next time.

Well I'll wait at least for today to see some kind of "official" reaction first. Reverting to previous version also returned your torrents?

Same here - torrents disappeared. Haven't tried to re-add them (one by one over 100 seeds)... Can someone give a step by step process to go back to previous version? Will that return the torrents listed?

Sorry if it has been asked before, but anything downloaded by this docker, has the wrong security attributes (and then I need to change them manually). It is read only for group and others. Any ideas?

Yes sorry... this is not an install since then, is a fresh one (less than a year) data xfs cache btrfs

I think you are missing the point. My problem is not if folder browsing is slow. It is yes, ok, but not a major problem. Again a "demo" of the problem: Editing a pack of let say 400 x 100kb files within a 400 files folder = 150 seconds. Editing a pack of same 400 x 100kb files within a 100000 files folder = 2 hours. (numbers are not real, but they are close to scale) This is the problem. I am using latest non-beta release for unRAID and using the default fs it installs on data disks. Client is Windows 10 x64 with all patches.

I have a seemingly huge issue with my unRAID. Seems the larger the folder in number of files, the slower the file access inside it. And I mean disproportionally. I don't mean that double the files the double the file access. And I am not just referring to listing the contents. I am talking about actual file access, edits etc. A tiny file with a small change that in a small unRAID folder takes non-measurable time after saving, may take... 1 minute (!!!) for the same tiny file if it resides in a huge folder (containing let say 100k files). I have read about case sensitivity and SAMBA issues with it, but I cannot experiment with it (yet) as I need to take down the array (else smbd cannot restart). But I DID try mounting a share using NFS, both case sensitive and non case sensitive... Supposedly NFS doesn't have such issues. Results? Even worse! Actually listing the folder of 100k files in windows explorer didn't even give me any contents after 5 minutes (then I dismounted the share). Both with case sensitive and non. I tried listing the folder in command line (where "dir" is more... erm... direct) and indeed started listing files but after around "c" letter it started having hiccups! With SAMBA at least, listing the folder (in windows) does work, but takes almost 2 minutes. There is definitely an issue. But large folders is common for me (as I handle large emulation collections) and this is major. For example I started a batch edit of simple text files in 7200 folders... normally it should take less than a second per file (a single file per folder). It took more than 2 hours for the first 400 files in folders!!! (so will take almost 2 days for a simple task!) Note that "normal" share access (of smaller folders, file copies etc.) is "ok-ish", not fantastic (40-50MB/s?) but given my unRAID setup it is ok. Any ideas???

Any chance for update on VNC Web Browser? Chromium crashes all the time and Firefox keeps popping I need a security update of the browser (that I cannot install). EDIT: Just noticed about EOL. So new question, any news about new container?

Here is what I did in the end. First I set the commands to check for invalid dates. find /mnt/user -type f -mtime 8500 -ls ## Consider before early 1997 that the dates are invalid and usually they are. ## ## Note that Windows and Linux showed some of them DIFFERENTLY ## ## meaning "edge" dates behave differently between the two OS! ## find /mnt/user -type f -newermt today -ls ## I didn't find parameter "today" mentioned anywhere but suspected it works and from my checks, it does. ## Interesting trivia with -mtime 8500 (which is January 29 1997 if run today), is that few files (with obviously invalid dates) showed up at January 29, 28 and 27 of 1997, but no file before that date! Any ideas what OS intricacy does that? When I rerun the tests (after touching), with -mtime 8000 (1.5 years newer datestamp) no files showed up... Anyway, when the above two checks list at least one file, I run the corresponding commands below: find /mnt/user -type f -mtime 8500 -ls -exec touch {} -t 2001010123 \; find /mnt/user -type f -newermt today -ls -exec touch {} -t 2001010123 \; I then run the "check only" versions again to verify that the files where indeed touched (so, not listed) and it worked. Also checking from my Windows machine indeed touched files showed as modified in the specific date/tame I use as placeholder (easy to find them later as I don't think I indeed modified any files at 01:23 of January 1st 2020). I actually did the above on a per disk basis (so not /mnt/user) but now I trust it enough to use it on the full array (except if I know where the problem lies exactly) and also not run the simple (no touch) version in the future. NOTE that now I am looking into merging the two find (for future and distant past timestamps) into a single one as I believe there are logic operands in find command. Any help appreciated. EDIT: Found error. -mtime 8500 checkes for exactly 8500 days back. I need to put +8500.