Tag Info

Hot answers tagged

29

While S.M.A.R.T. certainly doesn't predict all failures, I worked in a computer repair shop for several years, and many times a S.M.A.R.T. error message was the first indication that a failure was about to occur, allowing me to save the customer's data before the drive died. The technology itself does not stress the drive, it just keeps track of a number ...


21

Yes, they have it, and yes, it's useful. Flash drives do develop errors over time, usually in the form of bad flash blocks - not unlike bad sectors in regular hard drives. Just like regular hard drives, the drive controller keeps track of these bad blocks and re-maps them to 'extra' blocks that were saved for this purpose. Whenever the computer requests ...


18

Sounds very much like the drives are doing SMART scrubbing (automatic online testing). smartctl -a /dev/hdx should confirm the configuration with: Auto Offline Data Collection: Enabled. Disable with: smartctl --offlineauto=off /dev/hdx It could be something else too...


13

Drives, like most components, have a bathtub curve failure rate. They fail a lot in the beginning, have a relatively low failure rate in the middle, and then fail a lot as they reach the end of their life. Just as the whole drive follows this curve, particular areas of the disk will also follow this curve. You'll see a lot of sector re-allocations in the ...


13

You don't. You go buy another disk to replace it unless you just really like losing data.


12

Re-reading Google's paper on the subject, "Failure Trends in a Large Disk Drive Population", I think I can safely say that Adam's answer is incorrect. In their analysis of an extremely massive population of drives, roughly 9% had non-zero reallocation counts. The telling quote is this: After their first reallocation, drives are over 14 times more ...


10

According to Steve Gibson of Spinrite fame, SMART values have to be taken over time, not as instantaneous readings. That means, a value of 47 isn't necessarily bad if the value has been 47 for months. However if the value was 42 an hour ago, and its climbing rapidly, then that means the drive is experiencing difficulty accessing part of the data and may soon ...


10

You could try hdparm --write-sector <LBA> /dev/ice. I don't know any other way of doing this - you need to manually convert the LBA into filesystem blocks (as you've already found)


10

I used to write disk firmware for WD, and I once wrote the firmware which reassigned bad blocks. First, most bad blocks are detected on reads, not writes. Writes are done blindly, meaning the data is written without being checked. Thus on a write if the media is bad, you won't know it until the host does a read to that sector. There is a small part of the ...


10

A good, but not infallible, way of checking any drive health is to check the SMART attributes. Below is the SMART attribute set for an Intel X25-M G2 160GB disk, taken using smartctl v5.41. (The version is important, earlier versions of smartctl had different attribute-name mappings, and didn't actually correctly understand the specific table for this ...


10

It's not about to die.. It's already dead. Replace it ASAP, and restore from backups if you lose any data.


8

Yes, it definitely looks like a hardware fault. I have had multiple Barracuda ES / ES.2 drives go..including 12 out of 16 across two servers. I don't think the smartmontools is sufficient for warranty replacement. Go to Seagate's website and download their SeaTools bootable CD. When/if it determines the drive has a fault, it will give you a warranty code. ...


8

Yes, your hard disk is failing. I'd replace it relatively quickly.


7

I'm not sure what you mean. You can ask the disk to run a (SMART) self-test. This usually takes some time, and is somewhat stressful for the disk. I'd not recommend to run it more than once in a long while. On the other hand, you can check the SMART status from the disk. In other words, this means "read the SMART meters from the disk". This operation is ...


7

The battery will degrade over time, eventually getting marked as "failed" by the controller. At this point, it can no longer guarantee that cached writes will be stored correctly on dish, so it will turn off its cache layer, significantly decreasing performance.


7

The life of a controller battery on HP Smart Arrays is ~3 years. The purpose of the array battery is to provide power protection for the controller's write cache. The is a data protection mechanism that allows writes to the cache to be acknowledged by a lower-latency cache versus waiting on the underlying disks. Typically, failure of this battery ...


6

I'd like to thank you for the advice and share some of the details that I've got from experiments. In short, there is no easy way to get the list of reallocated sectors and even statistical methods of mapping the disk are heavily encumbered by the need to play against the logic of the firmware. To test the drive I ran badblocks -wv with the default ...


6

The check_ide_smart plugin is part of the standard nagios plugins group. Despite the "ide" part of the name, it uses smartctl to check any drive that smartctl supports. It can return nagios-suitable output, e.g: $ ./check_ide_smart -n -d /dev/sda OK - Operational (17/17 tests passed) Or the full SMART status: $ ./check_ide_smart -d /dev/sda Id= 1, ...


6

Not easily. the sector reallocation happens inside the drive (which is why it's reported to you by SMART) -- your filesystem has no clue it's happening. As far as it's concerned sector 12345 is still sector 12345, that's what it asks the drive for. Internally the drive knows 12345 is now 67890 and returns the contents of the remapped sector. The only way I ...


6

This is far from abnormal. This is my server's HDD temperatures over the past year: They are correlated, sure, but one runs about 7C hotter than the other. In my case I'm fairly sure it's down to airflow differences inside the case: one catches more of the flow from the case fan than the other. In the past, when I've swapped them round, the lines have ...


5

SMART overall-health self-assessment test result: FAILED! That part is not interpreted by smartctl (assuming I understand correctly, of course) - that drive has told smartctl that is isn't happy with its current state (for whatever reason) and smartctl is just echoing that warning to you. Even if it is misinterpreting the spin-up time reading, I don't ...


5

I had a spare drive that I can still boot from that fails SMART checks every boot and requires a soft reset, has for years, but it's just a dump, not a system disk! So although SMART errors can persist for a long time they should ALWAYS be heeded in production, as the risks heavily outweigh the cost, time and data integrity benefits. Google studied 100,00 ...


5

I would guess that the answer to both questions is no, because SMART is handled internally by the disk and should be independent of the rest of the system.


5

Do the replace if you can. On the other hand these are 'only' read errors which is not that bad. If you write to that sector then you can be only sure if it has defects. I would run the vendors utility to check (they also run smart tests) if it has problems. They usually make bootable cds available. You can and should run a self test which you can do from ...


5

In my experience (20 years in operating servers, must have handled about 5.000 disks in all the servers I have dealt with) SMART is useful but no panacea. If you get SMART errors replace the disk asap. Chances hare very high that with 4-8 weeks the disk will have serious issues. (The Google study frequently mentioned in this regard correlates very nicely ...


5

This is SMART counter. Reallocated sectors are not exposed to the software. Physically, all drives have spare space reserve for reallocation, so, HDD is internally doing all the things, process is transparent to the outside world. While reallocated sector count is low enough - you don't have to worry about it, performance decrease won't be significant. ...


4

Maybe this will suit your needs: Quoted from this link: You'll need the SmartMonTools package and use *check_smart.pl* perl script (nagios plugin) to check hard drive health by running S.M.A.R.T. self-tests using the smartctl command, add to your snmpd.conf: exec CheckSmart /path/to/check_smart.pl -t -d /dev/hda


4

You can try build-in check_ide_smart


4

All drives are the same model and have been bought together. This is a ticking bomb. Based on both the message from SMART and the quote above, you should change disks right away. Since the drives have been bought together and are the same model, they will probably have the same weaknesses, and probably all fail simultaneously under the same ...


4

I would probably use nagios with passive checks if I could not set a nagios server on the remote network. On enterprise server hardware you can use tools like the insight manager (HP), opemange (dell) and have the passive checks query those tools. check_openmanage does that for dell servers and check_hpasm for HP hardware. With those tools you monitor all ...



Only top voted, non community-wiki answers of a minimum length are eligible