[VU+ Duo2] backup crash

twol · May 10, 2022

miguel57 said:
finally i managed to charge through usb the opnevix VI and i found on my HDD a debug that i have tried to put here but i read the following message "The text that you have entered is too long (101722 characters). Please shorten it to 22000 characters long". How can i send to tou this debug?.

Send it as an attachment… go advanced (see bottom right) andthen you can add attachments under additional options… manage attachments

miguel57 · May 11, 2022

twol said:
Send it as an attachment… go advanced (see bottom right) andthen you can add attachments under additional options… manage attachments

i have 2 debugsView attachment Enigma2_debug_2022-05-11_06-05-56.log View attachment Enigma2_debug_2022-04-02_20-26-59.log.

Huevos · May 11, 2022

What am I looking at? This is a log of running CrossEPG 6 weeks ago.

miguel57 · May 11, 2022

Huevos said:
What am I looking at? This is a log of running CrossEPG 6 weeks ago.

Those are the only reports that i have on my HDD.

Joe_90 · May 11, 2022

miguel57 said:
Those are the only reports that i have on my HDD.

The debug logs are in /home/logs/ by default, unless you changed the location when you set up debugging in the menu.

miguel57 · May 11, 2022

Joe_90 said:
The debug logs are in /home/logs/ by default, unless you changed the location when you set up debugging in the menu.

That is right. So i collected the debug from home/logs, and i had, i do not know why, two "debugs" on my HDD, related to EPG. The problem is that when the vu duo2 collapse i have to reflash it again through usb, so there is not any debug report about the problem, because the receiver is starting again from zero. So, ¿How can i solve the problem?. Is like a snake biting its own tail (La pescadilla que se muerde la cola).

Joe_90 · May 11, 2022

@twol suggested that you change the debug log location to hdd so that there would be a debug log available if you had to re-flash subsequently. So, once you manage to flash the box, go into debug log settings and change it to hdd and then reboot so that subsequent logs are on disk.

miguel57 · May 11, 2022

Joe_90 said:
@twol suggested that you change the debug log location to hdd so that there would be a debug log available if you had to re-flash subsequently. So, once you manage to flash the box, go into debug log settings and change it to hdd and then reboot so that subsequent logs are on disk.

I did it following your advice and i have several debugs,some of them repeated. Hee it goes...............

Joe_90 · May 11, 2022

miguel57 said:
I did it following your advice and i have several debugs,some of them repeated. Hee it goes...............

Em - I am a bit confused. It looks like you are restoring an old image

Code:

<   193.5465> [Console] command: /usr/bin/ofgwrite -r -k '/media/hdd/imagebackups/imagerestore/vuplus/duo2'

after you have installed the 6.1.004 version?
Maybe just flash the latest version and do not restore anything. Just do some basic setups and perhaps then try to restore a backup (not an image).

miguel57 · May 11, 2022

Joe_90 said:
Em - I am a bit confused. It looks like you are restoring an old image

Code:

< 193.5465> [Console] command: /usr/bin/ofgwrite -r -k '/media/hdd/imagebackups/imagerestore/vuplus/duo2'

after you have installed the 6.1.004 version?
Maybe just flash the latest version and do not restore anything. Just do some basic setups and perhaps then try to restore a backup (not an image).

I have restored 6.1.004. So i understand that you suggest to flash again 6.1.004, make a new backup and restore it?

Joe_90 · May 11, 2022

miguel57 said:
I have restored 6.1.004. So i understand that you suggest to flash again 6.1.004, make a new backup and restore it?

No - it looks like you are overwriting the install with an old image (not a backup). Backups are just settings and possibly plugin restores. What you seem to be doing is a full image restore using ofgwrite. Flash 6.1.004 and do a manual setup and see how you get on.

miguel57 · May 12, 2022

What i do is firstly is to flash through usb the openvix 6, then my vu duo ask me about restore settings and plugins that i have in my HDD. I have to say that the backup i have is from the old openvix 5 and that all these problems have apperead after the installation of the new openvix 6, before openvix 6, i mean two weeks ago with openvix 5 i do not have any problem at all doing whatever i did, so i suposse something does not match betwenn openvix 5 and 6. Now you suggest to flash openvix 6 and manually set my 5 dishes on it and all other plugins i have. A very hard job

twol · May 12, 2022

miguel57 said:
What i do is firstly is to flash through usb the openvix 6, then my vu duo ask me about restore settings and plugins that i have in my HDD. I have to say that the backup i have is from the old openvix 5 and that all these problems have apperead after the installation of the new openvix 6, before openvix 6, i mean two weeks ago with openvix 5 i do not have any problem at all doing whatever i did, so i suposse something does not match betwenn openvix 5 and 6. Now you suggest to flash openvix 6 and manually set my 5 dishes on it and all other plugins i have. A very hard job

After a clean install, you can extract your sat dish settings from the settings backup and then restore them in the /etc/enigma2/settings file … not that complex and just a cut and paste is needed.

miguel57 · May 12, 2022

twol said:
After a clean install, you can extract your sat dish settings from the settings backup and then restore them in the /etc/enigma2/settings file … not that complex and just a cut and paste is needed.

I will try this afternoon, but is there a "settings" file in etc/enigma2 or does it have another name?

twol · May 12, 2022

miguel57 said:
I will try this afternoon, but is there a "settings" file in etc/enigma2 or does it have another name?

Its called settings

miguel57 · May 12, 2022

twol said:
Its called settings

I did it but i can not ftp to openvix using dcc and name: root and password openvix it said enigma2 not detected functionality limited

twol · May 12, 2022

miguel57 said:
I did it but i can not ftp to openvix using dcc and name: root and password openvix it said enigma2 not detected functionality limited

There were issues with DCC.
You can set password if you haven’t already via a telnet session e.g. via putty. login root then enter passwd (it is passwd!) and enter password 2x
Then you just use filezilla, login root and your password

miguel57 · May 13, 2022

After doing everything the problem remains the same. I backup the new image and when i tried tor reinstall through image manager apears the new logo once and again without installing anything.

Huevos · May 13, 2022

Haz una foto de este logo que ves.

Intenta encargar OpenViX con un pincho USB.

miguel57 · May 13, 2022

Siempre cargo openvix con un pincho usb y el logo es el nuevo logo gris de openvix 6. Ademas ayer meti manualmente CCCam 2.3.0 y CCcam.config con mi proveedor que en el openvix 5 me salia conectado cuando chequeaaba con el boton verde y ahora con esta openvix me dice cuando chequeo su estado que no puede conectar, otro problema mas que antes no tenia. Por cierto ¿estas per Xixona?.

[VU+ Duo2] backup crash

Moderator

New member

ViX Beta Tester

New member

Moderator

New member

Moderator

New member

Attachments

Moderator

New member

Moderator

New member

Moderator

New member

Moderator

New member

Moderator

New member

ViX Beta Tester

New member

OpenViX Feeds Status