Thema: The hard disk starts when the channel changes

But something must be on the hdd, which is called up at the station change. Maybe the EPG?

In addition to the EPG cache and in addition to loading picons, this can be caused by the "Timeshift" function if enabled.

I didn't change anything in the set EPG, I put the picon in the device's memory. I'll check all the EPG settings, maybe something is there

...Edit...
on hdd i found 2 folders, timeshift and var, I deleted them.
After restart STB, folders are back.
How to completely turn off timeshift?
On the folder var there are more folders there, lib - opkg - info

By default, Timeshift is turned off, but check it out:
MENU -> Settings -> Recording and Timeshift -> Timeshift configuration -> .....

Maybe there is a BUG in Timeshift and maybe it wakes up your HDD after switching the DVB channel. Try disabling the "Clear the timeshift cache after switching channel" option, but that probably won't help.

It would be best to enable debug-LOG in the OpenATV MENU and then restart the box. When a problem occurs (the HDD starts spinning), send the latest LOG file from the "/home/root/logs" folder.

For example the timeshift feature is suitable for:

You can press the PAUSE button on the RCU. From now on, the DVB-stream will start recording on your disc and later when you return from the toilet for example, you can press the PLAY button again to continue watching.

Timeshift is also logically used to rewind the video. But only if the "Timeshift Recording" function is active - automatically starts recording to disc after switching channel. You must also set the maximum recording cache size on your disk (for example, 1 hour).

Advanced Timeshift functions I think can handle recording from other channels that are embedded on the same transponder (the tuned frequency or transponder can contain stream from multiple channels and not just one that you are currently watching).

Time shifting - Wikipedia

Ufff, so I don't know .... I don't see anything about using an external drive. But there is a record of showing a "spinner" (when Enigma is stuck in LAG).

Code:

23:07:27.8671 [   ] dvb/dvb.cpp:1495 DVBChannelStateChanged [eDVBResourceManager] start release channel timer
23:07:30.0095 [   ] gdi/grc.cpp:211 thread [gRC] main thread is non-idle! display spinner!
23:07:30.9186 {   } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-09-20 23:07:30+0200 [-] StackTrace
....

This is followed by a debug from a separate thread and at the end there is some plugin error called "WebkitHbbTV":

Code:

....
23:07:30.9406 {   } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-09-20 23:07:30+0200 [-] File: "/usr/lib/enigma2/python/Plugins/Extensions/WebkitHbbTV/vbipc.py", line 114, in run
23:07:30.9410 { E } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-09-20 23:07:30+0200 [-]   readable, writable, errored = select.select([self.mSock], [], [], self.mTimeout)
23:07:30.9414 {   } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2019-09-20 23:07:30+0200 [-] ========== Stacktrace end ================================

Try removing it temporarily - move the "/usr/lib/enigma2/python/Plugins/Extensions/WebkitHbbTV" folder from the set top box to a PC disk, via FTP connection, and then delete the folder in the set top box or uninstall it normally ( but I don't know if there's any dependency in some other plug-in). Reboot the set top box and check if the problem is solved.

You know this plugin - did you install it ? Or is it part of another plugin ? Or does it belong to OpenATV 6.3 firmware ? My OpenATV 6.3 doesn't have this plugin, but it's possible that it will only be in firmware for some devices, and of course I have another device - Formuler F3.

You wrote above that you also have the "/var" folder on your external drive. I don't know why there is this directory. Maybe some plugin created this folder? I have no "/var" folder on the external drive. On the external drive I only have a timeshift folder (empty folder, prepared during Enigma boot).


////////////////////////// EDIT :


One of the reasons could also be the search for picon after switching the channel on the external disk. If the picon is not found in the specific folders in a row / in a list, the picon is searched elsewhere, i.e. also on the external disk. Unfortunately, the first one search path is the external USB drive. Of course, if your disk was mounted as a USB device and not as a HDD device. Because the USB device is scanned as the first (the disk drive spins) for some picons, then the internal flash drive is scanned and finally the device mounted as HDD is scanned.

MetrixHD/MetrixHDXPicon.py at master * openatv/MetrixHD * GitHub
MetrixHD/MetrixHDXPicon.py at 6b1480ec32963c229bc22fb38eb089a7c834aae9 * openatv/MetrixHD * GitHub
MetrixHD/MetrixHDXPicon.py at 6b1480ec32963c229bc22fb38eb089a7c834aae9 * openatv/MetrixHD * GitHub

I don't know if the picons are subsequently stored in the RAM cache for later use. If so, the external disc will only spin when the specific satellite channel is switched for the first time. Then the picon will remain in the RAM cache. However, if you switch to another channel that does not already have a picon in the cache, the external disk will spin again.

You might need to change the search order. To avoid searching for picons first on the external drive and then on the internal flash drive. Perhaps this is the cause of the external disk spinning (but only first searching for picon - which is then stored in cache / in RAM).

So I would change maybe as pull-request (but I don't know if it can be this form) in code like this:

Code:

searchPaths = ('/media/mmc/%s/','/media/usb/XPicons/%s/','/media/usb/%s/','/%s/','/%sx/','/usr/share/enigma2/XPicons/%s/','/usr/share/enigma2/%s/','/usr/%s/','/media/hdd/XPicons/%s/','/media/hdd/%s/')

....to:

Code:

searchPaths = ('/usr/share/enigma2/XPicons/%s/','/usr/share/enigma2/%s/','/usr/%s/','/media/mmc/%s/','/media/usb/XPicons/%s/','/media/usb/%s/','/%s/','/%sx/','/media/hdd/XPicons/%s/','/media/hdd/%s/')

In this case, if you want, you can try the following procedure:

1. download the attached file - MetrixHDXPicon.py (it's the edited code by myself) and upload it into the folder:
   /usr/lib/enigma2/python/Components/Renderer
2. restart the GUI / Enigma or reboot the entire set-top box
3. delete the source-code file:
   /usr/lib/enigma2/python/Components/Renderer/MetrixHDXPicon.py
   (it has been compiled / compressed into the .pyo file at boot time and is no longer needed .... it will cause problems when updating OpenATV)

If it works, we'll fix it on GitHub server as a new pull-request. The condition is that the picons must be stored in the default folder, i.e. here:
/usr/share/enigma2/picon