technologiq Posted November 24, 2022 Share Posted November 24, 2022 I added a second Cache drive and did NOT back up my current appdata (I am aware I am an idiot for not doing this). After a Reboot (to 6.11.5) my docker list was empty and the appdata is also empty. Restoring previous containers does nothing to help since the config files are missing. AppData share is set to prefer: cache. Am I f'ed and have to start from scratch or can I get my appdata back? Quote Link to comment
ChatNoir Posted November 24, 2022 Share Posted November 24, 2022 4 minutes ago, technologiq said: I added a second Cache drive and did NOT back up my current appdata (I am aware I am an idiot for not doing this). After a Reboot (to 6.11.5) my docker list was empty and the appdata is also empty. Restoring previous containers does nothing to help since the config files are missing. AppData share is set to prefer: cache. Am I f'ed and have to start from scratch or can I get my appdata back? Please attach your diagnostics to your next post, preferably before any reboot. Quote Link to comment
technologiq Posted November 25, 2022 Author Share Posted November 25, 2022 On 11/24/2022 at 11:06 AM, ChatNoir said: Please attach your diagnostics to your next post, preferably before any reboot. Thank you, diagnostics attached. vault-diagnostics-20221125-1127.zip Quote Link to comment
JorgeB Posted November 25, 2022 Share Posted November 25, 2022 Cannot see what exactly happened since the diags are after rebooting but no btrfs filesystem is being detected on either cache device, try this in case one or both were wiped: btrfs-select-super -s 1 /dev/sdX1 Do it for both devices, replace X with correct letter, if the command is successful for one or both reboot and post new diags. Quote Link to comment
technologiq Posted November 25, 2022 Author Share Posted November 25, 2022 root@Vault:/dev# btrfs-select-super -s 1 /dev/sdo No valid Btrfs found on /dev/sdo ERROR: open ctree failed root@Vault:/dev# btrfs-select-super -s 1 /dev/sdk No valid Btrfs found on /dev/sdk ERROR: open ctree failed Tried with array started and stopped with the same results. Quote Link to comment
JorgeB Posted November 26, 2022 Share Posted November 26, 2022 Your are missing the 1 in the end: /dev/sdX1 Quote Link to comment
technologiq Posted November 26, 2022 Author Share Posted November 26, 2022 Thanks @JorgeB, I tried it again with the correct command and had the same results root@Vault:/dev# btrfs-select-super -s 1 /dev/sdk1 No valid Btrfs found on /dev/sdk1 ERROR: open ctree failed root@Vault:/dev# btrfs-select-super -s 1 /dev/sdo1 No valid Btrfs found on /dev/sdo1 ERROR: open ctree failed Quote Link to comment
technologiq Posted November 26, 2022 Author Share Posted November 26, 2022 (edited) I *do* have a couple backups of Appdata that was made using the CA Appdata Plugin. At this point would it just make more sense form me to get my cache pool mounted & formatted as new and then perform a restore? Edited November 26, 2022 by technologiq Quote Link to comment
Solution JorgeB Posted November 27, 2022 Solution Share Posted November 27, 2022 That suggests they were never btrfs or they were completely wiped with a trim command or similar, you'll need to restore the data from backups. Quote Link to comment
Doublemyst Posted November 27, 2022 Share Posted November 27, 2022 I had the same issue on my second server. I've added a new disk and moved the one with the appdata as a cache drive. All of sudden, all my adguard settings were vanished. Fortunately this is a rather new server with only a few dockers, so I just reconfigured everything again. Quote Link to comment
technologiq Posted November 28, 2022 Author Share Posted November 28, 2022 (edited) Going to wrap this post up. Ultimately I got in this mess because I didn't know what I was doing adding the 2nd cache drive. After watching @SpaceInvaderOnes Youtube video on the subject I had a much better understanding. Fortunately for me I had the CA Appdata Backup/Restore plugin installed which had 3 recent weekly backups. All I had to do was re-set-up my cache and then restore the appdata folder do it. Once I did that, it was just a matter of reinstalling my previous dockers and I was good to go. This also forced me to re-evaluate my cache setup as well as wrapping my head around cache pools and the prefer/yes/no. I ended up creating new multiple cache pools and now my unraid is running faster than ever and all my data is properly protected. Thank you @JorgeB for your help! Edited November 28, 2022 by technologiq 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.