From 6243dc9cea8238767cf19587eab5f2bb4b115a41 Mon Sep 17 00:00:00 2001 From: Yann Dirson Date: Wed, 24 Sep 2025 10:44:09 +0200 Subject: [PATCH 1/2] Fix confusing wording about installation logs Signed-off-by: Yann Dirson --- docs/troubleshooting/installation-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting/installation-upgrade.md b/docs/troubleshooting/installation-upgrade.md index 2187f15b..7c4e6118 100644 --- a/docs/troubleshooting/installation-upgrade.md +++ b/docs/troubleshooting/installation-upgrade.md @@ -31,10 +31,10 @@ The target installation partition is mounted in `/tmp/root`. ## Installation logs -The installer writes in `/var/log/installer/`. +On the installed system, installer logs are kept in `/var/log/installer/`. The main log file is `/var/log/installer/install-log`. ## Debugging the installer -You can [build your own installer](../../project/development-process/ISO-modification). \ No newline at end of file +You can [build your own installer](../../project/development-process/ISO-modification). From b2c64a41a28d94034383208d434c9e7428b8e992 Mon Sep 17 00:00:00 2001 From: Yann Dirson Date: Wed, 24 Sep 2025 10:59:51 +0200 Subject: [PATCH 2/2] Document how to access the installer using ssh Signed-off-by: Yann Dirson Co-authored-by: Thomas Moraine --- docs/troubleshooting/installation-upgrade.md | 29 ++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/docs/troubleshooting/installation-upgrade.md b/docs/troubleshooting/installation-upgrade.md index 7c4e6118..5fa2fb45 100644 --- a/docs/troubleshooting/installation-upgrade.md +++ b/docs/troubleshooting/installation-upgrade.md @@ -29,6 +29,35 @@ When asking for help about installation errors, providing this file increases yo The target installation partition is mounted in `/tmp/root`. +### Getting remote access to host during installation + +While the console access method described above may be sufficient for simple issues, collecting full logs (install logs, kernel logs, etc.) often requires copying large amounts of data, which is impractical without direct file access. + +To enable SSH/SCP access during installation, you can use the Linux kernel command line to: + +- Activate the network +- Enable the sshd service with a root password of your choice + +For the most common case (setting up the network via DHCP), add the following parameters to the Linux boot section: + +``` +network_device=all sshpassword=YOURCHOICE +``` + +You can also use the `network_config` parameter (which defaults to `dhcp`) to define an alternative network setup. Here are some template examples; replace the capitalized values with your own settings, square brackets ([]) indicate optional parameters: + +``` +network_config=dhcp[:vlan=VLAN] +network_config=static:ip=IP;netmask=NETMASK[;gateway=GW][;dns=DNS1[,DNS2]][;domain=DOMAIN][;vlan=VLAN] +``` + +:::note +you can specify an interface name such as `eth1` instead of `all` if necessary, which can be useful when you need to setup a static IP address. +::: + +The ssh server will be available once the network is up. If you are unsure which DHCP address was obtained, you can use the shell console as described above to look it up using `ip a`. You can then connect as `root` using the password you provided on the commandline. + + ## Installation logs On the installed system, installer logs are kept in `/var/log/installer/`.