Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2577 - Turris omnia: the medkit from master cannot be used to replace TurrisOS 4 #7455

Closed
openwrt-bot opened this issue Nov 5, 2019 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

rmelotte:

After building from the master branch (currently on 8184429), the generated medkit cannot be used to replace TurrisOS 4.0.1 with OpenWrt.

Steps to reproduce:

  • Flash TurrisOS 4.0.1 on the device.
  • Compile OpenWrt from master.
  • Boot from the initramfs from the medkit generated by OpenWrt (either through USB or tftp).
  • Use sysupgrade with the image you compiled from master.
  • The result is:
root@OpenWrt:/# sysupgrade -v /tmp/openwrt-mvebu-cortexa9-cznic_turris-omnia-sysupgrade.img.gz zcat: write error: Broken pipe zcat: write: Broken pipe Unable to determine upgrade device Image check failed.

Compared to the last release (18.06.4), sysupgrade now runs additional checks and tries to save existing partitions. It uses the "root" command line parameter to get information about the current partition.
When using TurrisOS 4.0.1, the "root" command line parameter is set to "b301", which is not taken into account by sysupgrade (specifically, "export_bootdevice" fails hence the "Unable to determine upgrade device").

Using "sysupgrade -F", also does not work since "platform_do_upgrade_sdcard" runs the same checks as "platform_check_image_sdcard" in the beginning, and "export_bootdevice && export_partdevice diskdev 0" fail.

In the meantime, a workaround is to first use the 18.06.4 release to replace TurrisOS (using the medkit then sysupgrade). After that, sysupgrade can be used again to flash the image from master. This works because sysupgrade from 18.06.4 blindly writes the image to "/dev/mmcblk0".

@openwrt-bot
Copy link
Author

rmelotte:

This issue can be closed, it has been fixed in: 3a4f587

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant