The best indicator I know of some type of mechanical issue is the multi zone error. But their are heads and actually motors and other parts that are not sector specific. We tend to think the sum total of disk problems are sector issues. I think this is a good example of the limitations of smart. And nothing is now reallocated or pending. The pending sector is returned to service. On the next parity check, it generated some 500 consecutive sector read errors. We had a situation where a sector was marked pending. I think that's true, as far as it goes, but implies that the outcome was somehow purposeful and "normal", and neither are true. I'm a bit concerned with shuffling drives around into different physical positions (ie: new parity into old parity physical position and old parity into removed drives physical position) and then performing the parity swap.Whilst my reading seems to indicate this is ok, I wonder whether it will lead to some additional risk that I can avoid. The reason for this is that if I put the new parity drive in place of the drive to be removed it's not on the motherboard but rather on my LSI HBA and I'd prefer it be connected to the Motherboard port. With two clean parity checks now, I think it's reasonable to assume that the array is ok.Īs there are no further errors and two parity checks have completed succesfully, I'm leaning towards doing the replacement in two steps.id: replace/rebuild parity (run parity check) and then replace drive 6 rather than do a parity swap. I'd expect the Reallocated Sector Count should be 1. To me the counters seem to contradict each other. The Parity check finished with 0 errors and the error count against all drives is 0, so looks like reads are ok. My theory is that continuing to mess with a bad sector is like picking a scab, and the problem gets bigger and bigger. I believe we'd start to see the reallocated sectors stop increasing if drives were more proactive in taking sectors out of service. In fact, it should try to reallocate the sectors around it as well. If the drive detects a sector as bad, it should not around with it when it has the opportunity to remap. A freshly written sector may appear fine right after writing, but if that spot is weak, a day/week/month later it can be unreadable again. I think this is an incredibly poor decision on the part of firmware makers IMO. If it did, it will unmark it as pending and allow it to stay in service. When a pending sector gets written to, the drive will test to see if the write worked or not. Have seen them accompanying other problems and see them as a sign of trouble, especially if they are new. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUEĢ00 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |