Customer Firmware + Nowster Patch plus BBC Red Button (2024 Olympics) = Video freeze, crash and reboot issues???

AntS

New Member
I installed the Custom Firmware v4.1.3 some time ago following a complete clearing and reformatting of my HD after a video then sound freeze issue and it has worked perfectly.

Very recently I installed the NOWSTER patch (allows HD channels to be recorded in an unencrypted format so that they can be downloaded and played back on a PC etc.). I tried this with BBC1 HD (only a minute or so) and it appeared to work.

Since installation the box has suffered from video freezes (audio continues) which can only be recovered by unplugging the box. On one or two occasions the freeze hasn't been spotted and the box reboots itself.

I spotted an old thread about BBC RB for the 2012 Olympics causing problems but (if I read correctly) this applied to recording so if this is a NOWSTER + BBC RB issue then I am guessing it is the timeshift/video buffering of a HD channel (I can't be certain but the problem seems to be isolated to BBC1 HD and BBC RB1 HD although that may just reflect that I have been watching a lot of the Olympics).

There is a possibility that the initial symptom (video freeze) is a reoccurrence of the problems from earlier this year (similar symptom) although that seemed to affect all channels and the box did not reboot.

If it is NOWSTER + BBC RB then I guess that a fresh installation of the Custom Firmware v4.1.3 will overwrite the patch and solve the problem.

Before I do that I thought I'd ask for advice. Any experience of NOWSTER issues, any ideas?
 
Last edited:
IMHO your issue is unlikely to be caused by the Nowster patch. From the symptoms you describe my guess (and it's only a guess) would be a disk corruption/failure affecting the timeshift buffer file. You said that you had similar problems previously but that they went away for a period following a reformat of the disk. This would almost certainly have moved the timeshift file to a different area on the hard disk and masked the problems for a while.

The easiest way to verify this is rename the existing timeshift buffer file so that the Humax firmware creates a new one on a different area of the disk. If you're comfortable with telnet, and you've got at least 2-3GB of free disk space, then telnet onto your box and issue the following commands:

Code:
cd /mnt/hd3/Video
mv 0.ts 0.ts.old
mv 0.nts 0.nts.old

Note that that's a zero (not a letter "o") in the file names. Note also that we're renaming the existing files not deleting them as we want them occupy the potentially corrupt sectors on the disk.

Reboot the box and see how you go.

If this fixes things for a while then your hard disk is likely on its way out I'm afraid.
 
Last edited:
following a complete clearing and reformatting of my HD
Did you actually fix the bad sectors? You never followed up on the end of the previous thread. You could provide updated SMART stats. (as a text copy/paste, not as hard-to-read images).
Any experience of NOWSTER issues
This is not going to cause the reported problems. It is just coincidental.
 
IMHO your issue is unlikely to be caused by the Nowster patch. From the symptoms you describe my guess (and it's only a guess) would be a disk corruption/failure affecting the timeshift buffer file. You said that you had similar problems previously but that they went away for a period following a reformat of the disk. This would almost certainly have moved the timeshift file to a different area on the hard disk and masked the problems for a while.

The easiest way to verify this is rename the existing timeshift buffer file so that the Humax firmware creates a new one on a different area of the disk. If you're comfortable with telnet, and you've got at least 2-3GB of free disk space, then telnet onto your box and issue the following commands:

Code:
cd /mnt/hd3/Video
mv 0.ts 0.ts.old
mv 0.nts 0.nts.old

Note that that's a zero (not a letter "o") in the file names. Note also that we're renaming the existing files not deleting them as we want them occupy the potentially corrupt sectors on the disk.

Reboot the box and see how you go.

If this fixes things for a while then your hard disk is likely on its way out I'm afraid.
Thanks.
I've done the rename and will report back.
 
The timeshift buffer rename and revcreate seems to have doen the job.

As regards the fixdisk I did run that.
 
Back
Top