mturcotte

Thanks again for your quick reply! You were right! Rebooting did bring everything back to life, except for domains which is not in the list of shares (not sure whether it was or is supposed to be listed in shares)... You are right about using the PERC H710P RAID controller without flashing it in IT mode... I was impatient to try unRAID and once I got it working on the H710P as is, I no longer wanted to risk breaking anything... Do you think it is a problem if I keep using it as is? Thanks! MT

Thank you for your quick reply! I started the array again and captured the attached diagnostics. I nocited that /mnt/cache still contains appdata, domains and system, but /mnt/user is not accessible: ls -l /mnt/user /bin/ls: cannot access '/mnt/user': Transport endpoint is not connected nexus-diagnostics-20220109-1535.zip

SHORT VERSION: Is there a way to recover after stupidly changing CACHE from PREFER to NO on appdata, domains and system? I have a backup but it was captured a few days BEFORE the addition of the NVME Cache drive, so I doubt it could be of help. LONG VERSION I made a rookie mistake my unRaid 6.9.2 configuration. I'm now looking for advice on the best course of action to resolve the problem I created for myself... I figured I should ask savvier people before I try to restore from the most recent backup I could find (2021-12-23), and potentially make things worse since that backup predates the addition and use of the NVME cache drive... After recently adding a 1TB NVME drive as a cache drive, I configured appdata, domains, system and a few shares as CACHE = PREFER. Everything worked fine and some 200GB ended up being used by these shares on the cache drive. Then, I realized I had not configured a minimum free capacity on the cache drive... So in an episode of peak stupidity, I tried to reverse course and move everything back 100% to the array... I set the appdata, domains and system back to CACHE= NO (thinking unRAID will surely transfer the data from the CACHE to the ARRAY). I think I should have set CACHE:YES and subsequently trigger the execution of the MOVER... Since those stupid changes, all shares seem lost. That said, I suspect the all the data is still there and there might be a way to recover from my stupid mistakes... Can anyone tell please me if there is a way back out of this situation^ My diagnostics info is attached for the current state of my unRAID 6.9.2 server. HW: Dell PE R720 with 8 x 3TB SAS drives (2 parity drives - was this a good choice?), 192 GB of memory and 2x Intel® Xeon® CPU E5-2680 0 @ 2.70GHz. Any help / suggestion will be much appreciated. Thanks, MT nexus-diagnostics-20220109-1349.zip