Is anything shown in webif-error.log (viewable via the diagnostics page) following a crop attempt?
As an experiment try a Detectads run with cropping within detectads and see if that runs (can specify -crop y -debug 2 in "Process options" if you don't want to change the global setting)
/mnt/hd3/fix-disk.0.log viewable in the log file list on the webif diagnostics page
Humax can get very slow if one of the bad sectors is in a file that is frequently accesed or seem unaffected if in a recording not being played,
Fixdisk is best run overnight because of the time it can take.
If your box fails to completely shut down when you press power off (& a recording is not in progress/pending) this is known a 'delinquent half awake'
This can have several causes but I have found these tests useful in detecting recordings causing problem
Just the three standard Humax partitions which didn't show any erros
I just ran df and surprised to see it showing 100% used on hd2 although webif show 96GiB free
humax ~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 22144 22144 0...
I can't say that I have ever seen this, I use Visual all the time to resolve conflicts.
What version of webif are you currently using?
Does Visual on Remote Scheduling show the same results?
Almost certainly coincidental - with random events it is very dificult to tell if they have really stopped occuring and why they have stopped,
but since there can no longer be any over the air updastes the package is fairly pointless these days.
I suppoe it is possible th Humax uses the OTA...
My only hypothesis at the moment is that as the disk fills it becomes harder to find contiguous free space and that if there are too many head movements the disk buffers fill up and eventually an error can surface. But the disk isn't that full and you would expect it to be more likely when...
Probably belongs on Site/Foums Issues https://hummy.tv/forum/forums/site-forum-issues.22/
But does it matter - just make a note for next year
Mine is on auto repeat
I am not sure whether this tells us anything useful - errors seem to be all reported at power up
smartctl -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION...
It is the original 500GB disk, CF auto processing was not active at the time and Detectads wasn't running (BBC recording) and it was 36minutes into the recording so not something caused by recording start/end.
The most obvious cause would be some sort of write error being misinterpreted as...
Today while watching a programme whilst it was recording I received an on screen popup saying "Recording stopped - HDD full" (or words to that affect) and the recording status shows as "Valid/Incomplete: Disk was full" but the disk has 88GiB free space and the file system hasn't gone Read-Only...
It was broken earlier today but now RS Visual display is showing correctly, strange but good.
I was pleased that webif was working fine on both Visual display and Webif
Another way to test via the epg page would be to set up favourites lists which contain a subset of channels and see which channels cause problems on the epg pages and which don't
Also try deleting all scheduled recordings, see if that resolves problem and then reschedule one by one
It must be...
It also works for me on an Android phone though I thought they were server generated error messages rather than browser error messages so device likely to be irrelevant.
Do other RS pages work?
Does it fail with your other Humax boxes?
What recordings do you have scheduled?
Have you tried from...
Is anything shown in webif-error.log (viewable via the diagnostics page) following a crop attempt?
As an experiment try a Detectads run with cropping within detectads and see if that runs (can specify -crop y -debug 2 in "Process options" if you don't want to change the global setting)
/mnt/hd3/fix-disk.0.log viewable in the log file list on the webif diagnostics page
Humax can get very slow if one of the bad sectors is in a file that is frequently accesed or seem unaffected if in a recording not being played,
Fixdisk is best run overnight because of the time it can take.
If your box fails to completely shut down when you press power off (& a recording is not in progress/pending) this is known a 'delinquent half awake'
This can have several causes but I have found these tests useful in detecting recordings causing problem
Just the three standard Humax partitions which didn't show any erros
I just ran df and surprised to see it showing 100% used on hd2 although webif show 96GiB free
humax ~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 22144 22144 0...
I can't say that I have ever seen this, I use Visual all the time to resolve conflicts.
What version of webif are you currently using?
Does Visual on Remote Scheduling show the same results?
Almost certainly coincidental - with random events it is very dificult to tell if they have really stopped occuring and why they have stopped,
but since there can no longer be any over the air updastes the package is fairly pointless these days.
I suppoe it is possible th Humax uses the OTA...
My only hypothesis at the moment is that as the disk fills it becomes harder to find contiguous free space and that if there are too many head movements the disk buffers fill up and eventually an error can surface. But the disk isn't that full and you would expect it to be more likely when...
Probably belongs on Site/Foums Issues https://hummy.tv/forum/forums/site-forum-issues.22/
But does it matter - just make a note for next year
Mine is on auto repeat
I am not sure whether this tells us anything useful - errors seem to be all reported at power up
smartctl -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION...
It is the original 500GB disk, CF auto processing was not active at the time and Detectads wasn't running (BBC recording) and it was 36minutes into the recording so not something caused by recording start/end.
The most obvious cause would be some sort of write error being misinterpreted as...
Today while watching a programme whilst it was recording I received an on screen popup saying "Recording stopped - HDD full" (or words to that affect) and the recording status shows as "Valid/Incomplete: Disk was full" but the disk has 88GiB free space and the file system hasn't gone Read-Only...
It was broken earlier today but now RS Visual display is showing correctly, strange but good.
I was pleased that webif was working fine on both Visual display and Webif
Another way to test via the epg page would be to set up favourites lists which contain a subset of channels and see which channels cause problems on the epg pages and which don't
Also try deleting all scheduled recordings, see if that resolves problem and then reschedule one by one
It must be...
It also works for me on an Android phone though I thought they were server generated error messages rather than browser error messages so device likely to be irrelevant.
Do other RS pages work?
Does it fail with your other Humax boxes?
What recordings do you have scheduled?
Have you tried from...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.