TallMan206

Hi, I today found I only reach 190MB max from my main Unraid server to my backup server. All is connected to 10G and even link aggregation to 20G. Mainserver: Unraid 7 Dell R720 with H310 IT modus 4x 20TB Toshiba enterprise drives in a zfs pool with 2x 500GB nvme drives as L2ARC. Backupserver: Unraid 7 Supermicro LSI HBA (more powerful than the H310) 4x 4TB vdev raidz1 and 3x8TB+1x16TB vdev 2 raidz1 these 2 vdev make up a zfs pool. Subpool L2ARC exist of 2x500GB Sata SSD Attached my diags unraid-diagnostics-20250201-2146.zip backuppie-diagnostics-20250201-2147.zip

That worked. Removed the script, and added the line to the GO file. Thanks

@ich777 Running 7.0.0 I get an error with these lines in my script. If I use nvidia-smi --persistence-mode=1 I do not get that error. Error with nvidia-persistenced: script location: /tmp/user.scripts/tmpScripts/Gpu idle/script Note that closing this window will abort the execution of this script nvidia-persistenced failed to initialize. Check syslog for more details. USER PID ACCESS COMMAND /dev/nvidia-modeset: root 13191 F.... nvidia-persiste /dev/nvidia0: root 13191 F.... nvidia-persiste /dev/nvidiactl: root 13191 F.... nvidia-persiste No error with this line nvidia-smi --persistence-mode=1: Script location: /tmp/user.scripts/tmpScripts/Gpu idle/script Note that closing this window will abort the execution of this script Persistence mode is already Enabled for GPU 00000000:04:00.0. All done. USER PID ACCESS COMMAND /dev/nvidia-modeset: root 13191 F.... nvidia-persiste /dev/nvidia0: root 13191 F.... nvidia-persiste /dev/nvidiactl: root 13191 F.... nvidia-persiste

Goodday, I recently had an issue that apps could not load, and that docker could not update. I found this was a DNS issue, and now I found out that it looks like it is caused by the Tailscale plugin. The server was running fine now, and I installed Tailscale yesterday again, and now the server was again not able to connect to Github. I uninstalled the Tailscale plugin and immediately Unraid was able to connect again to Github. What could be the reason that Tailscale causes Unraid not to DNS anymore?

Sorry I should have told that pihole and unbound are not running on the server, they are running on a Pi 4. The server is working fine at the moment, I really don't know what happened

Hi, Since 2 days, Unraid cannot find the DNS names anymore, and therefore apps are not able to update. I used to have a fixed IP in Unraid, and also fixed DNS but to try, it's now on automatic. I'm running Unraid 7.0.0 If I stop docker, and change the DNS server, I can reach the apps, and update them (not the dockers, since that is not running). As soon as I start docker again, the DNS cannot be resolved. I try to ping from the CLI, and cannot resolve. My other server, is running fine. Also Unraid 7.0.0. I am running Pihole with UNBOUND and both servers are In the NO blocking. unraid-diagnostics-20250114-2103.zip

Since the last update of LB, I cannot open it on my phone anymore. It does work on the computer. Running Unraid 7 RC2 On my phone I get the error: PC and phone is both Google Chrome

Hi all, Merry Christmas! Can someone explain me what these snapshot admin options are/doing? I cannot find any manual, and I am trying to restore a snapshots to a month ago, but I don't know which option I need to take. Thanks!

It's should be the zfs master plug-in

Hi all, Merry Christmas! Can someone explain me what these snapshot admin options are/doing? I cannot find any manual, and I am trying to restore a snapshots to a month ago, but I don't know which option I need to take. Thanks!

Yes, you are right. That works. Not on user level, but on pool level, resolves the issue

Yeah makes sense! I did switch to reconstruct write. Thanks!

Has this been resolved already? Running Unraid 7 RC1

Hi, I am backing up my mainserver to my backupserver. The backupserver is an array and while writing to the array, it also reads data at the same time from the same disk. The array is BTRFS, and I was expecting the data coming from the mainserver to be written to the array at higher speed, and TBH, I never saw the array disks being read off, when the array was ZFS. The speed was much higher because the data disk and parity disk were both writing at their max speed. How come the array is now reading from a data disk (to the parity disk?) while a steady flow of backupdata comes from my mainserver?

Does the Unraid write method impact zfs write speeds? (Disk settings: tunable: auto, read/modify/write or reconstruct) I also get with my raidz1 zfs pool 150MB/s or something with 4x 20TB Toshiba enterprise drives and 2x500GB NVME L2ARC drives in mirror.

How do I do that? I only see the mover action. I even tried, and it does move the Data share from Pool-One to Pool-Two, which is not what I want. The share needs to fill Pool-One and then continues on Pool-Two.

Ah I see what you mean. Radarr/Sonarr make this dataset all the time on the ssd-pool, but there is actually nothing in there.

No, it's the movies inside of my Movies share. I only have a couple of shares. Like 11 or so. Movies share only exist in main pool. I move the movies I downloaded from 'Downloads' to 'Movies'

Because it is not only Krusader, but also the file manager, I decided to put it in General support.

----SOLVED---- I am not copying/moving on /mnt/user level anymore, but between pools, so ssd-pool > pool or the other way around. That works flawlessly Please all I need your help, I am starting to get desperate now. When I do a fresh install of Krusader, everything works fine. After a couple of times copying and moving files, it just does NOT work anymore. I'm trying to move a movie from my Downloads share on my SSD-pool to my mainpool. This gives the error of insufficient space. Also copying/moving files on the SAME pool does not work anymore. Using UnRAID's file manager, I get the choose a valid path error. Running UnRAID 7 beta 4 with 2 ZFS pools, NO array drives. unraid-diagnostics-20241119-1724.zip

@ich777 Can you help me find the issue of why Krusader is not able to copy files between my shares (ZFS datasets), local and remote? Situation: Mainserver: 1 zfs pool of 4x 20TB drives and 2x500GB NVME cache 1 zfs pool ssd-pool appdata and downloads When using Krusader to move from the downloads folder to the main pool, it give me the error of 'There is not enough space' while there is more than 50TB free. The same issue happens when trying to copy/move files from my Mainserver to my Backupserver over the local network. I use Unassigned Devices to connect with SMB to the backup server. I mount that share, restart Krusader go to 'remotes' go to the right share, and try to start a copy. With enough free space on the drives, I still get the 'There is not enough space' error. Krusader is set to run as 'root'. It does not run with Privileged mode. The strange things, after a clean install of Krusader (binhex or ich777) it works for a while (a couple of times) and then it does not work anymore. So what is happening that Krusader CAN copy/move first, and later not anymore?

Ok, I found something else. After installing ich777/krusader it works, even remote copying/moving works. And a couple of minutes later, I get the same error. (There is not enough diskspace). How come a new install of Krusader works for a couple of minutes, and then refuses to work? PS: I'm talking also locally here! So from my SSD-pool where Downloads are, I could copy a movie and later not anymore!

I found out that Krusader gives the error when trying to add data. Creating a folder does work without any issues. How come Krusader does not see the (ZFS Dataset) space? Creating folder works on remote destination:L Copying a file into that same directory, and I am getting the error:

Hi, If I mount a root share, with <my name> via Unassigned devices from my Mainserver to my Backupserver, or even the other way around, and using Krusader, even after restarting that docker, both Krusaders (the Mainserver or the Backupserver one) say that there is not enough disk space. The drives were empty! I did not have this issue before, but for a while, I cannot use Krusader anymore to copy to the other server. MC does work so what is different from MC vs Krusader? Could it be that Krusader is not able to work with datasets? I have tried with a root share, <my name> and on both servers the same password for that account. I have tried to mount the shares separately, also no success. What could be the reason for this behavior? MAINSERVER: Krusader config: Pool config with zfs dataset and space available Share mount to 'Backupserver' BACKUPERSERVER config:

Hi, If I mount a root share, with <my name> via Unassigned devices from my Mainserver to my Backupserver, or even the other way around, and using Krusader, even after restarting that docker, both Krusaders (the Mainserver or the Backupserver one) say that there is not enough disk space. The drives were empty! I did not have this issue before, but for a while, I cannot use Krusader anymore to copy to the other server. MC does work so what is different from MC vs Krusader? Could it be that Krusader is not able to work with datasets? I have tried with a root share, <my name> and on both servers the same password for that account. I have tried to mount the shares separately, also no success. What could be the reason for this behavior? MAINSERVER: Krusader config: Pool config with zfs dataset and space available Share mount to 'Backupserver' BACKUPERSERVER config: