Duo2 uses hours to boot.

N

nuldus

Vu+ Newbie
Hi. I've a duo2 wich uses forever too boot. Works great when first up and running.
I'm on a boat with, and yesterday my girlfriend had to reboot my vu+.
Resulting in no more tv at home yesterday. :/
Nedless to say. I was not very popular yesterday.
But this morning it was finished booting and all well again.
I've acces to home via vpn. So i wonder, how do i collect the boot logs? Hopfully I can resolve this issue from the boat I'm working on.
 
nuldus said:
Hi. I've a duo2 wich uses forever too boot. Works great when first up and running.
I'm on a boat with, and yesterday my girlfriend had to reboot my vu+.
Resulting in no more tv at home yesterday. :/
Nedless to say. I was not very popular yesterday.
But this morning it was finished booting and all well again.
I've acces to home via vpn. So i wonder, how do i collect the boot logs? Hopfully I can resolve this issue from the boat I'm working on.
Click to expand...
If you have an HDD, it takes some time if the system wants to checkup the disk after a determinated number of mounts or some time (the first target reached starts the check).
 
That may very well be the case. But when I was home a month ago. I also rebooted the box. Then I belive it tok around half an hour. Not shure. Because i did other things while waiting. But it took a long time. Since I'm not at home for a while, I'm afraid of rebooting it. And still whant to check the logs if there are any way of doing this. :)
 
We need more info like what image version and what plugins you have added, a reboot should be about a minute at most.
 
I'm not sure on wich plugins that is in use. Don't think i have downloaded any. But i have removed some from the menus. (Can't remember wich, sorry)
I'm running BH 2.1.6.
Tuner a.b and c have same satellite and same cable via satcr. And tuner d have 2 satellites via simple disec a/b. I've picons on a usb stick in on the backside.
And I've also switched the Blackhole hdmi cec with vti hdmi cec so that i get volume controle on my receiver.
Newer had any problems earlier. And it everything still works flawlessly when the box first is started.
 
You know the box ip, so you can log into it using telnet (putty).
Root = login
This command---> init 4 && enigma2 <--- will reboot the box and output debug information. This information will include plugins, hard drive in formation, and where the box is stopping.
To break form this format, and release the receiver, on the keyboard, hold ctrl and C at the same time. Debug output will stop. Then type---> init 3 <---.

Again, doing this will reboot the box, but it will show you what the output is.
 
Thank you very much. Can I tell my girlfriend to unplug the tv and reciver so that it don't turn on in the midle of the night? Or can that confuse the box when it's rebooting?
If not a problem. I will try your sugestion later today.
 
No. But the problem in the beginning was that it tok hours to start. So if I reboot the box. I don't knowe when it will start again. And when it boots, it will start the receiver and tv via hdmi cec.
 
Ok. So now I`m a short trip home.
I could not replicate the error on a reboot. But when i took power togle. The error came back. Looks like there whil be no tv for me tonight. :/
Looks like there is some problem with my channel list and the tuner configuration. I had to use my old list, because when i scaned the last time. It would not save anny channels. I whill upload somthing from the telnet session, and pray to that someone smarter than me can help me. :) .
 

Attachments

nuldus said:
I could not replicate the error on a reboot. But when i took power togle. The error came back.
Click to expand...

My uncle has had this issue several time ... and i could newer understand why.
He says he just cuts the power off, and the duo2 never comes up again. (waited for hours)
I always have to help him reflash.

Best regards
 
That's weird. Anyway, I did the same my self. So now it boots as it should at last. But I still have problems when searching for channels. I have to use my old list. But I'm missing some new channels on the old list.
 
I had similar problems with my Duo2 and I struggled with it for a long time. The reason was in the end wrongly configured mounts from my Windows machine. As soon as I fixed them (first removed completely) everything started to work just fine. I think the box booted just fine if the network plug was disconnected too.

I got to the root of the problem by plugin the RS232-port on my box to my PC and checking the starup info from there. I could see that it hung up on shares.
 
Thanks for the reply. I don't use any network shares. As you can see in my log. It was looping with some problem with one channel. I've updatet the box and it's now working good. :)
 
You must log in or register to reply here.
Back
Top