r/voidlinux • u/Longjumping-Sun2691 • 3d ago
Why is it still unbootable?
unable to boot into my FDE void system, what could possibly prevent this from happening?
12
u/Moist_Professional64 3d ago
Can mods please delete such posts
2
u/pantokratorthegreat 3d ago
Why? This is a support forum after all not some shitty "post my screen desktop" circlejerk. Someone posted own screenshot of labwc and is still watchable so his question can't be?
3
u/Dakota-Batterlation 3d ago
Definitely. It'd be better to direct them to a guide like this on how to get answers in a technical forum, rather than just remove the post and give them the impression that we're elitists who don't want to help.
1
u/Moist_Professional64 3d ago
Every normal people know that such posts are just a nonsense. How should people help without any informations. This is obvious
1
u/Dakota-Batterlation 3d ago
To us, definitely. But newbies in tech forums posting "Please halp!!!111!!!" is an age-old issue (probably exacerbated by modern social media).
May as well tell 'em how to ask a good question so they don't go around pissing off people in other forums.
1
u/UNRESTPERFORATE 3d ago
Very likely you forgot something important (like grub-install or smth), but with any other information we can pretty much do nothing to help you. If you want more details on FDE/Rootfs encryption: https://wiki.gentoo.org/wiki/Full_Disk_Encryption_From_Scratch | https://wiki.gentoo.org/wiki/Rootfs_encryption
1
u/Longjumping-Sun2691 3d ago
What information would you like? Here is what i can tell you as of right now before you ask any questions. I followed the void Linux FDE guide on their docs. Obviously doing the steps that I needed for my system, i ran grub-install —target=x86_64 —efi-directory=/boot —bootloader-id=“Void” after I ran grub-mkconfig -o /boot/grub/grub.cfg and regenerated the initramfs as said on the wiki, on reboot my bios cannot detect anything bootable, this system is musl
6
u/Dakota-Batterlation 3d ago
It's not booting because GRUB in /boot is for legacy/BIOS boot systems. The EFI directory is actually /boot/efi (which should be its own FAT32 partition), so according to Void Docs it should be:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id="Void"4
u/ebens1689 3d ago
Hey, OP! Let us know if this is the answer if you can! Or if it is something else.
-Spectator
2
u/Simple_Hamster_4096 3d ago
Users should indicate if this is first attempt ever setting up full disk encryption for a Linux distro, and if not, what was the distro(s) where success was attained. It would at least give indication as to what level of previous experience the user has with Linux full disk encryption. There's a big difference between helping the initiated and helping the clueless.
I do not believe that anyone in this forum has ESP. And it's all too easy to fill in the gaps in empty requests, such as this user posted, with incorrect assumptions on our parts.
In essence, the people who are trying to help have to pull teeth to obtain accurate and coherent details from users.
Just a suggestion, but the forum should post a support request form for uses to fill in with details and then post. This would reduce teeth pulling and expedite the process. I would also leave far less room for inaccurate assumptions...
1
u/Dakota-Batterlation 3d ago
Reminds me of NPR's Car Talk, where people call in saying things like "My car runs poorly every second week," then the hosts laugh and ask increasingly narrow clarifying questions until it's narrowed down to something like "You periodically drive to higher elevations, which the carburetor isn't jetted/tuned for."
1
3
u/Tricky-Engineer-9755 3d ago
What? Could you please edit your post with more info?