Hmmm....this looks like the closest thing yet to tempt me away from the HDR-Fox T2:
https://www.trustedreviews.com/news/humaxs-aura-the-first-android-4k-hdr-freeview-play-pvr-4104564
No ad skipping of course, but most of the other features that I want/need seem to be there.
Any views?
So I just installed the new 2TB drive, and reinstalled the full web IF. The first time I accessed the web IF I got this warning. The drive was bought as new from Amazon - a Seagate ST2000VM003. Do I need to return the drive?
Not sure how to go about checking the cache directory???
I tried fixdisk without the -y, and wasn't offered the option to ignore fixing block #52457724 - it "cleared" it without asking, then aborted with the memory allocation failure, as usual.
So I seem to have hit a dead end - I have run fixdisk -2 -P -y several times now, and the last 3 times it has reported the same illegal block (#52467724) before hitting the memory allocation error and aborting. It is not currently reporting any other illegal blocks before aborting.
Any advice...
No probs. So it should have been E2FSCK_CONFIG=/var/lib/humaxtv_backup/mod/e2fsck.conf tmenu ?
If so, still no luck - I just tried that and got the "Memory allocation failed" error again:
So I followed these instructions to the letter, but the fix-disk still gave the "Memory allocation failed" error (see below), plus another shedload of Illegal indirect block messages:
Thanks - I'll try that.
In the meantime it reported a loss of the TV signal again - "The receiver is not receiving a signal or the signal is too weak". Signal strength and signal quality were both reported as 0%. The signal returned when I did a hard reboot.
OK I'll do another fix-disk with -P -y. In the meantime I just logged into the web IF and got this:
Reading between the lines, would it be sensible just to replace the drive, rather than waiting for it to fail (and lose my recordings)?
I ran fix-disk overnight with the -l parameter. Approx. 10 hours later the screen was full of these messages:
ncheck: EXT2 directory corrupted while calling ext2_dir_iterate
ncheck: Invalid argument...
I've just retried the fix-disk and it's doing exactly the same thing as before (stuck at "Running short disk self test - Waiting... 0"). I'm guessing that this is not good news?
Hmmm....this looks like the closest thing yet to tempt me away from the HDR-Fox T2:
https://www.trustedreviews.com/news/humaxs-aura-the-first-android-4k-hdr-freeview-play-pvr-4104564
No ad skipping of course, but most of the other features that I want/need seem to be there.
Any views?
So I just installed the new 2TB drive, and reinstalled the full web IF. The first time I accessed the web IF I got this warning. The drive was bought as new from Amazon - a Seagate ST2000VM003. Do I need to return the drive?
Not sure how to go about checking the cache directory???
I tried fixdisk without the -y, and wasn't offered the option to ignore fixing block #52457724 - it "cleared" it without asking, then aborted with the memory allocation failure, as usual.
So I seem to have hit a dead end - I have run fixdisk -2 -P -y several times now, and the last 3 times it has reported the same illegal block (#52467724) before hitting the memory allocation error and aborting. It is not currently reporting any other illegal blocks before aborting.
Any advice...
No probs. So it should have been E2FSCK_CONFIG=/var/lib/humaxtv_backup/mod/e2fsck.conf tmenu ?
If so, still no luck - I just tried that and got the "Memory allocation failed" error again:
So I followed these instructions to the letter, but the fix-disk still gave the "Memory allocation failed" error (see below), plus another shedload of Illegal indirect block messages:
Thanks - I'll try that.
In the meantime it reported a loss of the TV signal again - "The receiver is not receiving a signal or the signal is too weak". Signal strength and signal quality were both reported as 0%. The signal returned when I did a hard reboot.
OK I'll do another fix-disk with -P -y. In the meantime I just logged into the web IF and got this:
Reading between the lines, would it be sensible just to replace the drive, rather than waiting for it to fail (and lose my recordings)?
I ran fix-disk overnight with the -l parameter. Approx. 10 hours later the screen was full of these messages:
ncheck: EXT2 directory corrupted while calling ext2_dir_iterate
ncheck: Invalid argument...
I've just retried the fix-disk and it's doing exactly the same thing as before (stuck at "Running short disk self test - Waiting... 0"). I'm guessing that this is not good news?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.