April 28, 201610 yr I am running an unRAID system that I recently upgraded to V6. Previously I was V5 with reiserfs on all disks. After going to V6, I installed a new drive into the array that was XFS, and started transferring files, empty old disk, reformat as XFS, etc. Basically converting everything to XFS. However, I noticed today that on the SMART reports for all discs with XFS so far, I am seeing RAW Read Error Rates and Seek Error Rates in the millions (70-80 million on RAW read error). Yet on the discs that are still reiserfs (power on time totalling over 4 years on some), I have zero. Can anyone explain why I am seeing this on XFS disks and not reiserfs disks? There are no reallocated sectors, bad blocks, etc on any of the discs. None report any errors. Just playing 5 minutes of a movie off one of the discs results in 7 more seek errors and 900,000 read errors.
April 28, 201610 yr Author This gets more interesting... After looking at 18 discs, the only ones demonstrating this behavior are Seagate disks (2TB and 4TB, various models, standard, green, and NAS). Every single Seagate XFS disc is doing this (6 of them). I have one still Reiserfs and it has zero errors. I don't know if that is just coincidence or something to do with the file system?
April 28, 201610 yr Author After more reading, it looks like this is normal behavior for Seagate drives? It's weird that I have one that doesn't do this, and it just happens to be on reiserfs. But apparently that is just coincidence (it is also an older disk, so maybe old Seagates didn't do that, but newer ones do)...
April 28, 201610 yr Yes, it's just the way Seagate reports the raw error rate. By the very nature of the way a hard disk works there are huge numbers of errors in the raw data that are corrected by the use of error correcting codes. Seagate chooses to report this as a big meaningless number, while other manufacturers ignore it and report an equally meaningless zero. You could say that Seagate is being more honest, perhaps.
Archived
This topic is now archived and is closed to further replies.