![]() |
SMART Failure - Reallocated_Sector_Ct - LBA 0
Greetings;
I am encountering the problem where, on boot, I am receiving an 'immanent failure' from my HDD. All other usage of the disk seems fine. After doing some research, I figured out that the issue is the 'Reallocated_Sector_Ct' problem, and found this thread seemed to have the answer. Unfortunately, if I understand hard drives correctly, it's my MBR that's broken and I shouldn't be able to type this: Code:
# smartctl -t long /dev/sda Any suggestions or insights? Cheers. |
I had a hard drive that was report errors, and used this program to fix it.
http://hddguru.com/software/HDD-LLF-...l-Format-Tool/ It is a low level formatter, and it is a windows program. It's not strictly low level, but works at a level lower than 'dd' does. It seemed to fix the errors, as they were 'logical' bad sectors instead of 'physical' bad sectors. This will erase data though, and your partition tables and MBR. The suggestion of rewriting a sector again and again won't kill your drive, unless there is mechanical issue. If its your MBR that is bad, then you will lose your MBR, and your ability to boot from the drive. |
There is no such thing as a logical bad sector. A bad sector is always physical. What this program does is initiating a low-level format of the device, which will automatically mark bad sectors as unusable in the disks firmware. This is nothing more than a workaround and in no way fixes the drive.
Rule of thumb: If SMART reports an error the first thing to do is to backup your data that isn't currently backed up. Then download the disk manufacturer's diagnosis tool and check the disk. Most likely it will be reported as faulty, since SMART is usually correct when it comes to errors. For me it looks like that you need a replacement for that disk. |
Do you have any errors in dmesg? If there are bad sectors and the OS cannot read them, it logs the error in dmesg.
Example: Code:
[187442.852700] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x0 |
Post the output of 'smartctl -A /dev/sda'.
However, the long test failed so this means that the drive is failing, so backup all your data if you haven't already done so. |
Thanks for the replies :)
I'm not using this machine for anything particularly critical, so data loss isn't too much of a contributing factor; but if I can avoid a low-level solution, I'll try. I know this is an old machine (It's an Aspire 3500, complete with 'Designed for Windows XP' sticker), so it's quite possible that the drive is just old; but what I want to do is try and clear these bad sectors and monitor if and how quickly more bad sectors appear before consigning to a new HDD. The SMART errors: Code:
smartctl 6.0 2012-10-10 r3643 [i686-linux-3.7.3-101.fc17.i686] (local build) Code:
# dmesg | grep error Again, thanks for the replies. |
The drive is near death in many ways. It has used almost all of its spare sectors
Quote:
Code:
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always Code:
4 Start_Stop_Count 0x0032 001 001 000 Old_age Always - 987627 The reason for the anomalous test result is probably that the test is working with blocks larger than a single sector and is indicating a failure somewhere in the first such block. If you really want to know which sector is bad, you can use hdparm with the "--read-sector" option to read single sectors without confusion from the OS readahead: Code:
for N in {1..1000}; do |
I agree with rknichols, the drive will fail imminently. Backup all your stuff now if you have anything important.
|
All times are GMT -5. The time now is 05:50 AM. |