FAQ
During install a debug file is generated at the path /home/pinodexmr/debug.log Any errors from a failed install are passed to this file and may be helpful should you have a problem. Most commonly errors on first build are due to a dependency not being downloaded (server 404), the install command can be run multiple times. This file can be downloaded for viewing in the 'logs' tab of the Web-UI.
When updating to a new version of Monero, a failure at around the 43% is typically due to now enough RAM, enable a large SWAP file if this is experienced.
Ensure you only connect with **either ** Ethernet or WiFi, not both. PiNodeXMR uses the command 'hostname -I' to establish IP's and uses the first value. Multiple connections (and therefore multiple IP's) confuses it. On this matter ensure your router assigns your PiNodeXMR with a static local IP. This should eb found in your router settings menu.
Feature update scripts (with exception of PiNodeXMR updater) delete the selected feature and install a new version from source after checking dependencies and updates. If a feature doesn't work as expected an update will give a fresh install and may provide the latest fixes to your problem.
The PiNodeXMR updater is the only file I can control that your device reaches for externally when updating on your say so. It is always pulled from the GitHub repository an so allows me to provide patches to the other updater scripts. The script will save and restore your Web_UI variables (RPC username, password, bandwidth settings, peers etc) and then overwrite PiNodeXMR with the latest files, including the other updater scripts.
Errors regarding a corrupt blockchain are often due to unexpected complete power loss, or a cheap power supply not giving the required voltage. Ensure your power supply is more than adequate for both your device and it's peripherals (USB drive +anything else plugged in). It is possible but rare that a corrupted blockchain can be salvaged with either --db-salvage or --pop-blocks.
If your USB drive randomly unmounts when Monero is running and you use a Raspberry Pi, it could be caused by your USB adapter. It is talked about here https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931
- USB Not mounting on boot (rare) More unusual and technical, but connecting multiple USB storage devices which have the label 'XMRBLOCKCHAIN' (for restore) can confuse the USB storage helper. When it assigns the UUID to /etc/fstab for boot mounting it will add the first drive from the list 'lsblk'. Only attach one drive at a time containing label 'XMRBLOCKCHAIN'.
