e2fsck aborted; looks pretty much the same.
Not sure if too late to check after end of execution, but:
# free -m
total used free shared buffers
Mem: 125016 11392 113624 0 928
-/+ buffers: 10464...
Fell at the first hurdle:
# ls -l /mnt/hd3/.swap0
-rw-rw-rw- 1 root root 134217728 Jan 21 12:28 /mnt/hd3/.swap0
# swapoff /mnt/hd3/.swap0
swapoff: /mnt/hd3/.swap0: Invalid argument
Again many thanks for the interest.
So, are the steps thus:
Put the Hummy in maintenance mode.
Go into CLI
Run the commands in @Black Hole's https://hummy.tv/forum/threads/unresponsive-after-fixing-malformed-aac-bitstream-with-qtube.10480/#post-159594.
With 1024 rather than 256?
run e2fsck...
Thanks for the suggestion. Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient and I will need to do the Linux boot?
Good morning. I now realise that the front reports "fixdisk done". I exited maintenance mode and rebooted; the Hummy still asks to be reformatted.
Is there another diagnostic one could run?
Edit: I ran another fixdisk -P -y; this time the terminal showed progress and completed (failed, as per...
I think you are asking if I had set it to sleep after some time; I had. It had shut down earlier, before I put it in maintenance mode and started fixdisk and perhaps the maintenance mode prevents this from kicking in; the box appears on, the roundel being blue.
Wondering if fixdisk crashed...
3.5 hrs in it looks like it hung. I lost contact; is there a way to reconnect with the terminal? I restarted telnet on a new window and I just see the usual options; I thought there used to be a "connect" or something?
fixdisk - Check and repair hard disk.
short - Run short hard-disk self...
Empty directory. :)
OK, I ran fixdisk with -P -y, let's see how it goes.
Happy days (modulo the subject of this and the other thread. :) :))
Thank you for your prompt, informative posts!
Restarting the conversation from https://hummy.tv/forum/threads/schedule-list-shows-programmes-already-recorded.10474/page-3#post-159771 to decontaminate that thread.
The problem
I ran fixdisk, which made a large number of repairs. I think it finished with out of memory error, and I do not know...
Thanks for the interest, everyone. Are we contaminating the thread, is there a better one?
SMART stats (fixdisk still running, if it makes a difference):
Humax HDR-Fox T2 (HumaxOld) 1.03.12/3.13
To return to the menu, type: exit
HumaxOld# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109...
It has been running for 75 minutes or so now. That does not bother me; it's just the observation that the messages are exactly the same that I found alarming:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk...
I kicked it off; I think it's stuck in a loop thus:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk.
Also checking blocks 251006816 - 251006823 (8 blocks)
Block 251006816 - OK
Block 251006817 - OK...
Sorry, I was not clear: I followed your clear instructions and after a shedload of repairs, fixdisk finished. The system rebooted and the Hummy is asking to reformat the disk; I did not do that. I cannot access the WebIF (in a loop of "The system is initialising.").
I note @prpr's pointer and...
Ok, I will look into system flush next.
But after I do some research on whether/how I can recover from fixdisk trashing the remote Humax (it asks to reformat its HDD). Different thread, I am sure.
e2fsck aborted; looks pretty much the same.
Not sure if too late to check after end of execution, but:
# free -m
total used free shared buffers
Mem: 125016 11392 113624 0 928
-/+ buffers: 10464...
Fell at the first hurdle:
# ls -l /mnt/hd3/.swap0
-rw-rw-rw- 1 root root 134217728 Jan 21 12:28 /mnt/hd3/.swap0
# swapoff /mnt/hd3/.swap0
swapoff: /mnt/hd3/.swap0: Invalid argument
Again many thanks for the interest.
So, are the steps thus:
Put the Hummy in maintenance mode.
Go into CLI
Run the commands in @Black Hole's https://hummy.tv/forum/threads/unresponsive-after-fixing-malformed-aac-bitstream-with-qtube.10480/#post-159594.
With 1024 rather than 256?
run e2fsck...
Thanks for the suggestion. Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient and I will need to do the Linux boot?
Good morning. I now realise that the front reports "fixdisk done". I exited maintenance mode and rebooted; the Hummy still asks to be reformatted.
Is there another diagnostic one could run?
Edit: I ran another fixdisk -P -y; this time the terminal showed progress and completed (failed, as per...
I think you are asking if I had set it to sleep after some time; I had. It had shut down earlier, before I put it in maintenance mode and started fixdisk and perhaps the maintenance mode prevents this from kicking in; the box appears on, the roundel being blue.
Wondering if fixdisk crashed...
3.5 hrs in it looks like it hung. I lost contact; is there a way to reconnect with the terminal? I restarted telnet on a new window and I just see the usual options; I thought there used to be a "connect" or something?
fixdisk - Check and repair hard disk.
short - Run short hard-disk self...
Empty directory. :)
OK, I ran fixdisk with -P -y, let's see how it goes.
Happy days (modulo the subject of this and the other thread. :) :))
Thank you for your prompt, informative posts!
Restarting the conversation from https://hummy.tv/forum/threads/schedule-list-shows-programmes-already-recorded.10474/page-3#post-159771 to decontaminate that thread.
The problem
I ran fixdisk, which made a large number of repairs. I think it finished with out of memory error, and I do not know...
Thanks for the interest, everyone. Are we contaminating the thread, is there a better one?
SMART stats (fixdisk still running, if it makes a difference):
Humax HDR-Fox T2 (HumaxOld) 1.03.12/3.13
To return to the menu, type: exit
HumaxOld# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109...
It has been running for 75 minutes or so now. That does not bother me; it's just the observation that the messages are exactly the same that I found alarming:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk...
I kicked it off; I think it's stuck in a loop thus:
Running select disk self test
Error at LBA 251006816
/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk.
Also checking blocks 251006816 - 251006823 (8 blocks)
Block 251006816 - OK
Block 251006817 - OK...
Sorry, I was not clear: I followed your clear instructions and after a shedload of repairs, fixdisk finished. The system rebooted and the Hummy is asking to reformat the disk; I did not do that. I cannot access the WebIF (in a loop of "The system is initialising.").
I note @prpr's pointer and...
Ok, I will look into system flush next.
But after I do some research on whether/how I can recover from fixdisk trashing the remote Humax (it asks to reformat its HDD). Different thread, I am sure.
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.