Do you see any lines marked in red under the WebIf >> Diagnostics >> Hard Dusk page?
If ids 197 or 198 are non-zero, you are highly likely to get picture breakups.
This should be fixed by upgrading to CF version 2.19 and running fix-disk with the -l option. However, if these numbers are increasing then it is probably time for a new disk.
Nightmare isnt it! However i hope you get it sorted, i did and i am a complete IT novice, the guys here guided me through a treat.
On one side of things its a shame the HD does not seem to last as long as one might expect ( 2 and a bit years for me) but at least the box is such that we can replace components and not just end up with an expensive paperweight.
It has been around for a couple of versions now. When fix-disk is run without options it will normally perform a short test. If there are still pending sector errors which can not be located with a short test it will run a long test. The -l option forces a long test.My current software is 1.02.32 with firmware 2.18.
The new drive has arrived but I'm fine with trying 2.19. Is the -l option new? I don't remember the options I saw the last time |I ran fix-disc.
It took about 2-3 hours to run a long test on my 500GB disk but may take longer if it finds errors. When an error is found fix-disk will normally attempt to find the file which contains the error - this can take a few minutes.The only issue with running fix-disk is how long it takes, as I may not have time to replace the drive if I have to wait ages for fix-disk to run.
Edit: I just upgraded to 2.19, and am loading mtce mode so I can try fix-disk.
Now running long test. Last time I tried a long test it counted down to about 8000 and then froze on that value. I'm wondering if a scheduled program can interrupt the test?
Edit2. fix-disk is reporting a corrupt block that cannot be deleted and saying that I might want to delete it. Then there is a debugfs 1.41.14 (22-Dec-2010) line. I am not back at a prompt but there is no sign that it is still running or any option to actually delete the bad block. I guess I will leave it running, but not sure what to do next.
OK, it's still doing something. I just gave an option to attempt repair and reported that re-writing the sector was successful. There is a rather long delay between reporting a bad sector and giving an option to try and fix it.
Well, it finished and reported less than 10 sectors successfully re-written (didn't report any failures). Afterwards I went back to WebIf and ran disk diags, and the two red entries were still there and the counts reported were the same. However, a program recorded afterwards played back without any glitches.It has been around for a couple of versions now. When fix-disk is run without options it will normally perform a short test. If there are still pending sector errors which can not be located with a short test it will run a long test. The -l option forces a long test.
It took about 2-3 hours to run a long test on my 500GB disk but may take longer if it finds errors. When an error is found fix-disk will normally attempt to find the file which contains the error - this can take a few minutes.
No! You have not wasted my time. Time spent trying new things is time spent learning, and I very much appreciate your help, and that of other on this forum.Yes, it definitely sounds like the disk needs replacing. Sorry to have wasted your time.
I don't know if a 2 bay cloning device will work or not: I presume it is one of those ones that copies without the use of a PC. The method I suggested needs a Windows PC plus two caddies/ USB ports, with the clone mediated by the Acronis/ Seagate software. If the caddy can also be connected to a PC and mount the two drives separately you can probably use this to clone the drive using the PC and software. My other post discusses which software version to use.Hi MontysEvilTwin,
I have Acronis true image and I also have a drive cloning caddy with two bays that, in theory (and according to user manual) should copy direct from one drive to the other. However, I did not think that would work with the kind of drive format that the hummy uses. I don't remember the format types, but I know it's not a very 'usual' one.
By the way, I also have 1tb and the new drive is Seagate. Actually the first time I have seen a drive specifically labelled 'Video 3.5 HDD'.