<![CDATA[Dev1 Galaxy Forum / [SOLVED] Save an installation protocol]]> https://dev1galaxy.org/viewtopic.php?id=6599 Sat, 11 May 2024 12:29:24 +0000 FluxBB <![CDATA[Re: [SOLVED] Save an installation protocol]]> https://dev1galaxy.org/viewtopic.php?pid=49890#p49890 ok; ctrl+f4 shifts to vt4, which is dedicated to tail -f /var/log/syslog of the installer. Thus, you can use ctrl+f2 and less /var/log/syslog to explore that, or use nc to transfer it to another host.

]]> Sat, 11 May 2024 12:29:24 +0000 https://dev1galaxy.org/viewtopic.php?pid=49890#p49890 <![CDATA[Re: [SOLVED] Save an installation protocol]]> https://dev1galaxy.org/viewtopic.php?pid=49889#p49889 Thanks for the feedback, I'll dig through that.

Anyhow, I am a step further today when I was yesterday. New questions arise now, new post to be written. I will close this one.

BTW: installation protocol in my understanding is a listing of commands and outputs of the system as you get on F4, just all logged into a file for later analysis.

]]> Sat, 11 May 2024 10:12:08 +0000 https://dev1galaxy.org/viewtopic.php?pid=49889#p49889 <![CDATA[Re: [SOLVED] Save an installation protocol]]> https://dev1galaxy.org/viewtopic.php?pid=49885#p49885 I think
https://cryptsetup-team.pages.debian.ne … -boot.html
is a fairly uptodate page, though as I don't use such encryption myself, I don't really know.

The short story is of course that the disk must hold bootloader and decryption software outside of the encryption, and the bootloader installation must know how to use that.

grub offers a granule of documentation at
https://www.gnu.org/software/grub/manua … mount.html
although that merely tells about what's possible rather than how to achieve it. But it looks like section 2 of the debian page above attempts to cover the additional hands-on.

EDIT: That doesn't answer to your actual question, which perhaps would be to use CTRL+F2 to get a command line and use that to explore the installer filesystem. I'm not sure what "installation protocol" is talked about though.

]]> Fri, 10 May 2024 23:21:59 +0000 https://dev1galaxy.org/viewtopic.php?pid=49885#p49885 <![CDATA[[SOLVED] Save an installation protocol]]> https://dev1galaxy.org/viewtopic.php?pid=49883#p49883 I tried twice now to install a Daedalus encrypted w/o separate /boot in a luks container holding a LVM for / and swap. Both legacy as efi installs fail from the 501 netinstall when writing the grub. Both in a Virtualbox VM.

With some poking around I managed to open a console with messages, I guess it was right CTRL F4. These messages do not really tell whats wrong, at least I can't see the reason for failure. I'd like to understand what is going wrong.

As far as I remember somebody told me that there also is some sort of protocol which I possibly could save. How do I get there?

]]> Fri, 10 May 2024 15:41:41 +0000 https://dev1galaxy.org/viewtopic.php?pid=49883#p49883