CowboyPilot
Members
-
Joined
-
Last visited
-
Perfect, I suspected that would work but wasn't certain, ha ha. Thanks, I'll give it a shot! Is it going to spaz out when the GUIDs don't match up? Edit: Nm, I am confusing two things. Keep the GUID with the appropriate key and should be g2g I imagine.
-
Realized I never replied, sorry for the dead thread resurrection but yeah I did a correcting parity check and it didn't report any errors. Not sure because it seems to me like it should have and I remember being a little confused about that. It's had several successful parity checks since then though so I guess I'm in the clear, ha ha.
-
So in preparation for this move I wanted to grab an extra key but I've also been toying around with upgrading one of my existing licenses. I went ahead and just bought a new pro key, is there an easy way to move my whole config over to the new license/bootusb and basically keep my existing one as my backup key? I know that sounded confusing. Basically I have a machine running Plus, instead of upgrading that license to Pro and then buying another Plus key I just bought a Pro key and want to apply that to my existing installation and "bank" my Plus key for a future build.
-
I definitely did that. Good point!
-
Just spent two days copying over data to my new Unraid setup and after I powered it down (gracefully) to change some stuff out it reported that one of my encrypted drives was unmountable. The drive itself would unlock and the Luks header appeared to be correct. After fiddling around a while I was able to get it back via the following method (my drive was sde1) cryptsetup open /dev/sde1 luksRepair xfs_repair -n /dev/mapper/luksRepair --> This should be a read-only command. If you're nervous about anything on here make a dd image of your device first. This reported that I had a bad superblock so I reran the command as: xfs_repair -L /dev/mapper/luksRepair -> Took about 10 minutes to run. Found a secondary superblock that it substituted (or something like that) and then ran a bunch of other stuff. 10 minutes later my drive was back up and running. Hope it helps someone else!
