Hi there. So today I found out the motherboard I was using for my unraid server failed, so I swapped it out with another I had lying around.

 

Part of this upgrade included the addition of a new nvme cache drive to go along with my existing SSD cache drive. As far as I am aware, I should be able to add the nvme to the cache drive pool, so I went ahead and did that. Since performing all of these changes though, I have noticed a few potential problems:

 

1. I have two cache drives now, Cache 1 and Cache 2. Both drives are 500gb, and I am still only seeing the available space from the existing cache drive (Cache 1)

 

2. When I invoke the mover, nothing happens? Not sure why, but it just refreshes the webui and I get no output. Currently there is 95gb on the cache, so I would like it to be moved. It instantly completes and does not move the data.

 

I did notice that there are some warnings for multiple btrfs profiles, which I attempted to fix by running a btrfs scrub as well as a balance. Both of which came back without any errors. Since I have these two cache drives, is there a recommended configuration to utilize both of these effectively? I'm guessing my setup isn't ideal, but I figured I would just configure the cache pool to use both drives to have 1tb of space. At this point I'm not sure what else I can check but I would appreciate any insights the community can provide.

 

Diagnostics are included via the attached zip

bigboy-diagnostics-20240502-0142.zip

 

Edit: 

There also are some current errors for shares that aren't using the cache drives at the moment, such as system, appdata, etc. which are currently set that way since I was trying to troubleshoot the cache disks. I typically have those drives set to prefer the cache.

Edited May 2, 20242 yr by 1ss67s9b
additional info.

According to the log there's nothing to move, share name you want moved?

None of your shares are configured to be moved. And most of them don't have any files on cache.

 

However, your appdata, domains, and system shares have files on the array. Ideally, these shares would have all files on cache or other fast pool, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

 

These shares should be set to Primary: cache; Secondary: array; Mover action: array->cache.

 

Nothing can move open files, so you have to disable Docker and VM Manager in Settings first. Then run Mover, wait for it to complete, and post new diagnostics.