It will be up to Support to judge the situation. An increasing error report is troubling. You can get more information by running Data Lifeguard- WinDLG. Having had difficult experience with a drive that was showing signs of problems, I tend toward immediate replacement, if possible. I take it that the RAID has rebuilt itself more than once? I’m not sure what “turned into virying state” means. It’s a good thing that this is a RAID 1. Rebuilding with a new drive should be straightforward.
It seems unlikely that a drive will be replaced based on raw read error rate.
The first thing to understand that raw read error rate is not a counter, the number you see is not a direct count of read errors or anything like that. I just had a quick look at a few seagates, the raw read error rate value was 56 million. But if you take that and convert it into the proper formatted value (starting at 100, counting down to 0, with a value 6 or below being failed), then it’s at 65. And these drives all jump down to 65 as soon as you turn them on.
Each manufacturer has their own algorithms behind raw read error rate, and in fact manufacturers implement this differently on different models of their drives.
So for one you need to look at the formatted value, because raw value is meaningless. The issue here is that drives have ECC, meaning it can detect and correct read errors on the fly. So when you actually get a “bad sector” it is a sector so damaged that ECC can’t correct it. Now, if you take a WD black in good condition, ECC will be correcting errors all of the time, but the black will give a raw read error rate of 0 i.e. giving no information at all about what’s going on or what overall state the drive is in. Pick up a green and it could be in better condition than the black but it might give an raw read error rate of say 55 million, which is 68/100, which is say 18 higher than the typical for those drives meaning the drive is better than most other greens… Those numbers for the greens are made up, but I was trying to illustrate that you need to be careful when trying to interpret certain smart values for HDD’s, raw read error rate is not something most people should pay much attention to.
If you are worried about the disk (and I can’t tell without the formatted value) do a read test on both of your drives, one of the test that reports read time for each sector. If drive a reads most sectors at say 4ms with a few at 12, but drive b has a ton much higher, then it’s time to look into RMA. But if they give the same results you are wasting your time trying to RMA the drive…
It might be easier if you give a bit of information about what software/tools you are already running. Almost all software that reports smart will take the raw data (the one you supplied) and display it as the formatted value, or along-side the formatted value.
The raid needing verification really depends on the hardware/software running the raid. Again, more info is needed from you on your systems. The thing is the raw read error rate alone will NOT EVER lead to raid verification, if there is a fault with the drive that will lead to a verification of your array it will present itself in other smart values, which are much more prominent and easy to recognise as a problem. If you post the entire set of smart parameters I can take a look.
I use a dos tool that you probably don’t want to go near. HD Tune Pro has a trial period and will do the sort of test you want, HDD scan is free and does it. Google HDDScan and run a verification scan on your drives and compare the map tabs.
P.S. HDD Scan will give formatted SMART readouts too.
It gives feedback if you double click the test being run in the window at the bottom.
I can say though, that there doesn’t appear to be anything wrong with either drive and I would be extremely surprised if WD would even consider replacing the drive based purely off that SMART readout.
That picture is blocked, did it contain the serial number?
I mentioned it before, raw read error rate alone will NOT break the raid. If there are read errors it will ALWAYS present itself in other parameters that are a lot easier to interpret.The raw read error rate you showed does not necessarily mean there is a problem.
Most likely you are using intel ICH raid and if you elaborate on your raid controller I might be able to help you with that.
I’m trying to help you here, if you don’t want it you can try to RMA the disk. But given the data you have presented you could very well find they just send your disk back and charge you for postage…
Regarding the picture, I think it must be validated by WD before you can see it. What it shows is a slow decreasing curve BUT with a hudge gap at 3/4 of the disk array.
Yes I use the Intel sata port on a z77mx-d3h mobo with RST 12.6.0.1028 drivers and 12.6.0.1867 OROM.
Okay, that would indicate there may be a problem with the disk and it should show up as pending sectors or reallocated sectors. Do you have counts in either of these fields on either disk?
Also, check offline uncorrectable. Again, it owuld be easier if you could just post the full set of smart details.