Skip to content
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

Documentation, debugging #244

Merged
merged 2 commits into from
Aug 29, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/manpage.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,20 @@ If you have a problem with booster boot tool you can enable debug mode to get mo
information about what is going on. Just add `booster.log=debug,console` kernel parameter and booster
provide additional logs.

### Use TFTP to download logs for unbootable device
In case of a boot failure, when the devices are missing, logs can still be retrieved from busybox using the network.
First, set up a tftp server (port 69) on another machine/VM. For example on Archlinux, `pacman -S atftp; systemctl start atftpd`.
Then, edit `/etc/booster.yaml` and add [network support](#config-file) and busybox (`extra_files: busybox`).
Regenerate the initramfs and reboot. Once inside busybox, get the logs and send them to the tftp server:

$ dmesg >boot.log
$ lsmod >mods.log
$ tftp -pl boot.log <server ip>
$ tftp -pl mods.log <server ip>

The logs will be in `/srv/atftp` on the server.


## EXAMPLES
Create an initramfs file specific for the current kernel/host. The output file is booster.img:

Expand Down