9 replies to this topic

[mikel]

Hi,

 

when I flash a new Pli image into a partition of my H7S, regardless of whether it is 7.3 or 8.0, about

ca. 167 new update files are then displayed during the update with the remark that I should rather reflash. A current image doesn't need so many new updates, does it? A short time after use, system files or plugins are deleted and the box no longer shuts down and does not start anymore, I can no longer get onto the box from the outside and have to put everything back on, this is only the case with Pli. As the last test I have restarted without an update and have already survived one night without a crash. What can it be and are these updates normal? I didn't have these problems before converting the new formatting / images.

 

So I can no longer use the Pli on my H7S under these circumstances!

 

Greetings Mikel

[littlesat]

Why can't you use it? Why do you need (immediately) update?

Edited by littlesat, 5 March 2021 - 11:48.

[mikel]

Hi,

 

I now have the box in operation without an update and will see whether it crashes repeatedly.
Then I can never do an update if the system offers these many updates every time, with the note you should re-flash?
And then my box crashes and nothing works.

If there are innovations, do I have to flash again every time?

 

What's the point? Where is the mistake here?

 

When can I update without having a problem?

Edited by mikel, 5 March 2021 - 11:59.

[WanWizard]

What isn't normal is that an update makes your box unstable.

 

I have on my development box regularly 500 or more updates (happens when the kernel needs rebuilding for example), and never a stability issue.

 

The only issue is that sometimes you need to run the update a few times, due to dependency limitation of opkg, the package manager. If you don't do that, you haven't installed all updates, and that could cause instability.

[mikel]

Hi,

 

Here is an example, if I flash a current Pli 7.3 on my Zgemma H7S, the following is displayed when I go to update:
"Do you want to update your receiver? (167 updates available) re-flashing is recommended!"

Where does the update come from when the image is up to date? When I do this, as already described, my box had a total crash after some time, sometimes only after 1-2 days, I noticed in between that it then deleted system files and plugins independently. Images from the OEA are not affected.

 

What could that be? Error only after converting new formatting / images for the box some time ago.

Edited by mikel, 5 March 2021 - 17:12.

[WanWizard]

This has been explained many times before.

 

We build OpenEmbedded the way it was meant to, using a full "build image". We also use shared feeds for ARCH packages, these feeds are shared by all boxes with the same ARCH.

 

The problem is that if package X  for box A is build, it creates X.r1 (release 1), and when the same X is build for box B, it creates X.r2, which overwrites r1. If you then flash A, the box will see that r1 is installed in the image, but r2 is in the feed, which it sees as newer, although they are binary identical. This explains why you see updates directly after a flash

 

The root cause of this problem is in the build toolkit of OpenEmbedded, called Bitbake. It was never designed for building multiple images. It is on my todo list to look into it and try to address this issue.

 

OE-A images have a completely different way of building images, and doesn't use a shared feed.

 

All this is not really relevant, as I wrote before, this should not affect the stability of the box in any way, the update from r1 to r2 in this example replaces files with exactly the same (binary equal) files. The only thing you have to do if you see so many files, is do another update once the first is finished, to make sure they are all correctly installed. This is needed due to shortcomings in the design of the package manager (opkg).

[mikel]

Hello WanWizard,

 

"This has been explained many times before."

 

Thanks for the explanation, since I am mostly in the German forum and this was not to be read there, I also cannot know. Nevertheless, there must be an error in the system if my H7S crashes afterwards?
And as I said, that wasn't the case before the new formatting / images for the H7, everything worked.

 

If that is the case, I can only use the Pli image without updating, if at all!

 

Greetings Mikel

Edited by mikel, 6 March 2021 - 10:35.

[WanWizard]

Without seeing error logs, it's only guessing what your problem was (or is).

[mikel]

Hi,

 

if the box crashes and I can no longer get onto the box from the outside, unfortunately it is not possible to get a log! If by chance I notice the system files ect. disappeared, possibly a log with a statement, but here the box does not yet provide a crash log.

 

The box has been running for the 2nd day without a crash with Pli 7.3, of course without an update after the flash.

Edited by mikel, 7 March 2021 - 09:58.

[rantanplan]

If the box 'crashes' it performs a reboot and always creates a log.

Your description is not a crash.
It hangs and cannot be reached. You can only see what is happening when the debug log is activated.
I wouldn't recommend updates either.
If you want an update, flash it.