Recovery from an Unbootable Zynthian

This topic is for people who have had trouble with their Zynthian. If Zynthian doesn’t boot, and doesn’t ‘end’ you may be stuck. You may be able to access webconf and fix the problem from there, but sometimes you can’t access webconf. In many cases, you will be able to “ssh” then login to root, password opensynth, and from there you can use journalctl to look at logs to see what happened, or run a command (script) to re-scan the hardware, or do anything else from the Unix Command Line or “terminal“.

1 Like

I don’t know if this is a Vangelis problem, but once again Zynthian can’t boot properly. This time i tried to connect via usb my Behringer 404 HD sound card and after rebooting i’m stuck at the black screen of Zynthian login. Disconnecting the 404 doesn’t fix the situation, and even webconf is unreachable.

I can backup all my snapshots with Filezilla but i’d like not to start again from scratch with a new sd card.

Here’s a bit more detail on setting the Zynthian “first boot” flag so that it will probe for installed hardware, you run a script:

$ZYNTHIAN_SYS_DIR/scripts/set_first_boot.sh

$ZYNTHIAN_SYS_DIR is a variable which holds the Zynthian directory name, typically it is just zynthian.

After running the script you shutdown and restart Zynthian.

@Nicolaz- let us know if you are stuck at how to ssh-login to your un-bootable Zynthian or if you can get there, need help with how to get the log(s) exported through journalctl or running set_first_boot.sh.

You can find lots of info by searching in this forum, or the wiki, and even just the web for things like ssh which is regular Linux, which is what Zynthian and ZynthianOS actually is, more specifically currently Debian version 12 AKA bookworm, customized of course.

Thanks, it worked but the script deleted all the snapshots, wich i hadn’t saved yet. Luckily i have an old backup from early March.

1 Like

Great! Sorry about the loss of snapshots, we’ll have to remember that and copy them off the sd card before running set_first_boot.sh. I’m glad it wasn’t significant this time.