dfp wrote: ↑Sat Jun 16, 2018 16:48
Is there any debugging can turn on to work out the source of the spin.
Yes, debugging can be switched on in OpenWebif, in Settings>Log settings. Click on the "Enable debugging" checkbox. Leave the Log location as the default /home/root: switching it to /media/hdd will make the logging affect whether the HDD is considered idle. Log files are in /home/root/logs, date stamped by system startup time.
I assume from what you've written below that you're reasonably OK with getting files on and off the PVR.
However, those log files may not be all that helpful for this problem.
If you are familiar with the commandline interface, you can fairly easily read the counters that are used to decide whether the HDD is idle.
The command:
awk '{print $1, $5}' /sys/block/sda/stat
prints the two counters (reads from device, writes to device) that are used to check whether the disk is idle. If they don't change for more than 5 min (default setting), the HDD is spun down.
Once you've verified that there is HDD activity that's stopping the spin-down, you can then find which files processes have open on the HDD:
Code: Select all
root@beyonwizu4:/proc# ls -l /proc/[0-9]*/fd 2> /dev/null | awk '/\/media\/hdd/{print $11}'
/media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
/media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
/media/hdd/timeshift/timeshift.ZfV4iT
/media/hdd/timeshift/timeshift.ZfV4iT.sc
root@beyonwizu4:/proc#
That's from a running U4, with logging directed to the HDD. In standby, I get:
Code: Select all
root@beyonwizu4:/proc# ls -l /proc/[0-9]*/fd 2> /dev/null | awk '/\/media\/hdd/{print $11}'
/media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
/media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
root@beyonwizu4:/proc#
The timeshift files have been closed.
You can also extend that to see whether the files are being written to:
Code: Select all
root@beyonwizu4:/proc# ls -l `ls -l /proc/[0-9]*/fd 2> /dev/null | awk '/\/media\/hdd/{print $11}'`
-rw-r--r-- 1 root root 162786 Jun 16 17:34 /media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
-rw-r--r-- 1 root root 162786 Jun 16 17:34 /media/hdd/logs/Enigma2-2018-06-16_09-12-07.log
root@beyonwizu4:/proc#
If you repeat the command, you can see whether the file sizes and/or modify timestamps are changing.
Unfortunately, it's hard to check for file-specific read activity this way
Apologies if that's all gobbledygook to you - the Unix shell and command set are quite powerful, but can be a little cryptic if you're not familiar with it.
dfp wrote: ↑Sat Jun 16, 2018 16:48
I did import my autotimers.xml from the older firmware however I didnt bring in any other xml's, could this have caused a bug?
That should be OK, and shouldn't cause any problems.
