alexanderSad

I have recovered some but it's worse than you described. I started with most of the data in the array before I updated and changed my cache setting. Unraid then copied my data from the array to the cache (good) and deleted it from the array (absolutely insane with the name cache). That is not a cache behavior. The word "move" is also between drives as then there is only copy and delete. I read the descriptions and concluded one option was from cache to array. Don't like not safe. One option is from array to cache. They must mean caching it. But no

This is not a description of what a write cache is though. Wikipedia: In no sensible context would a write cache (or read cache) mean data is removed from storage. Except unraid i suppose. Not that it brings back my data 💔 Proper read cache definition from wikipedia:

Like a "This will break a share" instead of a this will erase the data on the cache warning would have saved me

Well this was incredibly depressing. I thought I had set everything up to write to disk always What are my chances of finding the files with file recover programs on the caches? I just can't believe this happened. I really really would have expected a lot more warning with clearing the cache if the cache was in fact not a cache at all.

It was several times larger than the cache pool. I my understanding was that prefer cache was a read cache. Writes straight through to disk. That is how the write speeds behaved at least.

bildtemp is the name. Which despite it's name did not hold only temporary data.

Hi, I've been running an unraid server for a few years. A day ago a cache drive dired. I was running 2TB + 2TB + 128GB cache drives and the small one died. No issue erase and remove it. After that the system ran fine and I checked that my latest data was available. It was all good. Today the array wouldn't start. Complaining about the cache drives again. With the confidence of long load times when the disks spin up and having seen all my data after the last clear I cleared and recreated the cache pool. Seemed to work until I realized that one of my shares was just gone. Not listed in shares and I can't see it if I traverse the file system online. Not mountable from my desktop. I can see by the used space on my array that it still uses up space (probably around 7 TB) but I can't find any way to get my files. And this is the last share I would have wanted to loose. Reading through the diagnostics dump I can see the config for the share (bildtemp) but it has a comment added at the top "# Share does not exist" How do I recover from this? What went wrong? All help is greatly appreciated. It would crush me to loose this data. tower-diagnostics-20240429-2210.zip