Solo 4k crashing and stuck at boot?

[abu baniaz]

What are you using to "telnet" to receiver.
Did you install anything else?
Can you still connect to receiver and FTP?
If you are using DCC, please say so.

[neo1607]

Logs are set to hdd, even rebooted to confirm the change as it said.

Tried using mobile telnet app off my phone and Putty on my laptop neither can connect to it after it crashes

[neo1607]

This is another crash from earlier today, different error this time, dunno if that helps any

20161211_141139.jpg

[abu baniaz]

Are you going to answer the question about FTP and other items installed?

[twol]

Both crashes are different, but show as in /tmp not on hdd......... strange

[abu baniaz]

There were posts pointing to same crash some time back. There was a quick solution by Birdman

[neo1607]

Can't connect to FTP or anything after it crashes, there is no network activity on the box, it's pretty much unusable apart from re-flashing

There is nothing else installed, I have tried the box from a fresh install, the only thing i configure is ABM and CrossEPG, then i move my oscam configs onto the box, download oscam (have tried both latest and pcscd), the box works ok for anything between 10mins and 30mins before crashing.

What I don't understand is why it's suddenly doing it now, the box worked fine for months and nothing was altered then after the initial crash last week it is now a regular thing, Im used to E2 boxes crashing but not where they refuse to boot again afterwards without a reflash

There were posts pointing to same crash some time back. There was a quick solution by Birdman

The solution by birdman to remove the memory stick wouldn't have affected anything, there was no memory stick inserted, it was removed as soon as the flash completed, the only storage is the flash memory on the box and the hard drive

[abu baniaz]

You are referring to HDD mount issues after flashing.

I am referring to something else. I'd post a link if I could find the posts. I'm pretty sure Birdman will post link to it after seeing this.

[DaMacFunkin]

Have you ever run another e2 image on the box?
I had solo4k from release when there was no VIX, so my hard drive was initialised and formatted by VTi and maybe again by blackhole.
I had lots of hard drive problems and some crashes caused by the hard drive randomly re-mounting at media/sda and media/sdb till I removed the hard drive, reflashed with no hard drive attached, deleted the partion in and formatted in a PC, then reattached hard drive, and initialised from fresh in VIX then converted to ext4.
Since then my hard drive mounts correctly as media/hdd and I've had no further problems.

[judge]

Where are you installing your cam from?
Also sounds like a solo2 clone issue...

[birdman]

because you have the logs in flash

Good spot.
My suspicion is that as a result of this you end up filling up your flash.
This might explain why it can't find /tmp/cam.check.log (it had run out of space to create it?).
It might also explain why it can't find /dev/dvb/adapter0/demux0.

Do you have USB stick on the box permanently? If so, configure your logs to /media/usb. If not, configure them to /media/hdd.

[neo1607]

I only started enabling the logs after it started crashing, unless oscam is filling the flash with logs?

There is no USB permanently attached only the hdd

And it shouldn't be a clone issue as I bought the box direct from WOS, is it possible the flash memory is maybe damaged? Maybe worth seeing about a RMA on the box coz it's less than 3 months old

[twol]

As it seems to log to flash and you have said earlier that you have set logging to hdd, can only think it doesn,t recognise the hdd.
Why don,t you use a usb stick for logs while the issue is resolved..... I don,t see the flash being "damaged".
So I would reflash, setup logs to usb, restart without doing anything else then run abm and see if the box holds up.
Then add the softcam etc ...... a step at a time.