Humax crashed

Last.To.Know

Last.To.Know

Member
Watching the build-up to the live MOTD today, the screen froze but the audio continued.

It then rebooted and was fine.

I was only reminded of it by the message in Web-IF.
Your Humax crashed and some packages may have been disabled as a precaution.
... view the crash.log for more details.
Click to expand...
Code: 
Humax crashed at Sun Jan 31 15:46:17 UTC 2016 - Uptime: 2406

Strange this is, the first 15 minutes of the 9.00am recording of The Andrews Marr Show was full of picture break-up.

As I only recently fitted a new Hard Disk, I wonder what else could have caused that, and the reboot?

Web interface version: 1.2.6-2
Custom firmware version: 3.03 (build 2368)
Humax Version: 1.03.12 (kernel HDR_CFW_3.03)
 
There is a custom firmware package which attempts to capture more data relating to crashes for analysis. If you install crashdiag then there may be a chance of determining the cause.

It's possible that the new disk is related. Have you tried the 4kalign diagnostic to check for alignment? Always worth running a diagnostic mode fix-disk following a crash too.
 
The video freezing but the audio continuing is a symptom of the Humax software crashing. Without the custom firmware you just get an immediate black screen and reboot, but the custom firmware attempts to finish writing data to the disk and do a more controlled reboot.
 
Thank, af123.

4kalign results were promising.
Code: 
*  OK   * - partiton /dev/sdb1 is properly aligned.
*  OK   * - partiton /dev/sdb2 is properly aligned.
*  OK   * - partiton /dev/sdb3 is properly aligned.
The results of the fix-disk were more opaque, to me.
Code: 
Please select option: 1
Any additional options (or press return for none):
Are you sure you wish to run the hard disk checker? [Y/N] y
Running /bin/fix-disk
Custom firmware version 3.03


Checking disk sdb

Unmounted /dev/sdb1
Unmounted /dev/sdb2
Unmounted /dev/sdb3

Running short disk self test

No pending sectors found - skipping sector repair
Using superblock 0 on sdb1
Using superblock 0 on sdb2
Using superblock 0 on sdb3


Checking partition /dev/sdb3...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
??
?Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? yes

Pass 4: Checking reference counts
??
?Pass 5: Checking group summary information
??
?
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 13/655776 files (0.0% non-contiguous), 112533/2622611 blocks

Checking partition /dev/sdb1...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
??
?Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? yes

Pass 4: Checking reference counts
??
?Pass 5: Checking group summary information
??
?
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 14/65808 files (7.1% non-contiguous), 14076/263062 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=4e8a31f0-b7f4-4198-a484-3787885d9ec5

Checking partition /dev/sdb2...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
??
?Pass 2: Checking directory structure
??
?Pass 3: Checking directory connectivity
/lost+found not found.  Create? yes

Pass 4: Checking reference counts
??
?Pass 5: Checking group summary information
??
?
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 6551/60334080 files (6.5% non-contiguous), 169036057/241304331 blo
cks
Removing extra swap space.
 
You must log in or register to reply here.
Back
Top