Hello all,

O am looking for a bit of direction here. I made a major server upgrade over the past week. I upgraded from a dell 710 to a supermicro x10, increased my parity drives to 12tb, my cache pool to 1tb.

The issue was timing or project management.

My goal is to have to parity protected cache pools , a 1 tb pool and a 240gb pool. I want to use the 1 tb for downloads and temp files TDAR and plex. and the 240 for everything else.

 

My mistake was starting the system with only the 1tb. I think that I have fouled things up. 

I added the second pool yesterday. changed the cache that the shares pointed to and ran mover. Nothing happened it ran for under 10 minutes.

 

My next mistake (possibly) was that I set the shares to yes, expecting the data to be pulled of "both" pools and moved to the array, and ran mover.

12 hrs later mover is still running, no change in the 1tb  drive it is still showing 1.21gb used and the 240 went from 40mb to 1.06gb used.

 

I am showing reads and writes but do not think that this is working properly.

 

Thoughts

diag attached.

 

Thanks Chas

tower-diagnostics-20230127-0823.zip

Sorry the 1tb drive has 121 gb not 1.21gb

Current one share works with one pool only, which pool is set on shares, you can use the mover to move data from a pool to the array and then to a different pool.

I'm thinking that my issue was because I didn't stop and start the array. I stopped mover. double checked that all shares that use the cache, were changed from prefer to yes. stopped the array, restarted the array and started mover.

We will see if this works

 

Chas

I am still getting these warnings in common problems.

Should I have moved files manually?

 

Mover moves cache:yes shares from the designated pool to the array, and moves cache:prefer shares from the array to the designated pool. Mover ignores files on other pools, and it ignores cache:no and cache:only shares.

So If I read this right, my error was changing the assigned cache pool before I change the cache setting to yes. I told mover to look in a share that did not have files for the files.

Unfortunately I do not know the steps to correct this.

Currently mover is running. I have appdata folders on both pools, they have different information in them (not sure how I did that)

Pool# 2 appdata folder reflects dockers that I am currently running (set to auto start)

Pool# 2 only has appdata on it (as of now, mover is running)

pool # 1 is all of the dockers that are installed including ones that are not currently in use.

Pool# 1 has all shares including appdata

Not sure if it is possible to screw this up more than I have already.

 

Pool # 1

 

 

Pool #2

 

 

Shares

After mover has finished, go to that last screenshot (User Shares) and click Compute All button at bottom, wait for the results, then post a screenshot and new diagnostics.

 

Another thing you need to look out for is if any of your dockers specify a path on a specific pool instead of a user share path. /mnt/cache_1tb/appdata instead of /mnt/user/appdata, for example.

Well 30 hours later and Mover is still running, seems like there is an issue here, should I stop mover and try something different?

 

Chas

Post new diagnostics

Sorry, I had ran out of patience before your reply (patience with my system, not your communication) 

 

I think that I know what I was doing wrong, and I hope that I am moving the right way now.

 

Docker and VMS were running on my system while mover was running, unless I am mistaken that requiered mover to check each and every file to see if it was in use before moving it. I'm not sure if it could or would move it if it was in use but I'm pretty sure that this check would slow down mover.

 

I ran Mover Stop. Set all of my Shares to the yes: 1tb  which is where the appdata was before I started this fiasco.

I then erased the data in the 250gb share pool, unraid then asked me to format the drives 8^)

I formatted and Unraid recreated the 240gb pool.

 

Next I stopped docker and my vm, then set both docker and vms to no.

Started mover again.

 

I think that everything is working right now, if I go to shares and click on compute on my appdata share I see it moving to the array.

 

Thank you for the assistance, I will update later if all works well, or if not I'll be back asking for help again.

 

Chas

 

 

 

29 minutes ago, kysdaddy said:

unless I am mistaken that requiered mover to check each and every file to see if it was in use before moving it.

It doesn't bother to check, it just fails to move the file the same way anything would. Nothing can move open files.

 

What you should have done is Disable Docker and VM Manager in Settings before attempting to move these files.

 

I'm not clear about the rest of your explanation but Diagnostics would help a lot with understanding where you are now and how you have things setup.

 

Attach diagnostics to your NEXT post in this thread.

 

 

You are correct, my mistake was not stopping docker and VM.

The good news is my roundabout path did reach the destination and all is running properly now.

Thanks again.

 

Chas