PeteAsking

Yes when you restore it make sure you have changed the tag to be the same version you are coming from, that is normal.

Unsure but you can try the other docker container (the reborn one) and see if thats easier for your use case and setup.

8.0.28 has failed testing and will not be promoted to an unraid tag and will be skipped.

Sure, however you have no way of knowing if media files are the majority of files stored by all unraid users, that is a major assumption on your part. For many, it helps, myself included. I saved 80GB on the last run for instance, that is over a 2 month period. For myself, that is something I cant really just give up as I use my NAS every day and would fill it up at a faster rate if I did not.

Ok interesting. I was unaware it had changed. In terms of defrag, if not using snapshots it is pretty useful as the amount of space reclaimed is significant when compressing files. This is normally many gigabytes. if you do use snapshots, I agree it would increase the space (have the opposite effect) as it would break deduplication. So it would depend on your use case.

On unraid nocow is the default so its not a problem. If you override that and use cow and snapshots then I agree its not appropriate. However this is not the default setup for unraid. I think the only issue is if you use snapshots and not cow. (The issue is just that more space will be used as the filesystem sees each snapshot as a different copy of a file each taking up space as opposed to sharing space).

For BTRFS volumes I see people having issues with BTRFS. This is because I think people dont know to do a balance/scrub periodically and a defragment. For example I have a userscript that runs on the 1st day of every 2nd month (6 times a year basically): #!/bin/bash date > /mnt/btrfsprotect/domains/Defrag.log btrfs fi show /mnt/btrfsprotect >> /mnt/btrfsprotect/domains/Defrag.log btrfs filesystem usage /mnt/btrfsprotect/ >> /mnt/btrfsprotect/domains/Defrag.log echo ----start---- >> /mnt/btrfsprotect/domains/Defrag.log btrfs filesystem defragment -r -v -clzo /mnt/btrfsprotect/ >> /mnt/btrfsprotect/domains/Defrag.log echo ----end---- >> /mnt/btrfsprotect/domains/Defrag.log btrfs fi show /mnt/btrfsprotect >> /mnt/btrfsprotect/domains/Defrag.log btrfs filesystem usage /mnt/btrfsprotect/ >> /mnt/btrfsprotect/domains/Defrag.log date >> /mnt/btrfsprotect/domains/Defrag.log The relevant line is this: btrfs filesystem defragment -r -v -clzo /mnt/btrfsprotect/ and the other lines setup logging I can review. It also has the output of "Free (estimated): " which is more useful in determining free space available. This allows me to defrag the volume and compress archived files and so on, and for the scrub and balance I run on a schedule Every Sunday a balance on the array which is quick as it never finds unbalanced files (so far) at 3AM and every Monday a Scrub at 3AM (Duration: 0:26:05) which checks for errors. Doing this I have never had an issue with BTRFS. I use Raid1 with 3 disks and if a disk failed, then it would at least rebalance on the next run to the remaining disks (and I would quickly realize a problem of low disk space when this happened). Just some tips I have found worked well for me for as long as btrfs has been available on unraid (I converted to it the moment it was available a few versions back). Hope this helps you.

Ubiquity releases a new update once a month on average. You can come back periodically to this thread and check what tag is safe to upgrade to. Its not automatic and you will have to check it every so often. If desired, simply use one of the less updated tags and come back twice a year if you prefer. No clue about changing the icon. Sounds unimportant and not an issue.

If you need any help just let me know. It can basically do anything you can want.

Not sure but that error means the OS told it to stop for some reason. Could be anything that causes it from a backup to low resources or so on.

Are you running out of resources or something? How much ram is in use typically that sort of thing.

Dont forget to check the inform host override is set correctly on the controller.

No problem. If you always take a backup before changes you should be fine no matter what.

The expand on this there is a testing process that we undertake on the new container prior to deployment and after before announcing it here on the forum so it has at leased passed a basic quality control check.

No this tag will not/does not exist and there are no plans to include it.

Yes this is correct.

New controller tag has been released and is tested for home use: 11notes/unifi:8.0.26-unraid

Not sure. Could you restart the docker or not? Check you had disk space available.

Im not sure but giving the unraid docker the same ip as the old ubuntu server if you turn it off might help adoption of you did a restore.

No you dint need to install a mongodb container. It is included. I think you type sudo service unifi stop sudo systemctl disable unifi

Probably will be fine.

Try to do a backup from the ubuntu box, and turn off the ubuntu box and restore the config to the docker instead of the process you are undertaking.

I think those specs are a little conservative but would be pretty easy to test. I have one of the amazon i5 qotom boxes and the cpu is never taxed at all.

If you dont agree opnsense with zenarmor on the free license is absolutely hands down the best thing you ever used I will eat my hat (words) because I have never used anything better. There is also a way to have a similar pfblocker experience if you google. Its well documented now.

100% another docker is using the port. Just stop all of them and start only this one and then start the others one at a time until you find it.