There is a problem but impossible to say how significant it is without the full diagnostics. I would try connecting via telnet and running fix-disk.
That isn't right. Can you explain exactly what you are doing, step by step.
I used Putty open a telnet connection. Enter System Pin, type diag, return, Fix-Disk, return. Says it running for less than a second and I get press return to continue, and I'm back to the Telnet Menu screen again. Since I've done that however, it seems to have settled down, is responding quickly and recording programs again. I'll have the new drive tomorrow so hopefully I'll have time to fit that and just call this episode another glitch, if any of that makes sense.
Don't - it isn't a diagnostic. Type "maint" instead and follow the instructions.
Probably not. But you need to post the SMART stats.
As others have said, you can't run fix-disk without first entering maintenance mode.
It's close enough - step 2 talks about how to access the Telnet menu, step 3 talks about entering maintenance mode and then selecting the fix-disk option.
Yes; that doesn't look too bad to me. Have you run fix-disk yet?
I've not done it since it started behaving itself. I'll give it a try before I fit the 2Tb drive which arrived this morning.
It isn't. You just haven't needed to read/write those problem sectors yet.
Just report the stats. again. The attributes of interest are IDs 5,187-189,197-198.
If you look in /bin the actual software is called fix-disk but the user interface may call it something else; anyway we are talking about the same thing.
It isn't the custom firmware version that matters; what does matter is the version of the standard Humax software. It needs to be 1.03.12.
I just checked and it is 1.03.12, so fingers crossed.
Yes.
