Box failing to power up properly

RickT

New Member
Hi,

I came to turn on my box tonight and it failed to respond to the remote. I tried the button on the front - nothing.

Display is showing the time. I have the redring package installed and the front was showing bright blue as if it was powered on.

I power cycled it, but same situation.

I tried connecting via the web interface - connection was reset suggesting web server isn't running.

I tried telnet and got a connection! But it took seconds to give me a prompt after the motd prompt, and trying some commands showed it was very slow responding to commands.

I went to /var/log and tried "cat"ting logs that had been updated today. modinit.log shows the following:

I tried to post the log here using the code tags but the board complains I can't post links or email addresses for some reason, so I've attached file with it in.

The message about timing out and aborting doesn't sound good to me.

I tried reloading the firmware from HDR_FOX_T2_1.03.12_mod_3.10.zip (which is what it was running) by plugging in a USB stick to see if that helped - it didn't but this time when it rebooted it got as far as giving me video and audio but it left the channel information on the screen not timing out and was still slow responding to commands and ignored the remote.

Any ideas please?

Thanks in advance.
 

Attachments

  • modinit.log.txt
    13.4 KB · Views: 9
Last edited:

peterworks

Ye Olde Bowler
If I read it correctly it looks like your My Video is nearly full (sda2 used 850.8 - 99%). If this is the case it may help to delete some files.
 

prpr

Well-Known Member
Run fix-disk from the command prompt (0r if using the menu select maint mode) and folllow the instructions.
 
OP
R

RickT

New Member
Thanks for the replies.

I tried deleting some files - no change.

So I rebooted into Maintenance Mode and ran fix-disk. That took some time, but it found some problems on the disk and fixed them (see below)

Code:
Humax HDR-Fox T2 (humax) 1.03.12/3.10

humax# fix-disk
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (512 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3


Running short disk self test
Error at LBA 1403006164
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1403006164: succeeded

Running short disk self test

No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 1403006164
LBA: 1403006164 is on partition /dev/sda2, start: 2104515, bad sector offset: 1400901649
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 1403006164 maps to file system block 175112706 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 175112706 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 60163035

The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.

debugfs 1.42.13 (17-May-2015)
Inode   Pathname
60163035        /mnt/hd2/mod/tmp/redring.log


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda3: 17/655776 files (5.9% non-contiguous), 341704/2622611 blocks

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 16/65808 files (0.0% non-contiguous), 17565/263064 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=6b8bbcdf-b2c0-4466-9937-639ecb69e592

Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 8701/60334080 files (6.8% non-contiguous), 225728348/241304332 blocks
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: n
Skipped

Finished
humax#

After rebooting - all seems fine again. :)

I ran up the web interface and got a message about problems with the hard disk:

Code:
There are potential hardware problems with the internal hard disk on this device.

Disk pending sector count is: 1
Disk offline sector count is: 1

So, I will have to keep an eye on that and make sure I have backed up the contents. I may have a failing disk. If it looks like it needs replacing I shall probably upgrade it and put a 2TB in it. I've found a guide that seems simple enough to follow here: www . avforums . com/threads/full-instructions-for-upgrading-humax-hdr-fox-t2-to-2tb-hard-drive.1335706/

Thanks again. :doublethumbsup:
 

Trev

The Dumb One
It's a doddle. Take the old one out, stick in the new one in. Follow the screen instructions. Job done.
Just need a little screwdriver expertise, but not a lot. Disconnect the drive connector from the mainboard first.
 

MartinLiddle

Super Moderator
Staff member
www . avforums . com/threads/full-instructions-for-upgrading-humax-hdr-fox-t2-to-2tb-hard-drive.1335706/
Those instructions are out of date (note I haven't read the whole thread). Assuming the Humax is using software version 1.03.6 or later then simply change the drive and allow the Humax to format it. The statement that drives larger than 2TB cannot be used is also wrong; using the custom firmware much larger drives are supported.
 

MontysEvilTwin

Well-Known Member
Thanks for the replies.

I tried deleting some files - no change.

So I rebooted into Maintenance Mode and ran fix-disk. That took some time, but it found some problems on the disk and fixed them (see below)

Code:
Humax HDR-Fox T2 (humax) 1.03.12/3.10

humax# fix-disk
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (512 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3


Running short disk self test
Error at LBA 1403006164
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1403006164: succeeded

Running short disk self test

No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 1403006164
LBA: 1403006164 is on partition /dev/sda2, start: 2104515, bad sector offset: 1400901649
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 1403006164 maps to file system block 175112706 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 175112706 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 60163035

The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.

debugfs 1.42.13 (17-May-2015)
Inode   Pathname
60163035        /mnt/hd2/mod/tmp/redring.log


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda3: 17/655776 files (5.9% non-contiguous), 341704/2622611 blocks

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 16/65808 files (0.0% non-contiguous), 17565/263064 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=6b8bbcdf-b2c0-4466-9937-639ecb69e592

Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 8701/60334080 files (6.8% non-contiguous), 225728348/241304332 blocks
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: n
Skipped

Finished
humax#

After rebooting - all seems fine again. :)

I ran up the web interface and got a message about problems with the hard disk:

Code:
There are potential hardware problems with the internal hard disk on this device.

Disk pending sector count is: 1
Disk offline sector count is: 1

So, I will have to keep an eye on that and make sure I have backed up the contents. I may have a failing disk. If it looks like it needs replacing I shall probably upgrade it and put a 2TB in it. I've found a guide that seems simple enough to follow here: www . avforums . com/threads/full-instructions-for-upgrading-humax-hdr-fox-t2-to-2tb-hard-drive.1335706/

Thanks again. :doublethumbsup:

One bad sector does not mean that the disk needs replacing yet. The problem is that it has not been reallocated. The key bit of your fixdisk log is here:
Code:
LBA 1403006164 maps to file system block 175112706 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 175112706 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 60163035

The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.

debugfs 1.42.13 (17-May-2015)
Inode   Pathname
60163035        /mnt/hd2/mod/tmp/redring.log
I would delete redring.log, and run fixdisk again.
 
Top