Troubleshooting
Troubleshooting
Section titled “Troubleshooting”Common issues and solutions.
Build Issues
Section titled “Build Issues”QEMU Won’t Boot
Section titled “QEMU Won’t Boot”Symptoms: QEMU hangs at boot
Solutions:
# Install UEFI firmwaresudo apt install qemu-efi-aarch64
# Increase timeout in config.shQEMU_TIMEOUT=3600
# Check logscat images/*/qemu-*.logQEMU Timeout
Section titled “QEMU Timeout”Symptoms: “QEMU timeout” error
Solutions:
- Increase
QEMU_TIMEOUTin config.sh - Increase
QEMU_RAMandQEMU_CPUS - Check network connectivity
- Review QEMU logs
Merge Fails
Section titled “Merge Fails”Symptoms: Error during merge stage
Solutions:
# Check disk spacedf -h
# Re-download base imagesrm images/debian/*.img images/debian/*.raw./bin/autobuild --image debian
# Check partition layoutfdisk -l raspios.imgfdisk -l debian.rawOut of Disk Space
Section titled “Out of Disk Space”Symptoms: “No space left on device”
Solutions:
- Free up space:
sudo apt clean - Use smaller
IMAGE_SIZE - Build fewer services
Boot Issues
Section titled “Boot Issues”Rainbow Screen
Section titled “Rainbow Screen”Symptoms: Raspberry Pi shows rainbow screen, won’t boot
Solutions:
- Verify image integrity:
sha256sum image.img.xz - Re-flash SD card
- Try different SD card
- Check UART output
Can’t Login
Section titled “Can’t Login”Symptoms: Credentials don’t work
Default: Username pi, password raspberry
Solutions:
- Check Caps Lock
- Wait for first-boot to complete (3-5 min)
- Reset password via SD card mount
No Network
Section titled “No Network”Symptoms: Can’t get IP address
Solutions:
# Check interfaceip link show eth0
# Restart connectionsudo nmcli con up br-wan
# Check NetworkManagersudo systemctl status NetworkManager
# Set static IP (see Configuration Reference)Service Issues
Section titled “Service Issues”Service Not Starting
Section titled “Service Not Starting”Symptoms: Docker/HAOS/OpenWrt not running
Solutions:
# Check first-boot logssudo journalctl -u services-first-boot
# Check service statussudo systemctl status dockerincus list
# Check disk spacedf -hContainer/VM Won’t Start
Section titled “Container/VM Won’t Start”Symptoms: Incus container/VM fails to start
Solutions:
# Check Incus logsincus info haosincus info --show-log haos
# Check resourcesfree -hdf -h
# Restart Incussudo systemctl restart incusHardware Issues
Section titled “Hardware Issues”WiFi Not Detected
Section titled “WiFi Not Detected”Symptoms: wlan0 doesn’t exist
Solutions:
# Check firmwaredmesg | grep brcmfmac
# Install firmwaresudo apt install firmware-brcm80211
# Rebootsudo rebootZigbee Not Passed to HAOS
Section titled “Zigbee Not Passed to HAOS”Symptoms: Zigbee dongle not in Home Assistant
Solutions:
# Check detectionsudo journalctl -u services-first-boot | grep -i zigbee
# Manual passthroughlsusb # Find vendor/product IDincus config device add haos zigbee usb vendorid=XXXX productid=YYYY
# Restart VMincus restart haosGitHub Actions Issues
Section titled “GitHub Actions Issues”Build Timeout
Section titled “Build Timeout”Symptoms: CI/CD build fails with timeout
Solutions:
- Increase
QEMU_TIMEOUTin workflow - Reduce
IMAGE_SIZE - Use fewer services
Asset Upload Fails
Section titled “Asset Upload Fails”Symptoms: Image built but not in release
Solutions:
- Check GitHub token permissions
- Verify release was created
- Check asset size (<2GB per file)
Getting Help
Section titled “Getting Help”Check logs:
# Build logscat images/*/qemu-*.log
# First-boot logssudo journalctl -u rpi-first-bootsudo journalctl -u services-first-boot
# Service logssudo journalctl -u dockersudo journalctl -u incusStill stuck?
Include:
- Build command used
- Error messages
- Relevant logs
- Hardware details (Pi model, RAM, SD card size)