Full Backup of the Recovery slot

N

NotLikeSomeone

Active member
I had to reflash the box three or more times from scratch because, for some reasons, also the Recovery Image got corrupted and it was not possible to boot not even by the RECOVERY_IMAGE pendrive.
This caused, of course, loosing the who multiboot structure.
This means the need of reflashing the box, choosing of multiboot install, long wait for the new reboot and preparation of multiboot itself and then setting again the network, password and all the indispensable things for the Recovery image.
Only at that point I can reflash the slots from the FullBackups...

I was wondering if rebooting in the Recovery image and performing a FullBackup from the GUI, would produce a backup that, in case you have again a corrupt image, put in the condition of reflashing the box having at least the basic settings and also the multiboot structure (of course, with empty slots but ready to be reflashed by the image itself).
Would it be so? It seems too easy to be working...
 
Actually, the last time it happened some months ago: so, I can't remember what had happened immediately before. But, I was thinking back to the situation in itself, trying to find a way not to go again through all the troubles and the steps needed to restore everything, recovery image and slots.
I use, mainly, an Ultimo4K.
It would be so useful if the image offered a sort of "SUPER FullBackup", meaning a GUI command or a script to prepare a TOTAL backup (to be put in a pendrive) with everything a user has got at the moment: multiboot structure AND slots.

Alternatively, at least, it'd be already a lot time saving, if we had a way of saving the multiboot structure and the RECOVERY image: this would allow the users to flash this scenario and afterwards they would be able to restore previous slots by usual Full Backups.
 
Boot into recovery image.

Download the latest image in Image manager and go to flash it, it will ask if you want to overwrite the recovery image or flash a slot.

Select the recovery image and it should ask you if you want to backup the images in slots 1,2,3 and warns you that it could take a while to do so.
 
Meanwhile, as you use the conditional "it should ask", I simpy tried to perform this Recovery image FullBackup getting this error:

Image manager
Error: [Failure instance: Traceback: <class AttributeError>: None Type' object has
no attribute 'backupstop'
/usr/lib/python3.13/site-packages/twisted/python/threadpool.py:269:inContext
/usr/lib/python3.13/site-packages/twisted/python/threadpool.py:285:<lambda>
/usr/lib/python3.13/site-packages/twisted/python/context.py:117:callWithContext
/usr/lib/python3.13/site-packages/twisted/python/context.py:82:callWithContext
/usr/lib/enigma2/python/Plugins/SystemPlugins/OBH/lmageManager.py:1571:BackupComplete

but the Slot0 still contains 5.6.008.In theiry it should make no difference for my wish, but I'm asking you if it does.
 
You can try the attached plugin and see what it does. It was designed for a wide range of uses and supports extra slots. But I have no clue if it will work on Vu+. The result if successful would be a zipped image. I just don't know how it will react with the slots on Vu+. I would assume it should read them ok....
 

Attachments

It seems not compatible: it says Multiboot is not installed, but it is. Also, it seems to backup only slots (for which task I already prepared a script which backups and prepares a .zip as the FullBackup, as of the Image Manager task but with the chance to run in background).
I was trying to understand if there's a way to save the Multiboot general structure, even without saving the content of the slots, in order not to go through the whole process in case on fail boot of the Recovery image.
 
You must log in or register to reply here.
Back
Top