Open utterances-bot opened 9 months ago
One error i've noticed: when setting the /etc/fstab, you don't want to use the UUID of /dev/md1 for the /boot mount. That will result in an error on booting since md1 will already be mounted for your root mount point. You want the UUID of /dev/md0, which is the one actually set up for /boot.
Good catch @metal-crow, that's definitely an error! I'll try to fix it this week ☺️. Thanks for reporting it, I really appreciate it!
no prob! Thank you for this guide as well, i really appreciate it! It was a lifesaver :)
I am glad it helped someone 🥳 I fixed it quickly and the changes are live - thanks once again!
Thanks for writing this tutorial. I can confirm that grub is able to load the v1.2 raid metadata and the system boots as intended.
Regarding debootstrap: You manually downloaded the packages to modify the path so that it runs from the tmp directory. But as far as I could see you are not actually modifying anything (anymore?) that makes it necessary to run from /tmp. Or am I missing something? I simply installed debootstrap from the apt repository and it worked just fine.
Even if you actually need to change the DEBOOTSTRAP_DIR, in recent versions of debootstrap it should be possible to override it by using an environment variable.
Manually installing Debian 12 (Bookworm) with fully encrypted LUKS (besides /boot) using debootstrap | Steffen’s random thoughts
Introduction In this post, we’ll cover the installation and configuration of a Debian 12 (Bookworm) system within a live environment. Such a live system could be the Hetzner rescue mode, or any other live CD based on Debian, such as SystemRescue [formerly known as SystemRescueCd]). In this example we are going to use the Hetzner rescue mode.
https://blog.scheib.me/2023/08/28/debootstrapping-debian-bookworm.html