Vu+ Duo2 Boot Time

[chuf]

Hi All

Is it just me but the boot time for my box takes nearly 5 minuets from power off to watching a tv show, are they all the same?

Chuf

[john doe]

should be faster. my solo takes about a minute to minute and half.

[chuf]

should be faster. my solo takes about a minute to minute and half.

Well that's what got me thinking as I have a VU+ Solo SE as well and that boots in under a minuet.............

Any ideas what might be slowing it down?

[tappari]

2 minutes and 12 seconds with 4 nfs mounts (FSTAB) and 3 cifs mounts (AUTOFS) connected. Duo2. Those cifs nas drives will take some time to wake up since they are upstairs behind powerline adapters.

[john doe]

Well that's what got me thinking as I have a VU+ Solo SE as well and that boots in under a minuet.............

Any ideas what might be slowing it down?

have you recently updated? if so try a restart

[bellejt]

duo2 openvix and softcam oscam : 1 min 50 sec and viewing channels.

[gerinemo]

VU+Duo2 with vix
1:50

[Rob van der Does]

My DUO2 also takes around 2 minutes to boot.
Be aware that plugins, external mounts (especially when not available) and (lots of) timers/autotimers have a huge influence on booting time.
Nevertheless: DUO2 is the slowest of all my boxes.

[Clabs]

My DUO2 also takes around 2 minutes to boot.
Be aware that plugins, external mounts (especially when not available) and (lots of) timers/autotimers have a huge influence on booting time.
Nevertheless: DUO2 is the slowest of all my boxes.

Thanks for that Rob

My Duo2 was taking a similar long time to boot but only had a chance to look at this today and your post made me mindful of the impact of unavailable network devices . Turned out to be a network mount for a device that is no longer connected to my network. I removed that and back to 95 second boot times.

[MPEGMAN]

My Duo2 takes in excess of 20 mins to reboot...I also thought that it could be trying to resolve non-existant network locations so I went through and deleted them all (Is there a 'bulk' way of doing this as it took me hours to do individually)
After all that effort the boot time has reduced from about 20 to 15 mins..
It does seem to be a rather flaky part of the system...Very often I add a new location and everything seems to have completed OK but when I try and access the location I get the message 'Directory /media/autofs/..... does not exist'
Could this be a clue..?
Any suggestions..

Mark

[Rob van der Does]

20 mins is far too long, as is 15 mins.
Having deleted my network mounts boottime is back to just over 1 minute.
The best way to add mounts that are not always available is using the networkbrowser and to add them via the autofs-protocol. But even then it takes time to look for them when they are not available at boottime. This is normal Linux behaviour.

To manually delete servers you can look in the files etc/enigma2/automounts.xml, etc/fstab & etc/auto.network. And given your excessive boottime, there may be still entries in there or they might be corrupted.

Anyway: your box set-up is not OK, far from it. I would simply reflash, without using restore.

[chuf]

I have three mounts so will try and remove them when I get 5 and see if it makes any difference

[chuf]

Just found my issue in etc/fstab found 3 old mounts that I changed the ip address

[Rob van der Does]

Good. So all fixed now? Boottime is....?

[chuf]

Good. So all fixed now? Boottime is....?

From poweroff to picture on the screen is an amazing...............................1 minuet 44 seconds Whey!!!!!!!!!!!!!!!!!!!!!!

Tnks for the help