14 replies to this topic

[колбаскин]

I have not seen a worse release.

openpli-8.0-release-vuultimo4k-20210222_usb

Did a clean install from USB. The receiver simply does not want to be loaded and goes into greenery.

7 reboots to the green screen without labels, after 3 reboots with labels and boots.
Scanned the channels. Reboot and again problems with the start.
HDD was able to format only via ssh. The team just hung out of the menu for a day.

Now, after the reboot, the antenna settings have disappeared.

Put the image of ATV, no problem.

Attached Files

•  enigma2_crash_14.log   26.34KB   9 downloads
•  enigma2_crash_25.log   1.17KB   5 downloads
•  enigma2_crash_1614157624.log   22.49KB   6 downloads

Edited by колбаскин, 25 February 2021 - 08:22.

[колбаскин]

Install openpli-7.3-release-vuultimo4k-20210223_usb
These are all the logs when the receiver is rebooted.

I did not configure anything except the network.

The internal HDD is empty.

Only logs.

It's all in just one reboot

Attached Files

•  enigma2_crash_14.log   26.12KB   3 downloads
•  enigma2_crash_26.log   1.12KB   1 downloads
•  enigma2_crash_37.log   934bytes   2 downloads
•  enigma2_crash_49.log   934bytes   4 downloads
•  enigma2_crash_65.log   1.23KB   7 downloads

Edited by колбаскин, 25 February 2021 - 09:01.

[WanWizard]

Enigma crashes in low-level C code during startup. Corrupt EPG data file perhaps, or a corrupt channel list?

[колбаскин]

Enigma crashes in low-level C code during startup. Corrupt EPG data file perhaps, or a corrupt channel list?

I'm doing a clean install and the receiver won't boot anymore. I have not installed or configured anything.

e2fsck -nf /dev/mmcblk0p4
e2fsck 1.45.3 (14-Jul-2019)
Warning!  /dev/mmcblk0p4 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (850708, counted=850680).
Fix? no

Free inodes count wrong (223946, counted=223948).
Fix? no

/dev/mmcblk0p4: 12694/236640 files (4.7% non-contiguous), 94444/945152 blocks

Is there a memory problem?

Edited by колбаскин, 25 February 2021 - 16:33.

[WanWizard]

This is the internal eMMC card (which is used these days instead of flash). I hope that is not failing, because afaik it can't be replaced.

 

You also have to be careful, one of the partitions contains the security software, if you lose that one, the box is bricked.

 

Perhaps @betacentauri can comment, this is beyond my expertise...

[mimisiku]

No, probably a defective HDD.... Physically disconnect it an try a clean flash from USB
Add an enpty file 'mkpart.update' on your USB stick before flashing...
If flashing / booting fails:: End of the Line....

Edited by mimisiku, 25 February 2021 - 16:54.

[колбаскин]

What else can I do?

[колбаскин]

No, probably a defective HDD.... Physically disconnect it an try a clean flash from USB
Add an enpty file 'mkpart.update' on your USB stick before flashing...
If flashing / booting fails:: End of the Line....

I tried unplugging the HDD, it didn't help.
Added file mkpart.update

init 4
ENIGMA_DEBUG_LVL=6 enigma2 2>&1 | tee /hdd/enigma2.log

 

Attached Files

•  msg-40867-0-60818200-1614261739.jpg   19.43KB   2 downloads
•  enigma2.log   9.44KB   8 downloads

[mimisiku]

I see 'nomkpart.update! Instead of 'mkpart.update'... Is this correct?
If you already tried with 'mkpart.update' and the box still won't boot try the official firmware from 'code.vuplus.com'. If that still doesn't boot: bye bye box...

[betacentauri]

Don't do a filesystem check while partition is mounted. I know it's rootfs and it's difficult to unmount it, but still don't do it.

 

As mimisiku wrote. Try with mkpart.update file. For that put an empty file with filename mkpart.update into the /vuplus/ultimo4k/ folder on your USB stick and flash via USB stick again.

[колбаскин]

The receiver sometimes boots up.

vuplus image has become. But also writes crashlogs

Install ATV image. It worked, but after another reboot it went into a cyclic boot. It looks like it's about flash memory.

[  319.863898] UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2)
[  319.918954] UDF-fs: warning (device mmcblk0p1): udf_fill_super: No partition found (2)
[  319.959037] UDF-fs: warning (device mmcblk0p3): udf_fill_super: No partition found (2)
[  320.012707] UDF-fs: warning (device mmcblk0p3): udf_fill_super: No partition found (2)

 

[mimisiku]

Your eMMC is defective.

[Aliraza63]

I Had faced this issue with  my giant what I did I share it for helping purpose .

1. use 4gb/8gb  original Kingston/Sandisk  usb ( not cheap generic chinese )

2. remove all other attached hdd /usb

3. unzip this file loader 

4. install it & reboot 

5. install original image & check

6. Now u can install any pli verion 

It will work flawlessly now  

 

 vuplus-image-vuultimo4k-bolt-v1.21-20171218_usb.zip   539.47KB   10 downloads

[колбаскин]

Thanks. But didn't help.

Installed vuplus-image-vuultimo4k-bolt-v1.21-20171218_usb

Installed vuplus-image-vuultimo4k-20210223154557_usb

installed openpli-8.0-release-vuultimo4k-20210222_usb

 

When choosing a language, I caught a green

The receiver is working, but several green screens when i make reboot.

[mimisiku]

I am afraid the eMMC is simply defective (at important location).. If still in warranty, send it in. A new mainboard will cost €250 if you wish to have the unit working again...