Jump to content


колбаскин

Member Since 7 Feb 2013
Offline Last Active 06 Mar 2021 09:55
-----

Posts I've Made

In Topic: VU+ Ultimo 4K crash OpenPLI 8.0

26 February 2021 - 14:44

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.


In Topic: VU+ Ultimo 4K crash OpenPLI 8.0

25 February 2021 - 18:37

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)

 


In Topic: VU+ Ultimo 4K crash OpenPLI 8.0

25 February 2021 - 17:03

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

 


In Topic: VU+ Ultimo 4K crash OpenPLI 8.0

25 February 2021 - 16:59

What else can I do?


In Topic: VU+ Ultimo 4K crash OpenPLI 8.0

25 February 2021 - 16:32

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?