Arragon
-
Posts
60 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Arragon
-
Now it's stuck again on this screen -.-
-
The SSD was not the cache. It assigned it to the VM. Dunno why the VMs gone but it should be easy to recreate it unless you know a better way to restore the settings.
-
After restarting another time, things look a lot better. I was able to start the array and everything seems okay except there are blue text boxes everywhere and my VMs are gone. Could attached the diagnostics file this time kellerbak-diagnostics-20220518-1128.zip
-
It just opens a window where a lot of text scrolls by and then it reads like this
-
So no problems while running Docker on ZFS anymore?
-
I switched my backup server to 6.10 which seemed to have worked okay until I started the upgrade of the certificate. Now my whole array and all drives are missing.
-
Does that mean it is save now to go to 6.10? I remember people having problems especially with Docker on ZFS (Dataset, apparently ZVOL seemed OK). Can anyone confirm?
-
Getting Error 5 when creating a new USB drive with the Unraid utility. Drive is a 16GB Sandisk Extreme
-
Lidarr doesn't seem to cache DNS queries at all, hitting my DNS server with over 1000 requests per minute and getting blocked. How can I prevent this?
-
I believe the AMD Ryzen 5 3600 has no integrated GPU and the board only has on PCIe x16 Slot (and 2 x1 Slots)
-
Would it be okay to have only one GPU for VM Passthrough and Transcoding if both aren't running at the same time? I only need the VM once in a while and would stop Plex before I use it.
-
Maybe this can help: https://wintelguy.com/zfs-calc.pl
-
Since the user asked for a server with SSDs, I did assume he wouldn't put some spinning rust for that obligatory array drive. And with a single drive, there is not parity
-
Of course Limetech would not account for ZFS since it is not officially supported. But since I was not sure about docker picking the right storage driver and my previous attempt with unstable builds (2.0.3 iirc) was unsuccessful, I recommended setting the docker vDisk location to path on the array which 100% does work.
-
it says zfs would have zfs storage driver instead of the btrfs or overlay2 one
-
Limetech does not yet recommend this (https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0#Docker) I think it would be best if we could get it to work with the ZFS storage driver (https://docs.docker.com/storage/storagedriver/zfs-driver/) once ZFS is officially in Unraid. @ich777what does docker info give you for your setup? Did it autoselect zfs as storage driver?
-
You should have a single drive for Unraid's array, so the system can start since most services need the array started. Also your docker.img should be placed on this drive as was witten earlier. I have atime off in general and setting autotrim on for SSDs is something I just do like setting ashift manually on creation. For the compression I would go with zstd instead of lz4 however.
-
Does the user/group have write access? The default when creating a dataset is root:root
-
Doesn't need the array to be started for serivces like SMB and Docker to run?
-
Can't find "Plugin Update Helper" in the apps tab. Is it not available in 6.9.2? Is it sufficient to change the location or do I have to move the docker.img file first?
-
This feature could make ZFS way more interesting for Unraid in the future: https://github.com/openzfs/zfs/pull/12225
-
All of a sudden my flash drive was not writeable any longer. Searching for that error revealed that this most likely because of bad sectors and Sandisk making their drives readonly in that case. So I want to switch to a new drive but of course I don't have a flash backup. Now I wonder if I can just copy the files in Windows to the new one or if I need additional steps.
-
Does Remote Access require you to have have Port 443 accessible via IPv4? I can't get it to work with IPv6 even thought that can be reached from the internet.
-
I can confirm that since I still had issues with 6.9.0/2.0.3 and my raidz1 didn't change.
-
I think we can omit createtxg as it's described as "The birthtime transaction group (TXG) of the object."
