-
Notifications
You must be signed in to change notification settings - Fork 108
Install troubleshooting with ssh #392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,12 +29,41 @@ 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. | ||
|
||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it would be useful to also explain:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I understand the need for "how to find the IP address when using DHCP", but I fear giving too many obvious details will just add noise to the doc. Doing as suggested, see the result for yourself. |
||
## 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). | ||
You can [build your own installer](../../project/development-process/ISO-modification). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're not starting the sentence with a capital letter?