Luv2Nap

I was able to use CA Backup / Restore Appdata to make a backup, or at least a partial one. The Plex metadata seems to have survived. After making the backup, I stopped the array, disable the cache disk and shut down. Then, I replaced the drive and started the server. I enabled the cache drive, started the array and formatted the disk. After that, I used CA Backup / Restore appdata to restore the backup it had made. I then tried to start the Plex service but it wouldn't or couldn't find the metadata. I then tried using Krusader only to realize it wouldn't launch. I ended up recreating docker.img and reinstalling the Krusader and Plex containers. Now, both apps are working and Plex seems to back to normal, all custom artwork and organization survived.

It looks like my single cache drive is going belly up. I started seeing SMART health warnings referencing reported uncorrect errors a couple of days ago. The reported uncorrect is now at 34155 on a 500GB Samsung 870 EVO SSD. I've checked the SATA cable, replaced it and checked it again. I've set the shares as Yes : Cache and disabled both Docker and the VM Manager before starting Mover. I've restarted the server a couple of times and Mover just can't move these folders. I've also tried using CA Backup and appears to have backed up the Appdata. I purchased a new 1TB Samsung 870 Evo Drive today and I'm ready to swap out the cache drive but I want to make sure I'm not missing something. I hate to swap the drive and find that server won't boot. Since these Cache folders were initially set as Prefer : Cache, the data appears to still be on the array. Can I just remove and replace the Cache drive and copy the data back onto it or do I need to set the shares as Prefer : Cache and let Mover handle it? central-syslog-20220122-0333.zip central-diagnostics-20220121-2135.zip