-
Slow Transfer Speeds on Unraid - Help Needed
Sorry for the late update. It seems the plugin was the problem, for some reason it was not triggering the TurboWrite. uninstalling and doing it manually fixed the issue. Thank you!
-
Slow Transfer Speeds on Unraid - Help Needed
Turbo wrtie is on through TurboWrite Plugin. right now I have 2 transfers, I tried with just one, and I have the same problem. 1 - Cache(raidz) to Disk 7(xfs part of array) 2- Disk 1 to Disk 1 (initially was transfered from an old server using Rsync, already added new permissions to all file/folders with new permissions. essentially from a folder to a dataset on Disk 1 (/mnt/user/movies/ to /mnt/user/data/media/movies/) at least thats what i think it is.
-
Slow Transfer Speeds on Unraid - Help Needed
If you take a look at the transfer on the right, its "reading" from a ZFS and "writing" to a XFS, do you think this is just because of ZFS problems or there might be something else wrong with it? how about a separate ZFS pool? do you not recommend having a ZFS Cache/pool at the moment?
-
mdaryabe changed their profile photo
-
Slow Transfer Speeds on Unraid - Help Needed
Even when attempting a single transfer at a time, I encountered the same issue. I was just follwing Spaceinvador's video that suggested this setup. The transfer on the left in the picture, is a "move" on the same disk. shouldn't this be almost instantly?
-
mdaryabe started following Invalid folder within /mnt and Slow Transfer Speeds on Unraid - Help Needed
-
Slow Transfer Speeds on Unraid - Help Needed
Hi everyone, I'm experiencing slow transfer speeds on my Unraid server and could use some advice on how to improve performance. Here are the details: System Configuration: Array Devices - media pool: 2 Partity - 22TB Seagate IronWolf, 18TB Seagate IronWolf 6 x 18TB Seagate IronWolf drives (XFS file system) Disk 1: 18TB Seagate IronWolf (ZFS file system) Cache Pool: 3 x 2TB TEAM SSDs (ZFS file system - raidz) Plex Pool: 3 x 480GB Kingston SSDs (ZFS file system - raidz) ZFS Pool - family/backup pool: 6 x 18TB Seagate IronWolf drives (ZFS file system - raidz2) Spare: 1 x 18TB Seagate IronWolf (ZFS file system) Issue: I'm transferring large amounts of data using Krusader, and the transfer speeds are extremely slow: Transfer 1: 10.9 MiB/s (3 days and 9 hours remaining) - from Cache pool to Disk 7 in the array. Transfer 2: 4.6 MiB/s (7 days and 8 hours remaining) - from a folder to a dataset on Disk 1 (/mnt/user/movies/ to /mnt/user/data/media/movies/). Observations: The move on all XFS drives worked almost instantly, but on ZFS drives/pools, it seems super slow, there are peaks, but average 10-15MiB/s. The mover does not get triggered, even manually, so I am transferring the files manually. Every couple of hours, I get a notification error from "Fix Common Problems," but most of the time, when I go to the plugin, it is clear. Occasionally, I get the "Write Cache is disabled on cache 2" error, even though I have already enabled it. What I've Tried: Tried using both Krusader and Unraid GUI file manager, with the same slow results. Request: I'm looking for advice on how to optimize my setup to achieve better transfer speeds. Here are some specific questions: Are there any specific settings or configurations for ZFS that could improve performance? Other general tips to improve transfer speeds in Unraid? Any help or insights would be greatly appreciated! Thank you!r540-diagnostics-20240618-0159.zip
-
Invalid folder within /mnt
Thank you everyone
-
Invalid folder within /mnt
Sorry, UD installed but no Recycle Bin
-
Invalid folder within /mnt
I Have UD Installed but not the recyle bin
-
Invalid folder within /mnt
Hi Everyone, I got an error in fix common problems in regards to an invalid folder in /mnt. A quick search and suggestion was to restart the server which I did. but unfortuanly that did not fix the problem. There is a "rootshare" folder in my /mnt that I have no idea how it got there. I haven't installed anything new on the server for a few weeks. Just general docker/plugin update. I have browsed to the folder, It's empty. I have tried to delete the folder but I get permission denied. I have tried using "MC" to delete it; with same results. Could you please take a look at it and maybe point me to the right direction. Thank you Invalid folder rootshare contained within /mnt caspian-1-diagnostics-20220311-0858.zip
-
Unmountable: not mounted
That worked! Thank you so much. Just for clarification, If now I want to replace Disk 7. I would just shut down the Array and replace that drive physically and run the array and let the parity rebuild the drive?
-
Unmountable: not mounted
So I ran "-L" on disk 5, shut down the Array and turned it back on and it seems that it fixed Disk 5, it is now mounted with around 6TB data on it. Should I do the same for Disk 8?
-
Unmountable: not mounted
- Unmountable: not mounted
Disk 5 and 8 both: Should I use the following command for Disk 5 with 2 parity drives? caspian-1-diagnostics-20210820-0844.zip I much appreaciate your help!- Unmountable: not mounted
So the parity-checkl/data-rebuild is done on those drives. they both show as green on the main page but they both still say "Unmountable: Not mounted" Do you need an updated log file?- Unmountable: not mounted
Thank you, I have updated the screenshots. I'll wait for the parity to finish and will update you. So Disk 7 and 8 were the disk I was trying to replace. What happened is, that I unplugged disk 5(didn't count the parity drives on the physical server while array was on - Dumb me!) and plugged it back in right away. Then shut down the array and replaced both 7 and 8. Unraid said it's missing more than 2(Disk 5, 7, 8 ) drives from parity and is unable to fix it. so I replaced back disk 8(original 4tb) with only disk 5, 8 missing I started the parity/rebuild. which did it for Disk 8. After that, I went on Maintenace mode to do the check for Drive 5. and it was giving me an error. I shut down the array and removed the drive from the array and started without disk 5. then turned off the array and added disk 5 again and started the parity check. Btw Disk 5, is the same original disk. it was just unplugged and plugged back in right away. I think it rebuild the array without that disk once, and now it's rebuilding that 8tb(Disk 5) drive again. Disk 7 is the next disk I want to replace after its fixed. Once again, Thank you for your help! - Unmountable: not mounted