1309 replies to this topic

[lincsat]

I'm only a novice when it comes to scripting and am using ATV rather than PLi currently. The latest files on the Git do work but still give error messages on building an image. It seems my busybox doesn't like the ls -e argument, so I've just taken them out. It gives another error towards the end, seems it doesn't like $ inside and outside brackets, like for example

SPEED=$(( $TOTALSIZE/$DIFF ))

So I've just taken the $ out from inside the brackets and it seems to complete without error.

[sat-mar]

Hi I have zgemma program h7s openpli 7.0 I can not make a full copy of the backupsuite system, it is not full and there are tar: ./ run / msg / 1783 errors: socket ignored

[Erik Slagter]

That's no error.

[Stosun]

It does me on Pli 7 to 6.2 it did not, but if it is not a mistake? So it's okay.

Attached Files

•  1_0_19_1F41_CA1_3_EB0000_0_0_0_20190124170530.jpg   143.88KB   4 downloads

[betacentauri]

Just ignore the "socket ignored". It's more a info than a warning and no error at all.

[sat-mar]

but it does not do a full image of only 70mb

[betacentauri]

Why? Normal image size is 60-65 MB.

[sat-mar]

the full image is 70 MB and it is tar.gz and it should be disk.img

[betacentauri]

Backup Suite creates no disk.img. The tar.bz2 can be flashed with the backup suite or with the in enigma2 included flash image.

[sat-mar]

and how to make a painting on a pendriva img picture

[betacentauri]

I guess you use google translate or similar. The translation is quite bad.

You can create a backup with the backup suite. In case the box don’t boot, you can flash a normal image (downloaded here) and afterwards flash the backup with the built in “Flash image”.

[sat-mar]

Good morning

I intend to make my own copy of the system so that I can later send it from the pendrive to another decoder

[sat-mar]

 

Good morning

I intend to make my own copy of the system so that I can later send it from the pendrive to another decoder disk.img

 

[gerard0610]

Has someone manage to restore a backup (by BackupSuite in OpenPli 7) in an Edison OS Mio 4K?
 

After power ON I see the message "Press and hold down the OK in 10 seconds".
After this done the box is rebooting as normal but not putting the backup in the box.
 

Making an backup is successfully.

I see on the USB stick in the directory "osmio4k":

- BackupSuite.log
- imageversion
- kernel1.bin
- rootfs.tar.bz2

[betacentauri]

As far as I know you first need to flash a normal image. When this is running you can flash the backup via builtin “online flash” or via backupsuite.

[gerard0610]

As far as I know you first need to flash a normal image. When this is running you can flash the backup via builtin “online flash” or via backupsuite.

I have a Edison OSMio 4k with the OpenPli 7.0 image.

 

After the installation via USB everything works well in the first trial.

Then i have installed BackupSuite via Openpli – extensions.

I format a old small size (1GB) usb stick FAT32. After this i put an empty file with the name ‘backupstick.txt’.

After this i have made a backup on my USB stick. This works well.

I can put back this backup via the menu from BackupSuite (bleu button) by selecting the directory ‘osmio4k’and then selecting overwrite.
Then the backup is doing his job :-)
 

But with my other satellite receiver VU+Ultimo 4k is it also possible to put the backup back as follows:
- power of from satellite receiver
- put the USB stick in the receiver (and all other USB connectors must be empty)
- power ON
- then I see in the display that I need to press the OK button to flash
- after I have pressed the OK button the backup is flashed in the receiver
 

However this procedure is not working in my the Edison OSMio 4k.
*) also not in case i put an empty file with the name ‘noforce’ put in the root of the USB.

 

Question: I someone able to flash the backup on the Edisom OSMio 4k via the power off and then power On method (after pres the OK button?

[betacentauri]

On some boxes it’s not possible to flash the backup made by backup suite via usb pen power off/on method. And os mio4k is one of them.

[gerard0610]

On some boxes it’s not possible to flash the backup made by backup suite via usb pen power off/on method. And os mio4k is one of them.

Thank you for this feedback.
 

Then I will use the reverse method via the menu and not via usb pen power. No problem.

Further, I am very happy with de BackupSuite.
Many thanks for the developer(s).

[foxbob]

Creating a backup passes without errors.

*** THIS BACKUP IS CREATED WITH THE PLUGIN BACKUPSUITE ***

***** ********************************************* ******

 

Plugin version     = git443+456c954

Back-up media      = /hdd

Filesystem                Size      Used Available Use% Mounted on

/dev/sdb1               915.9G    618.6G    250.8G  71% /media/sdb1

 

Back-up = 2019.04.14_11:45

Version = openpli develop 

Flashed = 2019.04.13_18:36

Updated = 2019.04.14_08:15

Drivers = et-dvb-modules-kodi-et1x000 - 4.1.37+20170927-r2

Enigma2 = 2019-04-12-develop

 

 

Working directory  = /hdd/bi

Not Open Vision, Open PLi maybe?

Destination        = /hdd/fullbackup_et1x000/20190414_1145/et1x000

 

RECEIVER = GI ET11000 

MKUBIFS_ARGS = 

UBINIZE_ARGS = 

KERNEL размер резервной копии:   8192 KB

ROOTFS размер резервной копии: 346120 KB

=TOTAL размер резервной копии: 354312 KB (= 346 MB)

Пожалуйста, будьте терпеливы, создание резервной копии началось, это займёт около: 7.52 минут

 

*** FIRST SOME HOUSEKEEPING ***

Remove directory   = /hdd/bi

Recreate directory = /hdd/bi

Create directory   = /tmp/bi/root

 

Создаём: kerneldump

Kernel resides on /dev/mmcblk0p3

Создаём: root.ubifs

Removed directory  = /hdd/fullbackup_et1x000/20190414_1145/et1x000

Created directory  = /hdd/fullbackup_et1x000/20190414_1145/et1x000

 

USB прошивка создана в: /hdd/fullbackup_et1x000/20190414_1145/et1x000

Содержание папки:

      68 Apr 14 11:48 noforce

     198 Apr 14 11:48 imageversion

   12.0M Apr 14 11:45 kernel.bin

  116.2M Apr 14 11:46 rootfs.tar.bz2

 

No additional USB-stick found to copy an extra backup

Время, необходимое для этой процедуры: 3.15 минут

 

Резервная копия сделана со скоростью: 673КБ в секунду

 

Then I want to restore the firmware and nothing happens.I choose to simulate - there are no errors on the screen.I choose a flash or kernel, it starts ofgwrite shows that the record goes and nothing changes.

 

[SKIN] Parsing embedded skin <embedded-in-'FlashImageConfig'>

[Skin] Processing screen: <embedded-in-'FlashImageConfig'>

[SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>

[Skin] Processing screen: <embedded-in-'SimpleSummary'>

[eEPGCache] nownext finished(1555234024)

[ActionMap] Keymap 'SetupActions' -> Action = 'ok'

[ActionMap] Keymap 'SetupActions' -> Action = 'ok'

[ActionMap] Keymap 'SetupActions' -> Action = 'ok'

[ActionMap] Keymap 'SetupActions' -> Action = 'ok'

[ActionMap] Keymap 'SetupActions' -> Unknown action 'save'! (Typo in keymap?)

[ActionMap] Keymap 'ColorActions' -> Action = 'green'

[Skin] Processing screen: MessageBox

warning, skin is missing element WarningPixmap in <class 'Screens.MessageBox.MessageBox'>(Warning!

Use at your own risk! Make always a backup before use!

Don't use it if you use multiple ubi volumes in ubi layer!

)

warning, skin is missing element autoresize in <class 'Screens.MessageBox.MessageBox'>(Warning!

Use at your own risk! Make always a backup before use!

Don't use it if you use multiple ubi volumes in ubi layer!

)

[SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>

[Skin] Processing screen: <embedded-in-'SimpleSummary'>

[eEPGCache] schedule finished(1555234033)

[eEPGCache] stop caching events(1555234033)

[eEPGCache] next update in 60 min

[ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'

[Skin] Processing screen: MessageBoxSimple

warning, skin is missing element WarningPixmap in <class 'Screens.MessageBox.MessageBox'>(Select parameter for start flash!

For flashing your receiver files are needed:

oe_kernel.bin, rootfs.tar.bz2

The found files:  rootfs.tar.bz2 (maybe ok)  kernel.bin (maybe error))

[SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>

[Skin] Processing screen: <embedded-in-'SimpleSummary'>

[ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'

[Skin] Processing screen: Console

[Skin] Attribute not implemented: scrollbarMode value: showOnDemand

Console: executing in run 0  the command: echo -e '

Show only found image and mtd partitions.

'

[eConsoleAppContainer] Starting /bin/sh

 

Attached Files

•  1_0_16_71C_12_70_1680000_0_0_0_20190414122915.jpg   48.34KB   7 downloads
•  1_0_16_71C_12_70_1680000_0_0_0_20190414122743.jpg   107.88KB   5 downloads

[nafaal]

Hello! Have the following error with my Mutant HD60: (with OpenPLI 7.0)

 

 

 

Full back-up direct to USB -> /media/usb (59.3G, available 57.6G)


MUTANT HD60 BACK-UP TOOL, FOR MAKING A COMPLETE BACK-UP


Version: git446


Some information about the task
KERNEL size to be backed up: 8192 KB
ROOTFS size to be backed up: 260216 KB
=TOTAL size to be backed up: 268408 KB (= 262 MB)


Please be patient, a backup will now be made, this will take about: 5.57 minutes


Create: kerneldump
cat: can't open '/sys/firmware/devicetree/base/chosen/kerneldev': No such file or directory
.bin = STARTUP_
Create: root.ubifstar: ./run/msg.sock/1548: socket ignored
tar: ./run/msg.sock/1879: socket ignored
tar: ./run/msg.sock/2553: socket ignored
tar: ./run/msg.sock/1707: socket ignored
tar: ./run/msg.sock/2770: socket ignored
tar: ./run/msg.sock/2412: socket ignored
tar: ./run/msg.sock/1545: socket ignored
tar: ./run/msg.sock/2772: socket ignored
tar: ./run/msg.sock/2660: socket ignored
tar: ./run/msg.sock/2549: socket ignored
tar: ./run/msg.sock/1550: socket ignored
tar: ./run/msg.sock/2775: socket ignored
tar: ./run/msg.sock/2345: socket ignored
tar: ./run/msg.sock/2408: socket ignored
tar: ./run/msg.sock/2552: socket ignored
tar: ./run/msg.sock/1876: socket ignored
tar: ./run/msg.sock/2342: socket ignored
tar: ./run/msg.sock/1705: socket ignored
tar: ./run/msg.sock/2555: socket ignored
tar: ./run/msg.sock/2661: socket ignored
tar: ./run/msg.sock/2409: socket ignored
tar: ./run/msg.sock/2406: socket ignored
tar: ./run/msg.sock/2658: socket ignored
tar: ./run/msg.sock/2410: socket ignored
tar: ./run/msg.sock/2551: socket ignored
tar: ./run/msg.sock/1706: socket ignored
tar: ./run/msg.sock/1547: socket ignored
tar: ./run/msg.sock/1877: socket ignored
tar: ./run/msg.sock/2343: socket ignored
tar: ./run/msg.sock/2771: socket ignored
tar: ./run/msg.sock/2662: socket ignored
tar: ./run/msg.sock/1708: socket ignored
tar: ./run/msg.sock/2773: socket ignored
tar: ./run/msg.sock/1703: socket ignored
tar: ./run/msg.sock/2769: socket ignored
tar: ./run/msg.sock/2664: socket ignored
mv: can't rename '/media/usb/bi/.bin': No such file or directory


Image creation FAILED!

 

Is there any solution, yet? Regards.