Browse Source

add logs and clarify

dev
openoms 6 years ago
parent
commit
6473457b2b
  1. 25
      dietpi/README.md
  2. 5
      dietpi/RaspberryPi.md

25
dietpi/README.md

@ -7,7 +7,7 @@ This guide was tested on:
* Odroid HC1 * Odroid HC1
* Odroid HC2 (the same board with a 3.5" 12V HDD) * Odroid HC2 (the same board with a 3.5" 12V HDD)
* Odroid XU4 (with HDMI screen) * Odroid XU4 (with HDMI screen)
* Raspberry Pi 3 B+ (with the default GPIO or HDMI display support) * Raspberry Pi 3 B+ (with the default GPIO or HDMI display)
See the [hardware comparison](hw_comparison.md). See the [hardware comparison](hw_comparison.md).
@ -37,16 +37,16 @@ Look for the SD card image for the specific SBC in the [download section](https:
* Insert the SDcard into your SBC. * Insert the SDcard into your SBC.
* Connect the HDD with a suitably powered adapter. * Connect the HDD with a suitably powered adapter.
A USB 2.0 port will not be able to power an HDD so you will need extra cable. Aim to use 2 USB ports or a separate power supply to power the HDD for a more reliable setup.
If you are connecting the HDD to a USB 3.0 port and have an at least 2A power supply, you might be able to run without an extra cable.
* Power up and log in with the desktop terminal on Linux / MacOS or Putty on Windows: * Power up and log in with the desktop terminal on Linux / MacOS or Putty on Windows:
`ssh root@[IP-OF-DIETPI]` `ssh root@[IP-OF-DIETPI]`
password: `dietpi` password: `dietpi`
* You might be asked about updating DietPi. This is not a straightforward process if starting from a version <6.20. Try to update, it is best to build on the latest version. * If you are asked about updating DietPi, go ahead with it. This is not always a straightforward process, but it is best to build on the latest version.
* In the DietPi software menu install `fail2ban` and make `OpenSSH server` the default SSH server. * In the DietPi software menu install `fail2ban` and make `OpenSSH server` the default SSH server.
If there is a screen installed: within the Dietpi-Config menu set the Autostart to `7: Automatic login. `
Changing the SSH server will change the SSH keys again. To clear: Changing the SSH server will change the SSH keys again. To clear:
`ssh-keygen -f "/home/[your-linux-username]/.ssh/known_hosts" -R "dietpi.IP"` `ssh-keygen -f "/home/[your-linux-username]/.ssh/known_hosts" -R "dietpi.IP"`
@ -64,7 +64,7 @@ password: `dietpi`
`wget https://raw.githubusercontent.com/[GITHUB-USERNAME]/raspiblitz/[BRANCH]/build_sdcard.sh && sudo bash build_sdcard.sh [BRANCH] [GITHUB-USERNAME]` `wget https://raw.githubusercontent.com/[GITHUB-USERNAME]/raspiblitz/[BRANCH]/build_sdcard.sh && sudo bash build_sdcard.sh [BRANCH] [GITHUB-USERNAME]`
If you are working from a forked repo be aware of that the fork needs to be called `raspiblitz` for the git downloads to work. If you are working from a forked repo be aware of that the fork needs to be called `raspiblitz` for the git downloads to work.
* Run the dev branch of @rootzoll: Example to run the dev branch of @rootzoll:
`wget https://raw.githubusercontent.com/rootzoll/raspiblitz/dev/build_sdcard.sh && sudo bash build_sdcard.sh dev rootzoll` `wget https://raw.githubusercontent.com/rootzoll/raspiblitz/dev/build_sdcard.sh && sudo bash build_sdcard.sh dev rootzoll`
This will take a couple minutes depending on your internet connection and the processing power of the SBC. This will take a couple minutes depending on your internet connection and the processing power of the SBC.
@ -76,15 +76,16 @@ password: `raspiblitz`
--- ---
### Useful commands for debugging: ### Useful commands for debugging:
To test a new configuration run XXcleanHDD.sh and strictly restart During the Automated setup:
(this makes _bootstrap.sh and 00mainMenu.sh run in the right order) `tail -n1000 -f /tmp/DietPi-Update/dietpi-update.log` - follow the dietpi-update process
`tail -n1000 -f /var/tmp/dietpi/logs/dietpi-automation_custom_script.log` follow the output of the build_sdcard.sh
`tail -n1000 -f /var/tmp/dietpi/logs/dietpi-automation_custom_script.log` follow startup setup script log During the RaspiBlitz setup process:
`lsblk` see the partitions `lsblk` check the disk partitions
`tail -n1000 -f raspiblitz.log` - debug logs of bootstrap.sh `tail -n1000 -f raspiblitz.log` - debug logs of bootstrap.sh
`sudo tail -f /mnt/hdd/bitcoin/debug.log` - continuous monitoring `sudo tail -f /mnt/hdd/bitcoin/debug.log` - continuous monitoring of bitcoind
`sudo tail -n100 /mnt/hdd/bitcoin/debug.log` - shows the last 100 lines `sudo tail -n100 /mnt/hdd/bitcoin/debug.log` - shows the last 100 lines
`sudo systemctl status lnd` `sudo systemctl status lnd` - status of the lnd service
`sudo journalctl -f -u lnd` `sudo journalctl -f -u lnd`
`./home/admin/XXdebugLogs.sh` - debug log collection on the RaspiBlitz `./home/admin/XXdebugLogs.sh` - debug log collection on the RaspiBlitz

5
dietpi/RaspberryPi.md

@ -24,8 +24,9 @@ https://dietpi.com/downloads/images/DietPi_RPi-ARMv6-Stretch.7z
The automated setup will continue and the Raspberry Pi will restart at least twice during the process. This will take up to an hour. The automated setup will continue and the Raspberry Pi will restart at least twice during the process. This will take up to an hour.
To follow along: login with `root`. The output of the build_sdcard.sh script can be seen with: To follow the logs during the automated building process login with `root` and press CTRL+C.
`tail -n1000 -f /var/tmp/dietpi/logs/ dietpi-automation_custom_script.log` `tail -n1000 -f /tmp/DietPi-Update/dietpi-update.log` - follow the dietpi-update process
`tail -n1000 -f /var/tmp/dietpi/logs/dietpi-automation_custom_script.log` follow the output of the build_sdcard.sh
6) When the setup is finished log in as `admin`: 6) When the setup is finished log in as `admin`:

Loading…
Cancel
Save