• 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.

Fixdisk caused HDR-FOX T2 to want to reformat the drive

prpr said:
Make sure you mount the drive, not the partition, as you want the partitions unmounted to be able to check/repair.
Click to expand...
Having read up on this again, I don't think it will work, as it will only mount the disk (unpartitioned) or mount the partitions you specify. Neither is what you want to be able to run e2fsck on P2. I think a real Linux boot is much the better option anyway.
Something like System Rescue CD ought to do the job.
 
You need to make sure /dev/sda3 is mounted on to /mnt/hd3 and /dev/sda2 is not mounted to /mnt/hd2, but yes that's about it. You might want -yv options on e2fsck too, and may want to run it under abduco to prevent termination if you get disconnected e.g. abduco -A fix e2fsck -yv /dev/sda2
cat /proc/swaps or free -m are useful to see the state of the swap.
 
prpr said:
You need to make sure /dev/sda3 is mounted on to /mnt/hd3 and /dev/sda2 is not mounted to /mnt/hd2, but yes that's about it. You might want -yv options on e2fsck too, and may want to run it under abduco to prevent termination if you get disconnected e.g. abduco -A fix e2fsck -yv /dev/sda2
cat /proc/swaps or free -m are useful to see the state of the swap.
Click to expand...
Code: 
# df -a
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                22144     22144         0 100% /
proc                         0         0         0   0% /proc
sysfs                        0         0         0   0% /sys
usbfs                        0         0         0   0% /proc/bus/usb
devpts                       0         0         0   0% /dev/pts
tmpfs                    62508        52     62456   0% /tmp
tmpfs                    62508         0     62508   0% /media
/dev/mtdblock1            2048       604      1444  29% /var/lib/humaxtv
/dev/mtdblock2            2048       548      1500  27% /var/lib/humaxtv_backup
/dev/sda1              1035684     54280    928792   6% /mnt/hd1
#

Do I need options for the mount command, or just sudo mount /dev/sda3 /mnt/hd3?
 
Fell at the first hurdle:

Code: 
# 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
 
See the last comment of post #25.
Probably means it's not using the swap at this point.
 
Ah, I thought that that last comment I would be using to monitor swap usage as things progressed.

cat gives me nothing; just deleting and cracking on.
 
e2fsck aborted; looks pretty much the same.

Not sure if too late to check after end of execution, but:
Code: 
# free -m
             total         used         free       shared      buffers
Mem:        125016        11392       113624            0          928
-/+ buffers:              10464       114552
Swap:      2097140          824      2096316

(Went big with 2048 swap-space.)

Log as follows:

Code: 
# abduco -A fix e2fsck -yv /dev/sda2
e2fsck 1.42.13 (17-May-2015)
ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
/usr/lib/ext2/bin/e2fsck: Group descriptors look bad... trying backup blocks...
hmx_int_stor was not cleanly unmounted, check forced.
Resize inode not valid.  Recreate? yes

Pass 1: Checking inodes, blocks, and sizes
Inode 1240688 has illegal block(s).  Clear? yes

Illegal block #2 (4026749441) in inode 1240688.  CLEARED.
Illegal block #4 (4027142657) in inode 1240688.  CLEARED.
Illegal block #5 (2383021157) in inode 1240688.  CLEARED.
Illegal block #6 (1852243972) in inode 1240688.  CLEARED.
Illegal block #7 (4209242121) in inode 1240688.  CLEARED.
Illegal block #9 (1728270849) in inode 1240688.  CLEARED.
Illegal block #10 (2550594278) in inode 1240688.  CLEARED.
Illegal block #11 (4027209992) in inode 1240688.  CLEARED.
Illegal indirect block (1701734160) in inode 1240688.  CLEARED.
Illegal double indirect block (1241712079) in inode 1240688.  CLEARED.
Illegal block #62915596 (3719620111) in inode 1240688.  CLEARED.
Error storing directory block information (inode=1240688, block=0, num=40903952): Memory allocation failed

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
e2fsck: aborted

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
fix: session terminated with exit status 9

Not sure about the next step. Thinking of removing the disk and attaching it to a PC (or maybe the other Hummy) to see if the recordings are still visible; is it just a case of attaching it and navigating through Media->Storage->USB on the other Hummy?

<edit>They have the same encryption key.</edit>
 
aekostas said:
Not sure about the next step.
Click to expand...
Backup and reformat (mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda2).
aekostas said:
Thinking of removing the disk and attaching it to a PC (or maybe the other Hummy) to see if the recordings are still visible
Click to expand...
Depends if it will mount at all. What happens if you try mount /dev/sda2 /mnt/hd2 ? If it does then you may be able to get stuff off it. The filesystem seems quite ill though.
 
Last edited:
prpr said:
Backup and reformat.
Click to expand...
What should I back up if the recordings are gone?
prpr said:
Depends if it will mount at all. What happens if you try mount /dev/sda2 /mnt/hd2 ? If it does then you may be able to get stuff off it. The filesystem seems quite ill though.
Click to expand...
Code: 
# mount /dev/sda2 /mnt/hd2
mount: mounting /dev/sda2 on /mnt/hd2 failed: Invalid argument
 
aekostas said:
What should I back up if the recordings are gone?
Click to expand...
Nothing. Aside from running e2fsck on System Rescue CD as previously mentioned, I'm out of ideas. I think you may have had it.
You've still got to fix the SMART problem as well somehow. A security erase has been mentioned in the past - you'll have to search the forum - but I've never done it and never had much good experience with WD drives. A Green is not really the right drive type either. Might be time to bite the bullet and get a Seagate :devilish:.
 
Just a wee update: the disk arrived, I fitted it in (with my son, extra bonus) and it seems to work. It downloaded the CF, I redeployed the extra packages, I added the two reminders.

System rescue is another story, some things maybe aren’t meant to be.
 
Ok, I overcame the rufus problem with the author's advice. My laptop will not boot from the USB key (it does not output to HDMI while rebooting and the screen is very, very broken), so I will have a go when I get a chance to access another computer.

When successful, I will go for this advice.
 
With the prelims all but over, I managed to get access to the desktop computer. I got it to boot from the System Rescue USB into Linux (findroot). It seems to report some issues, notably "Failed to find /sbin/init on any block device, cannot continue". It seems to see the Humax drive attached via a mains-powered USB dongle. I checked the path and it looked reasonable, but it cannot find the e2fsck command (it cannot even find shutdown).

Am I in the wrong boot option?
 
aekostas said:
With the prelims all but over, I managed to get access to the desktop computer. I got it to boot from the System Rescue USB into Linux (findroot). It seems to report some issues, notably "Failed to find /sbin/init on any block device, cannot continue". It seems to see the Humax drive attached via a mains-powered USB dongle. I checked the path and it looked reasonable, but it cannot find the e2fsck command (it cannot even find shutdown).

Am I in the wrong boot option?
Click to expand...
It should look similar to this when you try booting from the correct media.
 
You must log in or register to reply here.
Back
Top