Login screen after webconfig and Update

Using Zynthian
1

Hi,
So, here is my first issue that I can’t seem to solve.

(For some reason) I chose “Update” in the webconfig interface via the zynthian 5.1 being connected by wifi.
I cannot remember all output on the webpage, but I remember “0 paths being updated” in the first line, and the last line was something like “fixing inverted display”.
The web interface then apparently lost connection.
The UI on the hardware was still working so I chose reboot from the Admin menu. After a long time (maybe 1min) the system went to power off (without coming on again).

When I boot the zynthian it now leaves me with a tty login shown on the display.
I can access via ssh but the webconfig interface is not running

What went wrong? Is there a way to fix this without “re-burning” the system image?

Thanks

Edit: I made some progress: here are some errors found in the systemd log (journalctl):

Maybe this is helpful:

May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/zynthian.service:14: WorkingDirectory= path is not absolute: #ZYNTHIAN_UI_DIR#
May 18 06:19:46 zynthian systemd[1]: zynthian.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/zynthian-webconf.service:10: WorkingDirectory= path is not absolute: #ZYNTHIAN_DIR#/zynthian-w>
May 18 06:19:46 zynthian systemd[1]: zynthian-webconf.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/zynthian-config-on-boot.service:10: Neither a valid executable name nor an absolute path: #ZYN>
May 18 06:19:46 zynthian systemd[1]: zynthian-config-on-boot.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/usb-gadget.service:7: Neither a valid executable name nor an absolute path: #ZYNTHIAN_SYS_DIR#>
May 18 06:19:46 zynthian systemd[1]: usb-gadget.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/mod-ttymidi.service:11: Neither a valid executable name nor an absolute path: #JACKD_BIN_PATH#>
May 18 06:19:46 zynthian systemd[1]: mod-ttymidi.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/jack2.service:11: Neither a valid executable name nor an absolute path: #JACKD_BIN_PATH#/jackd
May 18 06:19:46 zynthian systemd[1]: jack2.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/filebrowser.service:8: WorkingDirectory= path is not absolute: #ZYNTHIAN_SW_DIR#/filebrowser
May 18 06:19:46 zynthian systemd[1]: filebrowser.service: Unit configuration has fatal error, unit will not be started.
May 18 06:19:46 zynthian systemd[1]: /etc/systemd/system/a2jmidid.service:10: Neither a valid executable name nor an absolute path: #JACKD_BIN_PATH#/ja>
May 18 06:19:46 zynthian systemd[1]: a2jmidid.service: Unit configuration has fatal error, unit will not be started.

2

Hi, replying to myself once more…it’s sunday morning after all…

Relaunching the update_zynthian_sys.sh script from the shell repaired my issue!
The script took more than 10minutes, and probably because I seem to have SD card issues, as some reported already.

dmesg output this while the script was running:
[ 2566.018599] mmc0: Card stuck being busy! __mmc_poll_for_busy
[ 2576.098587] mmc0: Card stuck being busy! __mmc_poll_for_busy
[ 2586.111679] mmc0: Card stuck being busy! __mmc_poll_for_busy
[ 2596.194569] mmc0: Card stuck being busy! __mmc_poll_for_busy
[ 2606.238562] mmc0: Card stuck being busy! __mmc_poll_for_busy

Will consider a new card, but I’m intreagued. This one is a Sandisk UltraPlus 32Gb … and should be a good one.

Best

3

Did you use Balena Etcher or some of the similar bloaties? If so, then this is the trouble-maker.
Please try to use Raspberry Pi Imager instead. For OS select Use Custom and lelect the ZynthianOS image (no need to unpack), without customisation / preconfiguration (choose No when asked).

@jofemodo In the Wiki is still Etcher recommended, but Etcher does not write MicroSD reliably. Strange enough, it does not even show a verify error, but the data on the card is still not correct. Please consider recommending the Raspberry Pi Imager, if that is possible without problems.

4

I agree. I stopped using etcher once I kept getting issues after writer zynthian images. Raspberry pi imager works without issues every time.

5

OK thank you all for these hints. Message received!

I used the Ubuntu disk tool (yes another one of the bloaties ;)). Will try with the raspberry tool soon.

Best