• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

Before I reformat....

Wouldn't it have been easier just to download and install CF2.12/1.02.29 (it upgrades the standard firmware as well as the CF) and then use instructions for fix-disk for CF2.12 as posted HERE (click) (although I agree that if just changing permissions makes it work, that's the easiest route from where you are).
 
Ezra,

I've run the commands as suggested and the box has rebooted and come up frozen with the reformatting request on the screen obscuring a message in a black panel behind it. Unfortunatley I can't run the command you suggested as I've been telnetting in via wifi and I can't start up the wifi in this mode. How do I telnet in now? Should I connect an ethernet cable from my computer to the Humax or even into my router? If so is there any special location I have to telnet into (similar to how I used the 192.186.1.74 address when on wifi).

Thanks again,
 
Yes, connect ethernet cables from your Humax and computer to ports on your router and then Telnet as before using the IP address of your Humax - I'm guessing that is what 192.186.1.74 is
 
Ezra Pound said:
Yes, connect ethernet cables from your Humax and computer to ports on your router and then Telnet as before using the IP address of your Humax - I'm guessing that is what 192.186.1.74 is
Click to expand...

I managed to get it connected via ethernet (it was a different IP address) but this time it claims it doesn't recognise the partition. Here;s the telnet commands and responses:

humax# cd /var/lib/humaxtv/mod
humax# ./fix-disk
Warning: This procedure will freeze the Humax for anything up to 2 hours.
Please ensure that no recordings are currently in progress or scheduled
during this time.
Do you wish to continue [Y/N}? Y
The Humax will now reboot into maintenance mode
After reboot please telnet in and type this command:
/var/lib/humaxtv/mod/fix-disk
Rebooting........Connection closed by foreign host.
macintosh-109:~ Muse$ telnet 192.168.1.76
Trying 192.168.1.76...
Connected to 192.168.1.76.
Escape character is '^]'.
humax# /var/lib/humaxtv/mod/fix-disk
Unrecognised partition type, aborting...
humax#
 
I'm guessing that neither the USB or HDD versions of fix-disk will work on your Hard Disk Drive in it's present state, You can either see if af123/xyz321 can suggest something that can be done with Fix-disk or alternately FTP your recordings off the Humax and allow a Humax re-format
 
Ezra Pound said:
I'm guessing that neither the USB or HDD versions of fix-disk will work on your Hard Disk Drive in it's present state, You can either see if af123/xyz321 can suggest something that can be done with Fix-disk or alternately FTP your recordings off the Humax and allow a Humax re-format
Click to expand...

In its current state I can't see anything on the disk with FTP. It's not looking good but maybe a f123/xyz321 can help. Are they likely to see this discussion or do I need to message them directly?
 
Assuming you're still at the humax# prompt after the error message, can you run this command and post the output?

Code: 
humax# cat /tmp/.chk_devs

That should give you the name of the your disk device, e.g.

Code: 
humax# cat /tmp/.chk_devs
sda

Then print the partition table of that disk like this:

Code: 
humax# fdisk -l /dev/sda

(assuming your disk is sda, otherwise substitute sdb or whatever)

Also, post the output of:

Code: 
humax# df -h
 
Here's the output you asked for:

humax# /var/lib/humaxtv/mod/fix-disk
Unrecognised partition type, aborting...
humax# cat /tmp/.chk_devs
sda
humax# fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 131 1052256+ 83 Linux
/dev/sda2 132 120295 965217330 83 Linux
/dev/sda3 120296 121601 10490445 83 Linux
humax# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 16.4M 16.4M 0 100% /
/dev/root 16.4M 16.4M 0 100% /
tmpfs 61.0M 44.0k 61.0M 0% /tmp
tmpfs 61.0M 0 61.0M 0% /media
/dev/mtdblock1 2.0M 552.0k 1.5M 27% /var/lib/humaxtv
/dev/mtdblock2 2.0M 1.2M 812.0k 60% /var/lib/humaxtv_backup
/dev/sda1 1011.4M 40.3M 919.7M 4% /mnt/hd1
humax#
 
Try this:

Code: 
humax# fsck -y /dev/sda2
which should do a filesystem check on the main video partition. Given that fix-disk doesn't like the look of that partition, I'm not sure how successful this will be. If you have a 1TB disk then it might bomb out due to lack of memory but should tell us something along the way.
 
Here's the output:

humax# fsck -y /dev/sda2
fsck (busybox 1.12.4, 2012-05-27 00:19:41 KST)
fsck: fsck.auto: No such file or directory
humax#
 
My version of fsck doesn't like the -y option
Code: 
humax# fsck --help
BusyBox v1.12.4 (2012-05-27 00:19:41 KST) multi-call binary
 
Usage: fsck [-ANPRTV] [-C fd] [-t fstype] [fs-options] [filesys...]
 
Check and repair filesystems
 
Options:
        -A      Walk /etc/fstab and check all filesystems
        -N      Don't execute, just show what would be done
        -P      With -A, check filesystems in parallel
        -R      With -A, skip the root filesystem
        -T      Don't show title on startup
        -V      Verbose
        -C n    Write status information to specified filedescriptor
        -t type List of filesystem types to check
 
Running it without -y gives me:

humax# fsck /dev/sda2
fsck (busybox 1.12.4, 2012-05-27 00:19:41 KST)
fsck: fsck.auto: No such file or directory
humax#

Running the help option gives me:

humax# fsck --help
BusyBox v1.12.4 (2012-05-27 00:19:41 KST) multi-call binary
Usage: fsck [-ANPRTV] [-C fd] [-t fstype] [fs-options] [filesys...]
Check and repair filesystems
Options:
-A Walk /etc/fstab and check all filesystems
-N Don't execute, just show what would be done
-P With -A, check filesystems in parallel
-R With -A, skip the root filesystem
-T Don't show title on startup
-V Verbose
-C n Write status information to specified filedescriptor
-t type List of filesystem types to check
humax#
 
No problem, I appreciate the help. I ran the command. It took a couple of hours and aborted. Here's the output:

humax# fsck.ext3 -y /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext3: Superblock invalid, trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
hmx_int_stor: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 548875 has zero dtime. Fix? yes

HTREE directory inode 8241496 has an invalid root node.
Clear HTree index? yes

Inode 8241316 has illegal block(s). Clear? yes

Illegal block #12 (3909155931) in inode 8241316. CLEARED.
Illegal block #13 (1627606199) in inode 8241316. CLEARED.
Illegal block #15 (2708556705) in inode 8241316. CLEARED.
Illegal block #16 (1100500844) in inode 8241316. CLEARED.
Illegal block #17 (3249796446) in inode 8241316. CLEARED.
Illegal block #18 (2396263198) in inode 8241316. CLEARED.
Illegal block #19 (836379930) in inode 8241316. CLEARED.
Illegal block #20 (1453231679) in inode 8241316. CLEARED.
Illegal block #21 (2400001329) in inode 8241316. CLEARED.
Illegal block #22 (1291976854) in inode 8241316. CLEARED.
Illegal block #23 (681477267) in inode 8241316. CLEARED.
Too many illegal blocks in inode 8241316.
Clear inode? yes

Inode 8241404 has illegal block(s). Clear? yes

Illegal block #12 (3093190430) in inode 8241404. CLEARED.
Illegal block #13 (466157639) in inode 8241404. CLEARED.
Illegal block #14 (3170786237) in inode 8241404. CLEARED.
Illegal block #15 (1594086869) in inode 8241404. CLEARED.
Illegal block #17 (3903202398) in inode 8241404. CLEARED.
Illegal block #18 (1619577328) in inode 8241404. CLEARED.
Illegal block #19 (3653113366) in inode 8241404. CLEARED.
Illegal block #20 (3193211390) in inode 8241404. CLEARED.
Illegal block #21 (1557728970) in inode 8241404. CLEARED.
Illegal block #22 (877222491) in inode 8241404. CLEARED.
Illegal block #23 (590919905) in inode 8241404. CLEARED.
Too many illegal blocks in inode 8241404.
Clear inode? yes

Inode 8241410 has illegal block(s). Clear? yes

Illegal block #12 (1408623385) in inode 8241410. CLEARED.
Illegal block #13 (3758545186) in inode 8241410. CLEARED.
Illegal block #14 (3987687934) in inode 8241410. CLEARED.
Illegal block #15 (3398280053) in inode 8241410. CLEARED.
Illegal block #16 (2176179980) in inode 8241410. CLEARED.
Illegal block #17 (2214154399) in inode 8241410. CLEARED.
Illegal block #18 (1958241224) in inode 8241410. CLEARED.
Illegal block #19 (1392490855) in inode 8241410. CLEARED.
Illegal block #20 (2933995985) in inode 8241410. CLEARED.
Illegal block #21 (3058494876) in inode 8241410. CLEARED.
Illegal block #22 (2387189126) in inode 8241410. CLEARED.
Too many illegal blocks in inode 8241410.
Clear inode? yes

Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 7364619: 32973976 32973977 32973978 32973979 32973980 32973981 32977084 32977444 32977493 32977508 32977535 32977541 32977542 32977543 32977544 32977545 32977546 32977547 32977554 32977555 32977556 32977557 32977558 32977559 32977560 32977561 32977562 32977563 32977564 32977565 32977566 32977580 32977610 32977715 32977733 32977810 32977833 32977839 32979255 32979256 32979475 32979619 32979761 32979957 32980009 32980084 32980088 32982195 32982224 32982247 32982256 32982270 32982271 32995330
Multiply-claimed block(s) in inode 8241399: 32977084
Multiply-claimed block(s) in inode 8241400: 32973976 32973977 32973978 32973979 32973980
Multiply-claimed block(s) in inode 8241401: 32973981
Multiply-claimed block(s) in inode 8241403: 32977444
Multiply-claimed block(s) in inode 8241405: 32977493
Multiply-claimed block(s) in inode 8241409: 32977508
Multiply-claimed block(s) in inode 8241411: 32977535
Multiply-claimed block(s) in inode 8241415: 32977541
Multiply-claimed block(s) in inode 8241416: 32977542 32977543 32977544 32977545 32977546
Multiply-claimed block(s) in inode 8241417: 32977547
Multiply-claimed block(s) in inode 8241422: 32977554
Multiply-claimed block(s) in inode 8241423: 32977555
Multiply-claimed block(s) in inode 8241424: 32977556 32977557 32977558 32977559 32977560 32977561 32977562
Multiply-claimed block(s) in inode 8241425: 32977563
Multiply-claimed block(s) in inode 8241426: 32977564
Multiply-claimed block(s) in inode 8241427: 32977565
Multiply-claimed block(s) in inode 8241428: 32977566
Multiply-claimed block(s) in inode 8241431: 32977580
Multiply-claimed block(s) in inode 8241455: 32977610
Multiply-claimed block(s) in inode 8241471: 32977715
Multiply-claimed block(s) in inode 8241481: 32977733
Multiply-claimed block(s) in inode 8241485: 32977810
Multiply-claimed block(s) in inode 8241494: 32977833
Multiply-claimed block(s) in inode 8241496: 32977839 32979255 32979256 32979475 32979619 32979957 32980009
Multiply-claimed block(s) in inode 8241990: 32979761
Multiply-claimed block(s) in inode 8242188: 32980084
Multiply-claimed block(s) in inode 8242192: 32980088
Multiply-claimed block(s) in inode 8242225: 32982195
Multiply-claimed block(s) in inode 8242250: 32982224
Multiply-claimed block(s) in inode 8242272: 32982247
Multiply-claimed block(s) in inode 8242280: 32982256
Multiply-claimed block(s) in inode 8242293: 32982270
Multiply-claimed block(s) in inode 8242294: 32982271
Multiply-claimed block(s) in inode 8242296: 32995330
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
fsck.ext3: Memory allocation failed while retrying to read bitmaps for hmx_int_stor
e2fsck: aborted
humax#
 
The disk does look quite badly corrupt, I am not sure how much you will get back but a filesystem check should complete using the commands below.

Your installation of fix-disk is incomplete. The section in the Wiki which documents the old method using untar should be deleted since it is broken.

You should install CF2.12 first, but don't try to install anything via the basic (or full) web interface until after the disk is fixed.

After the installation telnet into the box and run fix-disk to get into maintenance mode. After reboot type the following at the telnet prompt:

IMPORTANT: Please do not use this method anymore, it only applies to CF 2.12, use a later version instead and ask if you see a similar problem.

Code: 
sed -e '86,91s/^/#/' /bin/fix-disk > /tmp/fix-disk
chmod 755 /tmp/fix-disk
/tmp/fix-disk

Note to others: This will only work with CF 2.12 - do not attempt the above 'sed' command on later versions of firmware.

You may wish to wait for af123. He may be able to include the modified version of fix-disk as a diagnostic but I think you should still install CF 2.12.

Edit: If it has already fixed the missing superblock problem you may find that fix-disk will now run without using the 'sed' commands above. Still need CF2.12 though.

Edit2: Fixed an error in the sed command above.
 
You must log in or register to reply here.
Back
Top