VU+ Solo 2 - VIX image Hades / VIX 3.2 - Crashing

[Davitat]

Maybe not a cam issue so. However cccam221 isn't suitable for current images on multi tuner boxes.

I just have one tuner (Solo 2).
In fact it seems like the crash is corrupting the flash memory and the only thing you can do after that is to flash it again.
But more strangely, after having had this crash one of the first things I do was to go back to backuped images of prior versions that worked (I tried back to Apollo 166), and this versions working in the past, now crashed (exactly same 'big crash')!

Is like something get changed and 'memorized' or an hardware problem.
So I flashed the legacy Vu+ image and had no crashes (but I cant be sure because they are random and can come after more than ten hours working ok).
Then I googled and find this thread with exactly the same error that make me think it wasn't an hardware problem.

 

[abu baniaz]

The Solo 2 is a twin tuner receiver.

 

[Davitat]

Maybe not a cam issue so. However cccam221 isn't suitable for current images on multi tuner boxes.

Ah, and of course, nothing plugged into the usb ports and I reformatted my hdd to be sure that nothing could 'hide' there.
Is there some areas of internal flash (low level drivers or so) that can be changed and not updated by the images? (try to understand where a change could had been made ans memorized).

 

[Davitat]

Excuse me, you are right. But I dont think it has something to do with softcams because as I've explained I had this crash also without any cam.

 

[abu baniaz]

Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

Purely speculation here, do you get the crash without the USB tuner?

 

[Davitat]

Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

Purely speculation here, do you get the crash without the USB tuner?

Hi,
Sorry but impossible to have access to the box after the crash so impossible to get logs (look please to the #6 post of this thread by scar0x with pictures).
And yes I got this crash without any usb tuner (dvb-t) connected, nor any usb-dvb-xxx driver installed.

 

[Davitat]

Are you able to get a crash log from /home/root/logs/ ? If so, please upload as an attachment.

Purely speculation here, do you get the crash without the USB tuner?

How can I redirect the logs to the hdd in order to preserve them?

 

[abu baniaz]

In the logs settings.

Menu > Setup > System > Logs > Settings > Logs location

 

[Davitat]

In the logs settings.

Menu > Setup > System > Logs > Settings > Logs location

Oooops! Excuse me, it was in settings... I thought I had to create some sort of link. This OpenVix is fantastic, he has everything we can need
Ok, I'll make some tests and report the logs here.

Thank you very much.

 

[Davitat]

Bad news...
I've changed Logs Location to hdd and also activated 'debug mode'.

I had 2 crashes with v.3.2.013 but every time the '/media/hdd/logs' was empty!
First time I thought that perhaps for some reason, software have had no time to write log data before the program hanged, but it'worse... At the second crash I had some debug log files into '/media/hdd/logs' before the crash and they where wiped after the crash. Blank directory, nothing.

Crazy.
If not because the creator of this thread reported exactly the same issue, I'll would think that this is an hardware random problem.
Any idea?

 

[judge]

Bad news...
I've changed Logs Location to hdd and also activated 'debug mode'.

I had 2 crashes with v.3.2.013 but every time the '/media/hdd/logs' was empty!
First time I thought that perhaps for some reason, software have had no time to write log data before the program hanged, but it'worse... At the second crash I had some debug log files into '/media/hdd/logs' before the crash and they where wiped after the crash. Blank directory, nothing.

Crazy.
If not because the creator of this thread reported exactly the same issue, I'll would think that this is an hardware random problem.
Any idea?

If /media/hdd/logs/ is mounted properly & crash logs are saved there properly, there is nothing in E2 that will delete them.
Maybe a flakey plugin or a virus on your network?

 

[Rob van der Does]

Maybe it's easier to use an USB-stick for the logs. That can easily be disconnected from the box and connected to a PC to retrieve any debug & crash logs.

 

[Davitat]

If /media/hdd/logs/ is mounted properly & crash logs are saved there properly, there is nothing in E2 that will delete them.
Maybe a flakey plugin or a virus on your network?

I also thought of a virus. My network is a small home network with 1 desktop, 1 laptop with W10 and 1 Android smartphone but also 2 ip cams and one NVR (Network Video Recorder for the cams) on witch, you make me think of, I updated the firmware (based Linux box) this lasts weeks from a non very trusted source...
So I'll disconnect everything but the Vu+ and my desktop and see what happens.

BTW I could get a log in a recent crash because ftp this time was not down after the crash. I'll send you a cut version of the log file because the actual complete file was growing under my eyes (reached 80MB+) when I power off the box. The rest of the file was an endless repetition of the last blocks that you can see at the end of the one I send you.

The log reproduces the error message I got on the screen when setting the [TranscodingSettup]!? But I know very little on linux and I hope you can found some useful information in this file.

But how can I send the file? Attachments are disabled because I'm a new user with very few posts.

 

[Davitat]

Maybe it's easier to use an USB-stick for the logs. That can easily be disconnected from the box and connected to a PC to retrieve any debug & crash logs.

Good idea man, I'll do it.
For now it seems I could finally get some logs on my hdd (see please my post #33 replying to judge) and I'll gone to disconnect it on my box an read it in my pc.

 

[roybach]

I also thought of a virus. My network is a small home network with 1 desktop, 1 laptop with W10 and 1 Android smartphone but also 2 ip cams and one NVR (Network Video Recorder for the cams) on witch, you make me think of, I updated the firmware (based Linux box) this lasts weeks from a non very trusted source...
So I'll disconnect everything but the Vu+ and my desktop and see what happens.

BTW I could get a log in a recent crash because ftp this time was not down after the crash. I'll send you a cut version of the log file because the actual complete file was growing under my eyes (reached 80MB+) when I power off the box. The rest of the file was an endless repetition of the last blocks that you can see at the end of the one I send you.

The log reproduces the error message I got on the screen when setting the [TranscodingSettup]!? But I know very little on linux and I hope you can found some useful information in this file.

But how can I send the file? Attachments are disabled because I'm a new user with very few posts.

Davitat , I have exactly the same problem as yourself , I have flashed at least four different Vix images and am currently back to Apollo 011 , but still getting the same crashes , as you speculate that the problem is resident in the STB flash memory. Don't sweat over sending log files as I have sent numerous crash logs (saved to USB ) to Vix support without receiving any response to date, I expect they are busy trying to resolve the problem, I see that they have updated to 013 for some STB's but not all, so check if your VU+ has one. My STB is a GI Xpeed LX2 so looks like Vix Image is the common denominator here. Sorry I can't suggest anything .

 

[Davitat]

Davitat , I have exactly the same problem as yourself , I have flashed at least four different Vix images and am currently back to Apollo 011 , but still getting the same crashes , as you speculate that the problem is resident in the STB flash memory. Don't sweat over sending log files as I have sent numerous crash logs (saved to USB ) to Vix support without receiving any response to date, I expect they are busy trying to resolve the problem, I see that they have updated to 013 for some STB's but not all, so check if your VU+ has one. My STB is a GI Xpeed LX2 so looks like Vix Image is the common denominator here. Sorry I can't suggest anything .

Hi roybach,
Yes I read your post previously in this thread. It's a very strange issue because it seems to 'brake' something and then even earlier versions crash.
Second strange thing is its seems random, not tied to any user action, nor configuration... frankly it seems an hardware thermal issue.

I can confirm that it is NOT a virus in my network as I have disconnected everything but the STB and my desktop (W10), disconnected hdd in the STB and made a clean 3.2.013 install and log with a fresh formatted USB stick, and it just crashed a few minutes ago after running around 2 hours.

Do you think they are working on that? I'm not so sure because it seems (another mystery) that we are very few with this problem. I'm also not sure that the problems with build 010 were tied to this.

 

[abu baniaz]

Please wait until 014 is out. Flash without restores.

 

[Davitat]

Please wait until 014 is out. Flash without restores.

Ok, Abu, thanks... So can I speculate that this problem is what you are trying to solve with this 'post 010' builds?
As I write in some previous post, I'm pretty sure to have had this crashes before build 010, not the firsts 3.2 but somewhere in the middle.

 

[Andy_Hazza]

I'm unable to replicate any of this on my Vu+ Solo2 running on the latest ViX 3.2 Build. [emoji57]


Sent from my iPhone using Tapatalk

 

[Davitat]

I'm unable to replicate any of this on my Vu+ Solo2 running on the latest ViX 3.2 Build. [emoji57]


Sent from my iPhone using Tapatalk

Yes, that's one more reason why it's so strange and makes me think on a virus or an hardware problem but on the other hand, it's also very surprising to have the exact same error and behaviour in different hardwares...