Well, here's the next instalment.
Story so far: All three partitions are formatted from the command line (not Humax's UI) and check out fine with fix-disk.
This evening I ran fix-disk again. Still good.
Ran the Humax UI disk check. No problems.
So I tried formatting it from the Humax UI. The UI said:
Cannot format the hard disk. The capacity is too large.Re-ran fix-disk. Still OK.
Tried formatting the disk again. Same message.
Re-ran fix-disk again....
Now sda1 has the fault and fix-disk is spewing messages like mad.
So it looks as though:
Anyone else found this on machines formatted by 1.03.12/2.22?
- The boxes come formatted strangely, in a way that fix-disk (or rather e2fsck) doesn't like.
- Using the Humax UI formatter leads to it getting formatted strangely.
- Using the command line (mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sdan) leaves it formatted normally (at least by e2fsck's standards).
- It seems to stay that way as long as we don't reformat it using the Humax UI.
I tried installing e3fsprogs 1.41.14-2 from the web interface but it didn't change the binary for e2fsck. Didn't check to see if it changes the binary for the formatter though.It might be worth trying a later version of e2fsprogs since there seems to be a bug somewhere. I am not sure if the version that ships with 1.03.20 has been replaced in the CF version (@af123 would know).
The official firmware doesn't ship e2fsprogs, not even busybox versions. The CFW contains some of the binaries but they're the same as the ones in the e2fsprogs package, 1.41.14It might be worth trying a later version of e2fsprogs since there seems to be a bug somewhere. I am not sure if the version that ships with 1.03.20 has been replaced in the CF version (@af123 would know).
Especially as my reading of the DTG website is that Humax pay a significant amount of money for a broadcast...Makes you wonder why Humax couldn't have just released a USB stick installable version in addition, and avoided all the conspiracy theories about why the OTA was pulled.