Hoopster

Expected behavior because a delay set on a docker container does not apply to starting that container. It is a delay that will be applied after the container starts to delay the start of the next container. So, yes, it is more useful on boot when multiple containers are loading. Probably on a stop and start of the Docker service as well.

Updated two servers to 6.11.0 without incident. One from 6.11.0-rc5 and another from 6.10.3. I was aware the Nerd Pack was deprecated for 6.11.0 and placed the necessary packages in /boot/extra before upgrading and rebooting. I am not sure that everyone is aware the Nerd Pack has been deprecated and how to load the necessary packages. It might be wise to include this in the release notes (as if everyone reads those 😀).

I am not sure how this may be impacted by the Docker Folder plugin as I do not use it, but, in the Docker tab Advanced view, you can set a delay AFTER a docker container starts. The wait value will delay the next docker container start by that amount. I believe it is in seconds.

Just an FYI in case you notice docker image utilization rising. The last two unifi-controller updates I have done left behind orphan images. These are not visible unless you go into the Advanced View on the Docker page in the unRAID WebUI. Deleting these two orphan images reduced my docker image utilization by 7%. Not every update will necessarily result in orphan images but in my case it did. It is worth checking.

Until June of this year, I was sill running controller version 5.14.23 via this docker container. I don't think the container cares much about which version of the controller is used. Some configuration or other issue must be preventing the webUI from loading on 6.5.53.

I basically did what the post I linked suggested. I applied duct tape where indicated, drilled some holes in the plastic insert in one of the drive bays, and added a 120mm fan to the bottom of the case. My biggest problem was identifying and replacing a noisy fan. I would not say the cooling was horrible before the mods but it is much better after them. My drive temps fluctuate between low 30s (two are active and at 31C right now) with little activity to low to mid 40s in a parity check. My server sits inside a cabinet with a ventilated door and one side ventilated. It can get a little warm in the cabinet so I also have a small desktop fan inside the cabinet to evacuate warm air coming out of the server. It is important to note with this case that leaving a side panel off does not decrease temps. The fans on the drive bays push air through the drives and then that air flows back over the motherboard and CPU. With the right side panel off, your MB and CPU temps will climb a bit. Yes, this is a tower case but I like that it is a relatively short tower compared to many other tower options.

That is fine for the flash drive, but RAM in the server needs to be at least 4GB (8GB if you have a lot of docker containers, even more for VMs) and you only have 2GB.

unRAID got its start as a simple NAS and will always be a NAS at its core. Yes, now its capabilities are greatly expanded with support for Docker and as a VM host. Your unRAID system can be as simple or as complex as you need it to be. Many unRAID users are still using it as just a NAS for serving up files to external clients. The bottom line is that you do not have be a genius to use unRAID. Many unRAID user had no Linux experience at all when they started. unRAID is not a full Linux distribution and very little command line expertise is needed as most of what you need to do is in the GUI either natively or via plugins.

Just a suggestion. Unless there is a reason you want a full size ATX power supply, I suggest you go with an SFX power supply such as the Corsair SF600. 600 Watts is more than enough for what you have specified and even if you fill the case with the maximum 6 HDDs. In fact, you may even want to consider the 450 Watt version which is what I have in my current backup server which has 5 8TB HDDs and NVMe M.2 SSD. (see my sig for all the details) The Node 304 case will accommodate a full size PSU but it is a tight fit. I had a backup build in this same case and found the SFX power supplies much easier to work with in the Node 304.

In unRAID you can choose whether or not to export shares and make them public, secure or private. I have all the media shares publicly exported and they show up in Windows as network shares. For my wife, I map specific drive letters to shares she needs.

Changing modes requires different firmware which means cross-flashing to the required firmware which is something other the what is on the chip/card. This information from the unRAID Wiki might be helpful and has a link to the larger discussion in the forums.

There are several threads in these forums and on the Internet about cross-flashing LSI chipset based cards to IT mode. I bought a SAS2008 card on eBay and followed the instructions to successfully flash it to IT mode. It may seem daunting but it can be done by following the documented steps. I did not watch that whole video so I can't comment on the technical expertise required to do what it shows. I linked it only because it was showing how to cross-flash an onboard LSI 2308 controller since that is what you have.

Just did the same. Upgraded from 7.1.66 with no issues.

Perhaps something in this video will be helpful.

I have had no issues at all with the backplane and I have had the case almost 4 years. As to cooling, yes, it can be improved and there is actually a thread in these forums addressing that specifically with this case. Some fairly easy mods wil take care of that. The smaller version of this case (the DS380) had much greater cooling issues. The sides pop off easily (rear thumbscrews) and the motherboard is easy to access. There is a limit to GPU length that some do not like. For me, that was no issue as I always go with a CPU with iGPU and do not have a need for discrete GPU. I hope you find something that meets your needs perfectly. For me, that was the CS380.

I really like the Silverstone CS380 case 8 front-accessible hot-swap bays and I put a 4 x2.5" SSD adapter in one of the 5.25" bays and a Blu-Ray drive in the other for ripping with MakeMKV. I got mine for $130 a few years ago but it looks like they are a little over $200 these days.

Not true. I have my Plex server with a static IP address on a docker container VLAN (br0.3 not host or bridge) which is a completely different subnet than the host unRAID server. Remote via Internet and all other access works great. How pfsense may impact that I do not know as I do not use pfsense.

Have you set up remote access in your Plex Server and are you forwarding the appropriate port in your router?

Since unRAID stores a single file, regardless of size, on only one disk (no data striping across disks) read speed is limited by the speed of the disk on which the file is stored. There is no way to speed this up.

I am not saying this is not a good PSU but I ordered an EVGA 500BQ for a light-use desktop PC and 4 weeks later it was completely dead and would not power on. Paper clip test verified it. A few other reviews mention the same problem. The inexpensive EVGA BQ models are on my "avoid" list now. Fortunately, the Amazon return/refund process was quick and painless. I ordered a Thermaltake replacement which continues to work well. I have Corsair SFX Gold PSUs in both my unRAID servers.

Anything in /boot/extra gets installed on a reboot. Running the intallpkg <packagename> is done only to avoid an initial reboot after downloading.

The K just means the processor is unlocked for overclocking. It's not that unRAID does not support overclocking but it certainly is not recommended for a server as overclocked CPUs can cause server stability issues. The K processors seem to be in greater supply and work fine for unRAID servers without the overclocking. Are you referring to some other K processor feature?

Depends on the version of unRAID. For 6.8.X and prior releases - Go file modifications For 6.9.X - the touch method was recommended for 6.10.X + - the drivers are automatically loaded if the appropriate hardware is detected. From the 6.10.0 Release Notes: Linux Kernel Upgraded to Linux 5.15.x LTS kernel which includes so-called Sequoia and Dirty Pipe vulnerability mitigations. In-tree GPU drivers are now loaded by default if corresponding hardware is detected: amdgpu ast i915 radeon These drivers are required mostly for motherboard on-board graphics used in GUI boot mode. Loading of a driver can be prohibited by creating the appropriate file named after the driver: echo "blacklist i915" > /boot/config/modprobe.d/i915.conf Alternately, the device can be isolated from Linux entirely via the System Devices page. Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enable loading a driver you need to create an empty "conf" file. After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is. This change was made to greatly improve the Desktop GUI experience for new users. I am running 6.10.3 on my main server and hardware transcoding in Plex is working great. I have the go file modifications commented out but the "touched" i915.conf from 6.9.x is still present.

Prepare another USB flash drive with unRAID (hopefully you have a backup of the lost flash drive) and follow the instructions linked below to transfer the license to the new flash drive: https://wiki.unraid.net/Manual/Changing_The_Flash_Device

Power outages have been known to occasionally cause corruption on the unRAID USB flash drive. You can try running checkdisk on the flash drive from a Windows computer. If you have a recent full backup of the flash drive (always recommended), you can reformat the USB flash drive and restore the backup. In a worst-case scenario (physically-damaged USB flash drive), you can restore a backup to a new flash drive and transfer the license/registration to the new flash drive. If you have no flash drive backup, copy everything you can from the current flash drive (corrupted files will likely not be copied) and restore them to either the same or another flash drive.