DiscDuck

You can try to default the bios and enable the functions you need step by step (like vt-d). 6.9.2 does not like "too fast" for some reason. At least that is what I have found. Previous version never shown that. Good luck.

Hi honestly, having more than one cache pool drive is not a 1 in a million exotic server case but very common place since the release of unraid 6.9.x many moons ago. If you find the time to look into this, simply add another cache pool drive (doesn't even need to be an ssd) to your server and you have all the information you could possibly need. If you don't have the time or the drive to bring unbalance up-to-date, that is of course totally up to you. You will still get my appreciation for the great tool that has helped me moving many many bytes.

Hi did the week or two allow you to look into the missing pool drives? With 6.10 release around the corner it would be nice if unbalance would support 6.9.x. Again, if we can help pinging Limetech, looking for api's and such, let us know. Thanks

Hi Just wondering if you had any luck. It seems more and more users enjoy the multiple cache pools function. If we can help pinging Limetech, looking for api's and such, let us know. Thanks

Actually there are two solutions I manged to get going. One very complicated with an external vserver and costs attached. The other using a free cloudflare tunnel. Works great! There is even a video about it: There is a lively support group on the associated discord server.

I would love to find out, how the choices for the gui icons came about? What made you choose a paw for boot devices? A snow flake for array operations? More about this and the early decisions.

Thanks for the update. Will there be a version that supports more than one cache pool drive? Mine still seem to only show one.

Thanks for the quick response. I guess I'm used to companies that charge money (and even ones that don't) for their products, would have at least given an acknowledgment after several days. Let's see when a response and a fix is published.

@Squid is this something you could help with?

This is still happening. Any new development?

My docker update also fails with ghcr images.

Just had a movie not wanting to play on an iPad. Error not enough space to convert. Upped the ramsdisk from 4 to 6 GB and everything worked fine. Maybe this will help the next person running into this.

The problem is not, that the phrase is wrong or not applied. It fails randomly on drives, every time the array starts. Without touching the kexfile. Only happens with 6.9.0.

Normally pulled of an ftp server so that the array can start automatically. But took that out here for testing. Makes no difference to do it via the GUI.

After testing 6.9.0 on two other unraid servers for a couple of days, without any problems, I updated the next unraid server, my storage server from 6.9.0-rc2 to 6.9.0. Now I see drives with a red lock icon, claiming "WRONG ENCRYPTION KEY". But every time I try to start the array, it is a different set of drives. Even managed to get the array started with all drives unlocked once. The two other unraid servers also have their drives encrypted, the same way, the same key. No problems there. Example array start:

The screenshot has the destination down as /transcoding, is that a typo in the text with ?

Managed to get ports tunneled from the outside to my servers/dockers. Using SSH remote port forwarding. Now in the process of automating everything and getting reverse proxy setup again including certificates. If there is interest from others, I would be happy to write up a little howto once everything is up and running.

For preparation, I rented an external virtual server with a public IP address. Locally I configured a VM with pfSense. pfSense is up and working, standard NAT and test clients can access the Internet. How to proceed from here? Looking for help, tutorials, documentation here. Can pfSense connect to the external Server with SSH and could I forward all ports from external to the WAN interface of pfSense?

@bilinz I'm using: #!/bin/bash mkdir /tmp/PlexRamScratch chmod -R 777 /tmp/PlexRamScratch mount -t tmpfs -o size=4g tmpfs /tmp/PlexRamScratch

@AinzOolGown & @cesman Did you try piping the passphrase via textfile?

@itimpi Certainly, a good idea. Also looked at https://www.zerotier.com/ (there is a docker template for UNRAID). Hope to find UNRAID Community members with tested solutions in place. With ipv6, ISPs blocking 443 and more, surely there is some demand.

Looking for the best way, using a fixed ip address of an external located Server, to access services on an UNRAID Server. The UNRAID Server in question is unfortunately behind a double NAT without any way forwarding ports.

Managed to get access to the lost data. Hope this little workflow helps the next person this might be happening to. So, after a system lockup and a hard rest, one of my data drives in the array showed up without any partition or data. The drive was part of an array with xfs-encrypted drives. There was no parity drive. (No risk for me, as I have plenty backups) Use the following method at your own risk. Always have backups, there is no substitute. The drive in question needs to be outside the array or the array needs to be stopped. My drive was outside the array and only visible in the GUI with the great plugin Unassigned Devices. At the end of the identification (Table Unassigned Devices, Main page), you find the device name sdx (where x typically is a, b, c, etc.). Let us say it is sdg. Open the terminal. First, we need to find the LUKS header. hexdump -C /dev/sdg | grep "4c 55 4b 53 ba be" If you get a result use CTRL-C to stop the dump. Note the first Hex number, it should look something like “00008000”. Now translate it into decimal. I used https://www.rapidtables.com/convert/number/hex-to-decimal.html 00008000 translates to decimal 32768. Let us find the next free loop filesystem. df -h If you see entries like /dev/loop3 use the next one up, that is not listed. Now we combine the device, the decimal number and the next free loop in the next step. losetup -o 32768 /dev/loop4 /dev/sdg Now we open the device. If we get asked for the secret password, we hit the right spot to access the data. cryptsetup luksOpen /dev/loop4 lukstemp Enter your passphrase. If you get back to the prompt without any message, it worked! Finally, we create a mount point and mount the filesystem. mkdir /mnt/decrypted_drive mount /dev/mapper/lukstemp /mnt/decrypted_drive If all went as planned, we now can access the data under /mnt/decrypted_drive .

Already checked that. Unless I overlocked it (if so, please point me to the correct block), there is no entry for fixing xfs - encrypted. Searching the entire wiki page for encrypted or luks provides no hits. First I need to recover the LUKS entries. Only than can I use xfs_repair.

No paritiy on the old server, therefore no rebuilt. New server setup, different Hardware. First thing I tested was different hardware and controllers. All hardware checked OK. Drive is also OK. I did not loose anything. Still a single drive which I would like to start a non destructive look onto. Since I can't loose anything on the drive, nothing can go wrong.