right now i wanna try practicing zfs and the benefits.. on one of my unraid servers

when i set the mover to move docker vms from the nvme to the array .. i onlky getting from 1 to 3 megs per second

i have the mover tunning installed and set to reconstruct... i have the docker and vms managers turned off but for some reason i getting piss poor speed i should get like what 80 to 250mbs roughly

but to transfer 74gb its going to take forever...

and the single array drive is a WD 7200 drive ... so not sure what causes it this massivly slow

only dockers i run is krusader, frigate,jellyfin,sftpgo

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread.

It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

sorry my bad i forgot as i didnt think it would have matter if its just a toggle switch or something.. here is the diagnostic.. i do know how know how long it took to move 74 gig but here is the log file

maybe you can see how long it took and if so how i can see in the future too how long it took

actually mover is still running but it looks hanged 145mb to go yet nothing is moving so i guess mover has crashed

looks like a bunch of errors too not sure what they mean but its complaining about the nvme i guess or the pool or i dunno sometimes i wish teh logs would explain things better sometimes i can never figure it out what its talking about

k-9-diagnostics-20260320-0731.zip

Edited March 20Mar 20 by comet424

oh and can you look at my main server diagnostic here.. do i need to reboot unraid more often? its been up 18 days.. but there is no error array login messages just text in the diagnostic and i dont really under stand all that whats going on there

i just figured id look now and i see its blank mostly except the text

tardis-diagnostics-20260320-0742.zip

@itimpi

so i rebooted the k-9 server and re ran mover but its still locked up

i looked at the nofications pop up on the screen and it shows share.cfg issue but i have shares is there a way to fix this and the other others or are the other errors due to the share.cfg issue

i re saved each share to update incase that fixes share.cfg

i then rebooted and re tried again still cant move

instant error as you see... so i not sure how i fix? or do you gotta reformat things?

Edited March 20Mar 20 by comet424

your K-9 server has an issue with your NVME drive

BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0

and is having further checksum errors

Mar 20 00:46:44 K-9 kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 147958 off 53248 csum 0xb0c0e1ae expected csum 0xb0c0e9ae mirror 1
Mar 20 00:46:44 K-9 kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0

Since you are not running the devices in a mirror a btrfs scrub will not repair the corrupted data.

Edited March 20Mar 20 by MowMdown

Youre going to want to likely run a memtest, you can do so from the unraid boot screen (blue screen with menu options) Look for Memtest86

@MowMdown oh ok ill give it a shot see what memtest shows up with

i cant seem to fix the mover crashing though share.cfg what does it mean? and how do i create a share.cfg?

guess its a global setting i tried the google ai

but gotta reboot unraid cuz mover has locked things up as you cant run it with the array on

Just now, comet424 said:

@MowMdown oh ok ill give it a shot see what memtest shows up with

i cant seem to fix the mover crashing though share.cfg what does it mean? and how do i create a share.cfg?

Your USB may not be writable and for some reason is missing the share.cfg file. Not sure what's up with that. Someone else may have to answer that.

But right now running a Memtest should be a #1 priority. I mean, it's what I would consider an emergency. Everything runs thorough RAM and if RAM is bad, your data can be compromised.

@MowMdown

ah ok i did try the reboot, stop array do the global share mount back on and run mover... no errors but it left files on the cache drive... so i then just used the the dynamic file manager and moved. and got errors

right now i rebooted and running memtest and see how it comes out with things... and you dont happen to know from my tardis logs why it just logs text stuff and is that stuff good or bad that shows up

so ill let memtest run and see where to go from there

rsync: [sender] read errors mapping "/mnt/unraid_files/appdata/Jellyfin/metadata/library/05/058b6f616292697635c6116c836b0c40/poster.jpg": Input/output error (5)

rsync: [sender] read errors mapping "/mnt/unraid_files/appdata/Jellyfin/metadata/library/78/78fe47a1df277d424eb6b7416edf32da/poster.jpg": Input/output error (5)
WARNING: appdata/Jellyfin/metadata/library/05/058b6f616292697635c6116c836b0c40/poster.jpg failed verification -- update discarded (will try again).
WARNING: appdata/Jellyfin/metadata/library/78/78fe47a1df277d424eb6b7416edf32da/poster.jpg failed verification -- update discarded (will try again).

rsync: [sender] read errors mapping "/mnt/unraid_files/appdata/Jellyfin/metadata/library/05/058b6f616292697635c6116c836b0c40/poster.jpg": Input/output error (5)

rsync: [sender] read errors mapping "/mnt/unraid_files/appdata/Jellyfin/metadata/library/78/78fe47a1df277d424eb6b7416edf32da/poster.jpg": Input/output error (5)
ERROR: appdata/Jellyfin/metadata/library/05/058b6f616292697635c6116c836b0c40/poster.jpg failed verification -- update discarded.
ERROR: appdata/Jellyfin/metadata/library/78/78fe47a1df277d424eb6b7416edf32da/poster.jpg failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]
This moves all the selected sources

13 minutes ago, comet424 said:

you dont happen to know from my tardis logs why it just logs text stuff and is that stuff good or bad that shows up

Only thing I see is you appear to have a docker container restarting/crashing constantly. You will want to check the uptime for each container on the docker container page to see if any are showing as recently restarted.

ah ok i know i was trying to get nextcloud aio to install on that server where i just had enough of it.. spent 2 weeks installing uninstallling installing uninstalling.. total bs and then i did get that nextcloud plain but if you copy files to an account on the server side the nextcloud doesnt detect it... you gotta run some docker scan or external storage google ai says yet it doesnt exist in the nextcloud plain

so thats a container i was starting stopping like 100 times... best do a reboot today to clear that up for now i shelved it wasnt happy with this nextcloud stuff

Then yeah if you were doing that, that would explain the container restarts in the log.

As far as the memtest goes, you will want to run that for at least 24 hours or unless you get a FAIL message. If you get a FAIL, you can stop the test and either retest each stick individually or replace the entire kit. Do not run the server on failed RAM.

It can take several passes to find faulty RAM

Edited March 20Mar 20 by MowMdown

You should stop that bad container, and set it to not autostart.

I recommend removing Mover Tuning plugin until things are working normally.

ah ok so uninstall jellyfin and then reinstall etc

i can do that i just experimenting as i going to post a new question about ZFS i have questions for

3 minutes ago, trurl said:

You should stop that bad container, and set it to not autostart.

And nextcloud

ok sounds good

@MowMdown so ive run memtest 2 1/2 times passed 2 times and on its 3rd.. gonna quit if it passes on 3rd.. maybe just a glitch.. i guess ill format the nvme drive and set it to zfs as i wanna try and then copy the dockers vms appdata back to nvme and maybe it will pick up speed using te mover will see. right? but no memory issues

so i formated the cache drive to zfs

i set the shares to go from array to cache

and ran mover it instantly stopped.. wasnt working.. i ended up uninstalling cache mover, and cache tunning

and set the disk settings to reconstruction write

i i re pressed move button.. and seems to be moving back but it went from 1-3 mb/s to a 6-8... 3meg read on the array and a 6-11mb/s write on the nvme

didnt improve much... here i figured it would jumped to 100mbs as a secon... wonder what is causing the slowness the ram ran 3 memttests and passed each one no fault

so its going to take a way to copy back... i know the disk speed test... but ive never been able to test the cache drives

and running "top" in the command line the "wa" fluxuates from 0.0 to 0.5 not sure if those are the good readings for the copy wait or so what i watch a video about slow mover transfers

Edited March 20Mar 20 by comet424

Attach Diagnostics ZIP to your NEXT post in this thread.

ok here it is

k-9-diagnostics-20260320-1520.zip

Edited March 20Mar 20 by comet424

56 minutes ago, comet424 said:

uninstalling cache mover, and cache tunning

reboot and try again just in case those plugins didn't clean up well enough.

still going slow need to kick its but into gear

i guess only way to test is to test with single files like 25 gig or so

and that the appdata be always slow as mollases

k-9-diagnostics-20260320-1540.zip

appdata and system shares have files on the array. So does vms share