Well today I am the gorilla nigger. On Monday I upgraded one of my Debian servers with a much larger hard drive so I can use it as an auxiliary NAS on top of my TrueNAS. When I was re-installing, I decided to opt for LUKS encryption, which I don't usually use for servers. I got everything set up the way I like and have done about ~40 hours of productive work since, stored only on the Gitea instance hosted on the Debian box.
Well yesterday night the power was knocked out and the servers went down. My TrueNAS is back up and running as if nothing happened, but now the Debian server is not recognizing my USB keyboard during the LUKS decryption at boot. Apparently this is because I opted for a "targeted" initramfs over a "generic" one during the install.
I've rebooted from a live CD to chroot in and regenerate the initramfs, however now I've discovered cryptsetup is unable to decrypt my LUKS partition using my passphrase. I've tried a few different keyboards, checked the layout, and no luck - I suspect my LUKS header file was corrupted somehow during the shutdown and I didn't read up enough on LUKS to make a backup of the header. Seems unlikely, but I'm quite sure I've entered my passphrase correctly.
I run weekly backups on Sunday, so I'm probably SOL on all of the work I've done this week. I'm going to fiddle with the memory a bit before I re-install, because apparently LUKS is memory-sensitive, but my hopes aren't high.
Don't be a gorilla nigger retard like me, and remember:
- Opt for a generic initramfs over a targeted one unless your hardware is fixed (laptops)
- When using LUKS encryption, backup your LUKS header file in case of corruption
- BACKUP YOUR DATA AS OFTEN AS POSSIBLE