My Foxsat is set to record "Home and Away" and "Neighbours" each day on Channel 5 (13.15-13.45 and 13.45-14.15). It's set on accurate record - no padding. Most days both programmes record ok, although I've noticed recently that the start signal for Home and Away is not being sent until about 1 or 2 mins into the programme.
The problem I've noticed is that on three separate occasions since either my 1TB disk upgrade or the release of 1.00.15 (both happened around the same time), "Neighbours" starts to record but seems not to finish recording. Each time I've noticed, the box is in that record/standby mode around 4 or 5 o'clock in the afternoon when it should be in full standby with the red LED illuminated. When I check the box there does not seem to be a recording in progress and when I press the media button, there are no video folders or standalone programmes in the list. If I go into file manager I can see the various series folders but each has has a zero (0) beside it indicating no contents and there are no standalone programme recordings shown in the root. If I go back to normal channel viewing I can neither pause the running programme or record it - no response to either button. Channel changing is ok - normal response to the remote - just PVR functions seem to be inhibited.
If I put the box into standby and re-boot the media list shows ok and all previously recorded programmes play ok. The particular episode of "Neighbours" is not recorded at all nor is it shown as failed. The recording schedule shows that tomorrow's edition of "Neighbours" is due to be recorded.
This happened again yesterday and I set the box to record the repeat episode of Neighbours at 17.30. It was in the same odd state when I checked around 18.15, so I re-booted. It subsequently recorded "Corrie" automatically without any issues.

Any ideas?

I don't think Channel 5 use Accurate Recording, Recordings aways seem to start and stop at the scheduled times. Very often the begiinning of Home & Away is lost. Not had the runaway recording problem. Try editing the Home & Away recording to start at 13:14 and finish at 13:45. Change Neigbours to start at 13:45 and finish at 14:16. In both cases change the repeat pattern to every weekday. You will of course have to keep an eye on the guide as if CH5 change the schedule you will have to alter the manual reservation to match.

Thanks Graham. I'm aware that C5 (and C4) seem to play fast and loose with the EIT p/f tables. They seem to be linked with scheduled clock time as you say, instead of to the actual programme start. I thought that the usage of the TV-anytime CRID data brought with it a recommendation to keep the p/f data to within 10 seconds of programme start time to facilitate accurate recording. Maybe some channels don't have the facilities for live update of the p/f data into the DVB SI stream?
I'll certainly try the manual method, although I fear the repercussions if I mess it up
I'm just a bit worried that the disk upgrade is in some way responsible for these occasional "hangs" in recording, although they seem to be linked to "Neighbours" in some mysterious way

You could schedule the late afternoon ones as well to protect you from the wrath of SHMBO

Just back from a week's holiday. The box was left to its own devices to record H&A and Neighbours (still on Accurate Record). On Wednesday 27th Home & Away (13.15) is marked as "Failed - Unknown reason" , but is, in fact, recorded ok. The following program - Neighbours (13.45) is not recorded at all, nor marked as failed. The following days, both programmes are recorded as normal.

My theory is that the box failed to detect the start flag for Neighbours on 27th, so continued to record H&A until the expiry of the time-out (I think I read somewhere that the box would continue to record for four hours if it didn't detect the end of current/start of next programme). It then truncated the recording to the scheduled start/end time and marked it as "Failed". The problem with my theory is that I would expect many soap fans to be similarly affected (if it's a broadcaster error) and I don't see any reports of this...