The actual normalized value depends per drive. So its not 200 - actual sectors reallocated = normalized value. So it could be:Ġ reallocated sectors -> 200 normalized valueġ reallocated sectors -> 200 normalized valueĢ reallocated sectors -> 200 normalized valueģ reallocated sectors -> 200 normalized valueĤ reallocated sectors -> 199 normalized valueĥ reallocated sectors -> 199 normalized valueĦ reallocated sectors -> 199 normalized valueħ reallocated sectors -> 199 normalized valueĨ reallocated sectors -> 198 normalized valueĩ reallocated sectors -> 198 normalized valueĮtc. The drive decides how quickly that 200 number drops down towards the threshold value. Unless you see very high values or it keeps increasing steadily, this usually is not a big issue.Ĭlick to expand.It doesn't work like that. Technically this means the receiving end did receive a corrupted version of the data that was sent by the transmitter the corruption was detected by CRC which means the data is NOT accepted and the request will be sent again. UDMA CRC Error Count = cabling errors if this is higher than 1000 and increasing you have severe cabling problems under 100 does not need to trigger any alarm. Writing to this sector will solve the problem if there was physical damage it will be realloacted by a reserve sector and the Reallocated Sector Count raw value will increase. Current Pending Sector = THE MOST DANGEROUS smart attribute this should ALWAYS BE ZERO or you have severe problems! This can be either weak electric charge with insufficient ECC correction ability -OR- it can be physical damage. Reallocated Sector Count = bad sectors in the past this might have caused problems in the past but does not have to drives replace weak sectors as a precaution which may never have caused any problems. My advice: do not look at the normalized values at all. So if the normalized value is 200 and the threshold value is 100, that would be perfect, while the normalized value being 98 and the threshold being 100 would mean that attribute signals a FAILURE. If the normalized value drops below the THRESHOLD value, that SMART attribute counts as a FAILURE. You have to look at the RAW VALUE instead! For example, a raw value of 0 reallocated sectors might be the equivalent of a 200 normalized value. However, the value 200 you're seeing is a normalized value where the higher = better.
These are VERY DANGEROUS and cause ALOT of problems! These sectors are NO LONGER VISIBLE to your operating system and as such can NEVER cause any more problems.Ĭurrent Pending Sector = ACTIVE VISIBLE bad sectors that CANNOT BE READ but are still visible to the operating system.
Realloacted Sector Count = INVISIBLE bad sectors that have been swapped with reserve sectors.
#Crystaldiskinfo reallocated sectors count how to
Sadly, few people know how to interpret the SMART data, and programs that try to interpret for the user do a poor job at it. It's so sad that SMART is so poorly understood I think SMART tells alot about the drive and is the best drive diagnostic available. more WD Green drives, the only long-term solution is probably to just call all the drives a loss and replace them with something else. And really, since WD will only replace dead WD Green drives with. Since this box is just a backup for another (which is itself running in RAID-Z, so single-disk redundancy), I'm not too worried about having to take it down later for another drive failure. Should I RMA the drive anyway, or is it, in all likelihood, just fine? I'd rather not have to RMA any more drives than necessary, since of the 7 original drives (all bought from NewEgg in a single batch, ~6 months ago) I'm now up to at least 4 RMAed (more if the final two drives scanning now report failures). Now, 3 totally failed the diagnostics for an unrelated reason, but for the 1 that didn't, the WD Diagnostic tool seems perfectly happy with that sector count it reports that the drive passes all tests. Minor issue: at least 4 of the 6 drives give me a SMART result of Reallocated Sector Count: 200.
#Crystaldiskinfo reallocated sectors count full
I mean, why not check and see how they're doing? Especially now that I have a spare machine with internal SATA bays, so a full surface scan takes 6hrs rather than 25hrs like it did with the USB2 dock. There's no data on the array (it's about to become the backup of another FreeNAS box), and I decided to run all 6 WD Green 2TB EADS drives through the WD Data Lifeguard Diagnostics suite. I recently brought down my first FreeNAS box to replace a disk it was reporting as bad.
0 kommentar(er)
