Fix-disk "Error - pending sectors but LBA not found"

free30

Member
I get the following message when trying to fix a pending sector in maintenance mode.
"Error - pending sectors but LBA not found"
It then goes no further.
Is there a line command I could use to try and fix it?

Thanks
Code:
humax# fix-disk
Running /bin/fix-disk
Custom firmware version 2.22
 
 
Checking disk sda
 
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted
 
Running short disk self test
 
Pending sector error(s) found
 
LBA has not yet been found
A long test is required - this could take 8 hour(s) 2 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test
 
Error - pending sectors but LBA not found
 
So I ran fix-disk with option -P. Which skips pending section check. Fix disk completed over night.

Now when I run fix-disk is runs without option -P
but I get the error below.

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

So I guess I need to try and fix this sector. I saw a command around somewhere "hdparm --repair-sector."
Fix-disk just finished again with
Code:
Skipped repair of LBA 111550192
hmx_int_stor: e2fsck canceled.
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: y
 
Finished

So should I try hdarm and what options should I use ?
 
OK Thanks. I'll give it a go.:)
but I think I tied it before and it could not, then the option went away.

I think the wiki guide tells you to answer no unless it says delete loop.

Thank you.
 
Seemed to get into a few loops and now I'm back to where I started with Fix-disk only running with option -P
Looks like its one sector in the LBA. Is there anyway to target just this sector or mark it as damaged? Sorry I'm no real expert but I'm trying. This error has been recurring and is causing the odd problem with operating the HDR.

Code:
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
Error at LBA 111550192
Do you wish to attempt repair of the bad block? [Y/N]: y
 
/dev/sda:
re-writing sector 111550192: succeeded
 
Running short disk self test
 
Pending sector error(s) found
 
LBA has not yet been found
A long test is required - this could take 8 hour(s) 2 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test
 
Error - pending sectors but LBA not found
 
Press return to continue:

Thanks
 
That's a last resort if you're trying to keep your disk contents.
Indeed, but it may be the only way to solve the problem as fix-disk is not working. As an alternative, if the sector is not causing playback or other problems, you could just live with it.

If you do decide to go down the security erase route, you will need to copy any programmes you wish to keep to another hard drive, and you will have to reinstall the custom firmware packages etc. afterwards. You could wait a while: one of the forum experts may be able to suggest a more conservative solution.
 
Can you post the self-test log detail from the hard disk diagnostics page in the web interface?
 
A word of advice:

Never run the security erase unless you absolutely have tried everything including re-partioning.
Some manufacturers have flakely implementations and others auto-lock you out of the drive
even if you tell it not to. (Toshiba for example have a history) To unlock a drive can be
a nightmare regardless of what you read on some forums. (Commands simply dont work - sometimes)

I recommend this as a last ditch on the way to the trash can method.
(I doubt it would ever fix anything anyway)
 
The security erase is the last resort, but it did solve a very similar problem for another poster: see link in post #7 for details.
 
Thanks everyone for the advice.

I can not paste my log as it crashes my computer, must be too big.
I'll try and attach a file but it will not let me do it, so I'll add a link soon.

I have not secured erased anything as yet.

The problems I get it it fails to delete things sometime, getting stuck deleting. Also it will not fully power down from time to time.

The disk fix seemed to keep trying to do the same thing. Also I lost connection by my computer going into sleep mode, leaving me having to re-run telnet and stopping fix-disk.

Link to file https://app.box.com/s/isrj9tbpcgwp9tlplbum
 
Back
Top