8 replies to this topic

[Qu@rk]

I had multiboot running but in June 2024 after an update of my OpenPLi 8.3 slot my VU+ DUO4K did not boot any more (kernel updated?, multiboot kernel overwritten?). I had to perform some tricks to get my box running again (inject a kernel image from an older backupsuite image into a recent image backup). But I Iost all my slots and settings in there.

 

I am running OpenPLi 8.3 on a VU+ DUO4K as my daily driver.

I would like to try OpenPLi 9 and OpenATV again.

 

My steps to do that would be: Is this the correct procedure?

• Create an image backup of my OpenPLi 8.3 with backupsuite.
• Flash OpenPLi 9.0, perform basic setup (network etc.) and activate multiboot
  This would be my recovery image, correct?
• Flash my OpenPLi 8.3 backup into one slot
  Is there an easy way to do that? I could not select the latest backup image directly. I had to rename it to a specific name format and copy it to the images folder on my hdd.
• Flash OpenPLi 9.0 and OpenATV to Slot 2 and 3

But after every slot is configured and running how would I backup each slot completely?

How to restore a backup to a slot?

 

I found this post;

https://forums.openp...p/#entry1626943

 

But if the box wouldn't boot, how do I recover or restore my slot backups?

Flash OpenPLi 9, basic setup, activate multiboot and then how to restore the slots correctly?

 

In general:

What would be the best and hopefully easiest backup/restore/recovery strategy of a multiboot setup?

 

[WanWizard]

That is a known issue, and present in all VU+ 4K images, it has only been adressed in the latest images a few months ago, and in OpenPLi develop (fix will be in 9.1-release).

 

For details, see https://github.com/o...core/issues/877

 

The problem is indeed that the image itself isn't multiboot aware, so if there is a kernel update in the updates, that update will overwrite the kexec multiboot kernel of the box.

 

See https://wiki.openpli...er_an_update.3F for more details, and a howto on how to fix it if it happens.

 

I haven't seen a box that doesn't boot anymore after this happened, obviously, if it doesn't boot anymore, you're out of luck, and USB flashing is the only remaining option.

 

True multiboot boxes have multiboot support in the bootloader, separate partitions for the kernel of each slot, and a recovery partition that can be booted by the bootloader. VU+ doesn't have any of that.

[WanWizard]

For the rest of your questions:

 

Yes, the first image flashed, from USB, will be the slot 0 image, and should be treated as the recovery image. Which means flash, configure network (so you can access it remotely if needed), and nothing else.

 

I never use (and have never used) backupsuite. I never had a need for it. I only use the autobackup feature.

[littlesat]

Actually using backupsuite nowadays has not a real added vallue…usually normal backup/restore is sufficiant for openpli. I have no idea if the same is true for other images.

Edited by littlesat, 28 September 2024 - 13:15.

[Qu@rk]

Thanks for the immediate reply.

 

Kexec:

After posting my questions I have found the updated wiki. Thanks, very helpful.

I have read the github kexec discussion and in principle I have understood the problem and the possible solution in future builds and why it fails with current/older builds. I will have to think about a procedure to backup my slots.

 

Additional to the "tar method":

Would it be possible to use backupsuite within each slot?

The created backup image would contain the kexec kernel, right?

Would it be possible to restore an backupsuite image created like that within the multiboot menu of the recovery image? Or will this fail because of the kexec kernel?

 

Autobackup on OpenPLi 8.3:

I have never used autobackup/autoinstall to restore an installation. I made my own settings backups manually.

I prefer a full image backup. If something goes terribly wrong the box is in a working state exactly as before within minutes.

But I have read the autobackup wiki and understand your point. I will use it as an additional safety net.

 

On my OpenPLi 8.3 I changed the autobackup settings (start time 03:00, save previous backup=ON, create autoinstall=ON). If I leave the menu with the green button and enter the autobackup settings again the setting "save previous backup" is OFF again.

 

The box did not start and performed a backup this morning at 03:00 and the setting "save previous backup" was off again.

Manual backups work.

 

Would the box start from deep standby and perform the autobackup?

[twol]

Actually using backupsuite nowadays has not a real added vallue…usually normal backup/restore is sufficiant for openpli. I have no idea if the same is true for other images.

@qu@rk,  @littelsat flashing an image and restoring the settings backup to recreate the normal working environment  is true for images such as  openvix, openbh and openatv, as well as openpli.
Alternatively to reduce slot restoration, the originators of Vu+ multiboot specifically also supported usb images, so that if slot 0 is replaced (for whatever reason) usb images are available instantly by installation of the STARTUP files for those images.
Slot 0 can also be online flashed without loss of the other emmc slot images.

[WanWizard]

There is only one possible reasons for wanting to make a full backup with backupsuite: you have plugins for which no ipk exists (for example plugin developers who develop on the box).

 

In all other circumstances, a flash + autobackup is better and faster. I consider myself a "power user", and I have never ever had the need for a full backup.

 

I can't comment on the situation for non-OpenPLi images.

 

And OpenPLi doesn't support slots on USB.

[littlesat]

Even then you do not need that… just put that ipk in the folder as ipk where the backup files are and they also are installed. At least we do…

Edited by littlesat, 29 September 2024 - 14:10.

[WanWizard]

I wrote "when no IPK exists"...

 

For example when you are developing a new plugin and you do that directly on the box, without git (so you would lose your work after a flash).