Permanent Deletion « My Humax Forum

My Humax Forum » Freeview HD » HDR FOX T2

Permanent Deletion

(75 posts)

Martin Liddle

special member
Joined: Feb '11
Posts: 4,685
offline

bill3579 - 1 hour ago »
I do not understand how I can send you the file. Extracts for the items you mention are:-
5 Reallocated_Sector_Ct, PO--CK, 8, 100, 100, 036, 100%
9 Power_On_Hours, -O--CK, 9545, 090, 090, 000, 90%
187 Reported_Uncorrect, -O--CK, 14, 086, 086, 000
197 Current_Pending_Sector, -O--C-, 7, 100, 100, 000
198 Offline_Uncorrectable, ----C-, 7, 100, 100, 000

The reallocated sector count is low (up to say a thousand reallocated sectors would be OK). The Current_Pending_Sector and Offline_Uncorrectable are a concern. As I think you suspected, running fix-disk is the next thing to try.

| Sun 7 Feb 2016 21:39:20 #51 |
bill3579

member
Joined: Jan '16
Posts: 37
offline

I have tried Fix Disk. it gets into a loop repeatedly asking if I want to attempt repair of the same bad block. After choosing N, it checks to see if the block is in use

" Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
/dev/sda2: Can't read an inode bitmap while reading inode bitmap
testb: Filesystem not open
Unknown error"

I suppose the last thing left is format. Can I recover some of my recordings first?

| Mon 8 Feb 2016 8:02:16 #52 |
bill3579

member
Joined: Jan '16
Posts: 37
offline

The raw values for the five items are different-
5 Reallocated_Sector_Ct 16 coloured buff
9 Power_On_Hours 9553
187 Reported_Uncorrect 27
197 Current_Pending_Sector 14 coloured orange
198 Offline_Uncorrectable 14 ditto

My efforts appear to have restored the ethernet connectiom

| Mon 8 Feb 2016 9:16:26 #53 |
bill3579

member
Joined: Jan '16
Posts: 37
offline

In the self test logs there are five instances of #1 and 16 of #6

# 1 Short offline Completed: read failure 90% 9553 1805655240

# 6 Short offline Completed: read failure 90% 9553 1805655232

| Mon 8 Feb 2016 9:27:52 #54 |
Martin Liddle

special member
Joined: Feb '11
Posts: 4,685
offline

bill3579 - 3 hours ago »
In the self test logs there are five instances of #1 and 16 of #6
# 1 Short offline Completed: read failure 90% 9553 1805655240
# 6 Short offline Completed: read failure 90% 9553 1805655232

These are linked to the problems reported by attributes 197 and 198. fix-disk will hopefully map out the sectors concerned; if not it should be possible to do it from the command line.

| Mon 8 Feb 2016 12:37:01 #55 |
Owen Smith

special member
Joined: Aug '11
Posts: 184
offline

bill3579 - 5 hours ago »
I have tried Fix Disk. it gets into a loop repeatedly asking if I want to attempt repair of the same bad block. After choosing N, it checks to see if the block is in use
" Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
/dev/sda2: Can't read an inode bitmap while reading inode bitmap
testb: Filesystem not open
Unknown error"
I suppose the last thing left is format. Can I recover some of my recordings first?

Why did you choose N? You should be choosing Y to reallocate the bad block, that's the way to fix them.

| Mon 8 Feb 2016 13:19:33 #56 |
bill3579

member
Joined: Jan '16
Posts: 37
offline

I chose N because the program appeared to be repeating the same thing. I will try again. is that is what I should have done.

| Mon 8 Feb 2016 14:05:46 #57 |
Martin Liddle

special member
Joined: Feb '11
Posts: 4,685
offline

bill3579 - 1 hour ago »
is that is what I should have done.

Yes and worth trying. If you format without fixing the problems then they will remain in place; the filesystem will be fixed for the time being but the problems will come back in due course.

| Mon 8 Feb 2016 15:13:22 #58 |
bill3579

member
Joined: Jan '16
Posts: 37
offline

Fix Disk ran for about two hours, the first 20 min were taken up by what I thought was a loop, then the rest of the action followed. All seemed to go well and the HDR appears to work without any hitches.

However, the HDD test in Settings - Data Storage shows a disk failure, error 81, and a suggestion that format should be used to recover the data storage. The raw values in the drive diagnostics are 16 (buff), 9560, 27, 2 (orange) and 2 (orange).

I will run Fix Disk again

| Mon 8 Feb 2016 16:43:53 #59 |
MontysEvilTwin

special member
Joined: Jan '14
Posts: 240
offline

@bill3579 - take a look at this thread here. Is your disk advanced format (4k physical sectors)? I think it probably is. The current version of fix-disk does not reallocate 4k sectors correctly. One physical 4k sector corresponds to 8 logical sectors: fix disk reallocates the first logical sector only and gets stuck in a loop. To clear the problem, you will have to manually write to the next seven sectors using telnet. It is easier than it sounds. Note where the problem occurs (fix-disk should report the LBA of the bad sector/s) and start from there. What you need to do is described in the above link.

| Mon 8 Feb 2016 17:10:02 #60 |