TexasUnraid

Yes, I deleted the entire appdata folder (well technically renamed) and then reinstalled.

Yep, I tried that but nothing changes regardless of the scaling setting. The black part seems to be part of the active "desktop" but firefox is simply not maximized to fill it for some reason. Yes, restarted and reinstalled it a few times now. The mouse turns to an X anytime I try to adjust any settings that might allow me to maximize it.

I have been using the firefox container for some time and it has worked great. Today firefox crashed so I restarted the container and now firefox will not maximize for some reason and I can't figure out why. I even resorted to completely wiping the whole container and reinstalling it (including appdata) yet the same issue persists. Nothing has changed on the server or my PC in this time.

yeah that^. Most people either do not use dockers or if they do do not keep track of the writes to the SSD's until they have an issue.

Still wish this could be turned into a plugin, would make things so much simpler and is a prime candidate IMHO.

While I agree with the rest (although had mixed results with adding more ram, I now have 256gb of ram and had to limit wrtitecache to ~2gb or it would have lockups). I did extensive testing with encryption and btrfs / XFS and noticed no difference with either of these on SMB performance at all. While they can technically slow down the drive speed SMB with small files is limited by the SMB bottleneck, not the drive speed. Even on windows with small files getting more then a few MB/s of writes was good, 10mb/s was really good. You are well below drive bottlenecks at those speeds.* You would have to have a REALLY slow CPU for either of these to make a noticeable difference in my testing. Even locking my CPU to 1200mhz didn't noticeably slow down speed tests to the drives when I was testing raw drive speed. I was only using an I5 2500 at the time as well. *obviously there are edge cases that could not be the case but practically with hardware from the last half decade, it is highly unlikely

Unraid fixed their side of the issue, the rest of the issue seems to be a linux/windows issue. I have found that a faster CPU on the unraid machine helps some. Also use direct disk share access and not the user share, this also improves things. It is still much slower then when I was using windows but the other features of unraid make the switch well worth it. Docker alone is worth the hassle in my case, I have like 20+ of them running and they are just so nice. BTRFS file system is also Super nice to have. Already caught a few corrupted files here and there that windows would not of (or other linux file systems outside of ZFS). If you are just setting things up, highly recomend using BTRFS for the file system on all drives, easy to do now, hard later. Also recommend disk encryption, just good peace of mind. If you ever have to RMA a drive, you don't have to worry about wiping it first.

What bug is this? I just had to rebuild all my dockers and my qbittorrent lost all of it's settings, it is like it is not even reading the conf file since all the settings are correct in it. Also if I update the settings, the .conf file is not updated yet the settings seem to stick? Is it using a new conf file that is not mapped to appdata now? Edit: Can confirm that the .conf seems to be the issue, reverted to that version and all my settings showed back up and it is using the correct conf again. Seems the new version is using a differnt conf location or something.

I would also like to see this option added. Been trying to figure out how to do it manually but have yet to find any good writeups. Can't tell if I manually mount a drive with compression if it will "stick" after a reboot, doesn't seem like it.

Great, that got it working!

No worries, was just not sure if I missed it.

I was not sure if you had time to look at this yet? No big deal, didn't see an update so far. No worries if you have not had time. To refresh your memory:

Yeah no worries, sounded like you had it sorted so was not sure if it was an issue with it being pushed or just had not done it yet.

Cool, band-aids are perfectly acceptable. lol. I tried updating the docker but it did not pull anything, guess you have not pushed the update yet?

the makmkv docker is complaining that it is too old and must be updated to be used?

No, just a standard bridge network setup. It seems to be something about how it interacts with the drives since it always complains about sync issues when it does crash.

No worries, luckily I was getting a head start on this project so I have some time to spare. Thanks!

Trying to setup your Debian-APT-Mirror docker but having an odd issue. ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Adding user: debian to www-data--- The user `debian' is already a member of `www-data'. ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting cron--- ---Starting apache2--- ---Starting...--- ---Something went horribly wrong, can't find the mirror directory!--- I have checked things over and over, I have the folder mapped to valid paths, if I manually create files in these folders, either inside the docker or on the server side, it is visible and editable from both ends. I also manually created the mirror dir under the data folder but didn't help. It is like it is using another folder tree entirely. I manually started apt-mirror and it ran but started filling up my docker image but I could not figure out where the files were going. It is using all default settings in the mirror.list file for now. The download itself seemed to be working fine.

lol, I actually did not try the webui, sure enough it is working! thanks!

Ok, did a force update and that solved the firefox install issue but now getting a new error: ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Starting...--- ---Version Check--- ---Firefox not installed, installing--- ---Sucessfully downloaded Firefox--- ---Preparing Server--- ---Resolution check--- ---Checking for old logfiles--- ---Checking for old display lock files--- ---Starting TurboVNC server--- ---Preparing Server--- ---Resolution check--- ---Checking for old logfiles--- ---Checking for old display lock files--- ---Starting TurboVNC server--- ---Starting Fluxbox--- ---Starting noVNC server--- WebSocket server settings: - Listen on :8080 - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) WebSocket server settings: - Listen on :8080 - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) ---Starting Firefox--- [GFX1-]: glxtest: libpci missing (firefox:123): GLib-GIO-WARNING **: 07:58:18.494: Failed to execute child process “update-desktop-database” (No such file or directory)

Should be all default settings besides the port.

Been using the firefox container for some time, updated it and now I am getting an odd issue where it can't install firefox? ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Starting...--- ---Version Check--- ---Firefox not installed, installing--- ---Something went wrong, can't download Firefox, putting container in sleep mode--- How do I figure out what went wrong or install firefox manually?

Ok, I am seriously confused at this point. Server has been running great since I stopped using tartube. I have been using tubesync and just playing with it so far, downloaded 2 channels over the last few weeks and no crashes. Then a few hours ago I added 6 more channels to download and the server crashed AGAIN now! How in the heck is this possible? How can downloading youtube videos cause the whole system to freak out with a kernel panic no matter how it is done? Docker, VM, it doesn't matter. It always seems to get some kind of sync error kernel panic. The actual share setup is really basic, I have a share dedicated to youtube videos and set to only use 1 disk on the array and not to use cache. Basically as simple as it gets. I even have the docker mapped directly to the disk so it doesn't use the user share. If only SMB performance was not so abysmally bad with unraid/linux I could use another system or a windows VM to isolate the issues hopefully.

Not sure I understand your question, that quoted post does not matter what brand SSD you use. If you are referring to the script I posted to log SSD writes, I do not own any intel SSD's personally so I don't know what the multiplier is. One of the existing multipliers might work, if not then you will need to either do some research or testing to figure it out (get a file of a known size, copy to drive, see what writes increased in the smart log and do math to figure out the multiplier, generally takes a few different sized files in the 1-10gb range to narrow in on it).

The plot thickens. I spun up an ubuntu VM and installed tartube, Started a sync and a half hour later, the server locked up just like before. It was using the virtio share from unraid to access the files as SMB does not seem to work well. I have no idea how it is possible for it to cause these crashes inside both a VM and docker? Guess it is time to try tubesync. Does anyone know if it has the Ability to use a proxy/vpn so that my main IP does not get throttled? Edit: Installed tubesync, really liking it so far, doing some test downloads now. Just need to figure out the VPN/proxy issue as it tends to get throttled when checking as many channels as I have and it is really annoying if it is your main IP.