What's new
By:
Filters

Satellite Box crashing after reboot

imzy

imzy

Member
Hello Folks,

Hope you are all well.

Updated my Zgemma H7S box to the latest OpenVix firmware 6.2.001

Update was successfully done, everything running normal.

When I rebooted box and it came on as usual then it went into crash log screen.

Now the box just keeps rebooting and crash log screen appears, consistently.

any way to fix this?

Any guidance and support will be much appreciated.
 
ian1095 said:
No one can help you until you post the crash log
Click to expand...
Haha, My bad, how do I retrieve this?

I just removed the USB from the box and it did 1 round of the crash log screen boot and now it seems to be running okay.

but good to know where to find the crash log and submit here.

Thanks Ian for pointing out.
 
imzy said:
Haha, My bad, how do I retrieve this?

I just removed the USB from the box and it did 1 round of the crash log screen boot and now it seems to be running okay.

but good to know where to find the crash log and submit here.

Thanks Ian for pointing out.
Click to expand...
FileZilla into the box, crash logs are in home/root/logs
 
imzy said:
Yes, I think the usb which was in gone faulty for some reason.

after update seems fine but bit slow.
Click to expand...
Did you have a swap file running on the USB ? If so that may of slowed it down.

I personally never update an image this way, i just back up my settings flash the latest image and restore the settings.
 
Hello Guys,

Can someone please help me again.

box keeps crashing after boot. Attached is the crash boot log.
 
Quite a bit relating to storage:

< 23.1006> 10:11:24.2178 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1009> 10:11:24.2182 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1015> 10:11:24.2187 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1017> 10:11:24.2189 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1021> 10:11:24.2194 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1023> 10:11:24.2196 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)

<4>[ 1.940599] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<6>[ 2.127218] Adding 262140k swap on /dev/mmcblk0p7. Priority:-1 extents:1 across:262140k SS
<4>[ 2.690782] h7_1: module_layout: kernel tainted.
<4>[ 2.695437] Disabling lock debugging due to kernel taint
<4>[ 2.700775] h7_1: loading out-of-tree module taints kernel.

<3>[ 12.474893] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0
<3>[ 12.502605] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0


Just power off and remove the storage device and see if it will boot without it.
 
pabloescaban said:
Looks like a skin problem, the first twenty or so entries were missing skin components.
Try changing the skin to a different one and see if it's any better
Click to expand...
Hello Sir, I will give this a go, however when the box reboots it just goes in to crash mode.

after a nightmare morning I started repeatedly pressing the exit button on the remote before crash screen appeared after boot load and surprisingly it didn't crash.

But I know if I reboot box again, it will go in to crash log screen and so on.
 
Willo3092 said:
Quite a bit relating to storage:

< 23.1006> 10:11:24.2178 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1009> 10:11:24.2182 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1015> 10:11:24.2187 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1017> 10:11:24.2189 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1021> 10:11:24.2194 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)
< 23.1023> 10:11:24.2196 [eDVBServicePlay] timeshift not enough diskspace for timeshift! (less than 1GB)

<4>[ 1.940599] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<6>[ 2.127218] Adding 262140k swap on /dev/mmcblk0p7. Priority:-1 extents:1 across:262140k SS
<4>[ 2.690782] h7_1: module_layout: kernel tainted.
<4>[ 2.695437] Disabling lock debugging due to kernel taint
<4>[ 2.700775] h7_1: loading out-of-tree module taints kernel.

<3>[ 12.474893] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0
<3>[ 12.502605] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0


Just power off and remove the storage device and see if it will boot without it.
Click to expand...
This was the first things I did. was still crashing after.

I got the new 6.2.005 build
 
You must log in or register to reply here.
Back
Top