Berryboot

On this page
  1. Summary
  2. Who this is for
  3. What you'll do
  4. Requirements
  5. What Berryboot is
  6. Berryboot Status for Banana Pi
  7. Step-by-step setup
  8. Concrete example (backup before changes)
  9. Troubleshooting
  10. FAQ
  11. External reference
  12. Related guides

Berryboot multi-boot - Boot menu selection screen with multiple OS options

Summary

Historical Berryboot resource. Current Banana Pi image compatibility and maintenance status have not been established. The current upstream Berryboot page is a project reference, not proof of support for this board. No working Banana Pi download, current kernel or safe conversion of an arbitrary OS image is promised.

Who this is for

Users wanting to test multiple distributions without swapping SD cards, educators managing classroom setups with multiple OS options, developers maintaining separate development and production environments on one board, and anyone curious about Berryboot's capabilities and limitations.

What you'll do

  • Install Berryboot bootloader to SD card or eMMC storage.
  • Configure boot menu and add multiple OS images.
  • Understand Berryboot's SquashFS overlay system.
  • Manage storage space across multiple OS installations.
  • Troubleshoot boot menu failures and OS corruption.
  • Implement backup strategies for multi-boot configurations.

Requirements

  • Storage: Minimum 8GB SD card or eMMC; 16GB+ recommended for multiple OS images. Fast storage (UHS-I) improves boot times.
  • Power: Stable 5V 2A supply. Multiple OS installations stress storage; voltage drops cause corruption.
  • Network: Ethernet connection for downloading OS images during Berryboot setup.
  • Display: HDMI monitor for initial Berryboot GUI setup. Serial console recommended for recovery.
  • Backup storage: Spare SD card with working single-OS setup for fallback.
  • Patience: OS downloads within Berryboot can take 10-30 minutes depending on image size.

What Berryboot is

Berryboot replaces the standard bootloader (U-Boot) with a custom menu system. It stores OS images as compressed SquashFS files in a shared data partition, overlaying a writable filesystem at boot. Benefits: easy OS switching, space-efficient storage. Drawbacks: shared kernel (can cause compatibility issues), additional failure points, harder recovery if bootloader corrupts.

Compatibility/status review, 1 November 2026: no exact current Banana Pi Berryboot artifact, supported board revision or publisher checksum was verified. Existing historical material is archival, not a recommended security-maintained installation. Prefer the board-specific image workflow below. A normal raw SD image is not automatically a Berryboot-compatible image.

Find board-specific OS images

Verify your image and installation media

Step-by-step setup

The earlier generic install/add-OS sequence is withheld because no current exact-board image and recovery path was verified. Before any storage write, back up the target, establish board/revision and image format, obtain the publisher’s checksum and retain a known-good board-specific recovery image. Do not convert or flash arbitrary distributions based on this archive.

Concrete example (backup before changes)

# Save configs and key logs before modifying boot layouts
tar -czf lemaker-backup-$(date +%Y%m%d).tgz /etc /var/log

# Backup entire Berryboot data partition (from another Linux machine)
sudo dd if=/dev/sdX2 of=berryboot-data-backup.img bs=4M status=progress

# Clone OS within Berryboot menu before updates (right-click OS > Clone)

Troubleshooting

Boot menu does not appear; blank screen or kernel panic

  • Symptoms: Black screen after power on; cursor blinking but no GUI; kernel panic messages on serial console.
  • Steps:
    1. Connect serial console to capture boot messages. Look for "Kernel panic" or filesystem errors.
    2. Verify storage integrity: Remove SD card, insert in PC, run fsck on data partition.
    3. Re-flash Berryboot bootloader: Backup data partition if possible, then re-flash Berryboot image.
    4. Check HDMI connection and monitor input. Try different HDMI cable/monitor.
    5. If corrupted, restore from backup or start fresh Berryboot installation.

OS fails to boot; returns to menu or kernel panic

  • Symptoms: Select OS from menu, screen goes black, then returns to menu; or system freezes/panics during boot.
  • Steps:
    1. Check if OS image is compatible with Berryboot kernel version. Older OS images may require older Berryboot.
    2. Try booting different OS from menu. If others work, suspect corrupted image.
    3. Delete and re-download problematic OS image.
    4. Check storage space: df -h. Insufficient space causes overlay filesystem errors.
    5. Examine serial console logs for specific driver or module loading failures.

"No space left on device" errors; cannot add new OS

  • Symptoms: OS installation fails partway; applications cannot write files; boot fails with filesystem errors.
  • Steps:
    1. Check available space in Berryboot menu (shows total/used space).
    2. Delete unused OS images: Right-click > Delete.
    3. Clean up within booted OS: sudo apt clean (Debian/Ubuntu), remove old logs.
    4. Consider larger SD card. Berryboot can be migrated to new storage via "Copy OS to USB".
    5. Use external USB storage for additional OS images (configure in Berryboot advanced settings).

Random corruption; OS boots but files disappear or change

  • Symptoms: Configuration changes revert after reboot; files disappear; random application crashes.
  • Steps:
    1. Replace SD card immediately. Failing storage causes silent corruption in overlay filesystem.
    2. Test new card: sudo badblocks -wsv /dev/sdX before use.
    3. Verify power supply stability. Voltage drops during write operations corrupt Berryboot overlay.
    4. Avoid improper shutdowns. Always use "Shutdown" from OS or Berryboot menu.
    5. Restore from known-good backup if corruption is extensive.

FAQ

Is this a current Banana Pi installation recommendation? No. Exact board/image compatibility and ongoing security maintenance remain unverified. Can any Linux SD image be used? No such compatibility is established. Is the upstream project abandoned? This review does not establish that; absence of a verified Banana Pi artifact is a narrower finding.

External reference

Author: LeMaker Documentation Team
Last updated: 2026-01-20