Hoopster

Are you aware of this known issue with Unraid 6.12.x releases? Since hardware transcoding uses the i915 driver, perhaps this will help. I had to do this on my server with an i5 11600 CPU to stabilize the i915 drivers. In short, 11th gen Intel CPUs have issues with low power settings with recent Linux kernels. This change disables the low power mode on the 11th gen. CPUs. Known issues Crashes related to i915 driver We are aware that some 11th gen Intel Rocket Lake systems are experiencing crashes related to the i915 iGPU. If your Rocket Lake system crashes under Unraid 6.12.0, open a web terminal and type this, then reboot: echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf Setting this option may result in higher power use but it may resolve this issue for these GPUs.

You might find them on eBay. Also, there is an older thread in these forums on card readers that have a unique GUID and work with Unraid. I will link it when I find it but I am headed out the door right now for a few hours.

This is exactly what I do. Two of my three Unraid servers use Kingston Mobilite G2 or G3 (no longer available) card readers for the Unraid flash drive. I use the other slot in the card reader for the syslog. Been using these readers for 10+ years with no issues.

It is normal to have a User and User0 folder. User0 is the same view as User but leaves out the cache/pool drives. User0 is mainly for internal Unraid use. If you provide more details about your issues with Unraid and the diagnostics (might want to start a separate thread for that), some of the experts here may be able to give you some pointers to get you headed in the right direction.

I updated the post a bit to hopefully make it more clear there was a link in it. I can see how that would be missed.

Actually, yes I do, but I will not be home until November 27 to ship it if you are still interested.

The docker.img file is used to store the executable code for each container. Even with 25 containers, 20GB is generally enough, if the containers are properly configured; there may be exceptions if some of the containers are unusually large. At one time I had 20 docker container installed and was using only ~12-13B in docker.img. A couple of those were 1-2GB in size. In the Docker tab you can click on the button to see how much space each container is occupying in docker.img. If some look unusually large, it is likely that data is being stored in the container due to improper configuration

I followed this procedure to send the syslog to a USB flash drive mounted as an unassigned device.

Thanks. Good to know. I was unaware of this restriction with the trial key.

You could have a large external USB drive formatted in NTFS. Copy data there from Windows and then mount the drive in Unraid using the Unassigned Devices plugin which supports NTFS. When mounted in UD, copy to the Unraid array. Lather, rinse and repeat with more data.

Yes, you can run Unraid as a trial for 30 days. The trial is essentially the Pro version. There are no limitations to a trial other than the time. Unraid is not installed as an OS in the traditional sense and there is no difference between Basic, Plus and Pro versions as far as the Unraid files that get installed on the USB flash drive and loaded into RAM when the server boots from the flash drive. The drive limitation comes from the license. You could run a trial for 30 days from a different flash drive and copy the config folder (minus the basic license key) from the current flash drive to retain your current system configuration while running the trial. Then play around all you want with configurations in the trial. If it works out well, just go back to your current licensed USB flash drive and upgrade from basic to pro. You could then also copy the config folder from your trial USB key back to the licensed USB to retain your trial configuration. As mentioned, there is not path directly from a basic license to a pro trial.

I have had the case for 5 years and have never had an issue with the backplane connections. The Molex connectors that supply power to the HDD cages fit tightly. The SATA cables for each drive do stick out a bit as do some capacitors on the back of the cages. Just be careful when working in the case and there are no issues. As far as the hot swap connections for the HDDs inside the HDD cages, they seem solid and secure and I have never had a probem when inserting or removing an HDD in the hot swap bays.

I have this case and don't think this would be easily possible. There is not much room between the top of the 8 HDD hot-swap cages and the existing 5.25" bays. if you cut everything out above the HDDs to the top of the case and made your own bracket for a 3x3.5" it might just fit. Depends on what 3x3.5" (or even 5x3.5") unit you choose. I measure about 5.125" of space between the top of the HHD bays and the top lip of the case.

That means Unraid is booting properly and it is giving you the command line prompt when you log in. Generally, you access the server GUI via a browser on another computer on the local network. Just open a browser and enter the IP address of the Unraid server or http://Tower. IP address should always work. If you do not know the server IP address, type' ifconfig' (no quotes) at the "root@Tower:~#" command line prompt. You will need to login to the GUI with the root user. If you currently have no password for the root user you should set one.

In Shares, Plex is a disk share (name of SSD): In Plex docker container plex appdata is on the mnt/plex disk share View of Plex SSD in Windows: