Wikipedia's list of known SMART attributes lists 0xB8 as End-to-End error / IOEDC described as:
This attribute is a part of Hewlett-Packard's SMART IV technology, as well as part of other vendors' IO Error Detection and Correction schemas, and it contains a count of parity errors which occur in the data path to the media via the drive's cache RAM.
(I was unable to immediately find an official reference of SMART attributes for your particular drive, so will assume that the above is correct. You may want to spend a bit of time searching for a specific reference which will tell you exactly what the meaning (and interpretation of the raw value) of SMART attribute 0xB8 is on your particular drive, to verify the below. Seagate should be making such a reference available.)
Parity errors can be caused by hardware being operated too close to the limit of its operational envelope (overclocking), but a far more plausible explanation would appear to be poor connectivity somewhere.
The first thing I would do is check the cabling. Replace the cabling from the controller all the way to that drive (including any breakout cables) and see if the problem goes away.
Note that parity errors are non-critical. This is a parity error which is being detected, and thus corrected for (most likely by throwing out the damaged data and requesting a re-read from the original source). SMART may read it as FAILED because the drive has seen too many such errors, but at most, detected parity errors degrade performance. As long as this is the only error that the disk is reporting, I wouldn't worry too much.
It's also worth noting that the Seagate DM series drives are a poor fit in general for RAID because they don't support SCTERC. As long as they are working properly this won't be a problem, but if you hit an unreadable sector, the drive is going to keep trying to read it for a very long time even though (depending on your RAID level) redundancy may exist elsewhere to allow it to be reconstructed much quicker. That applies to any RAID level other than RAID 0 (which is striping without mirroring or parity).
so the drive is connected to a pcie raid controller but is not set as raid, just as legacy. the sata cable I already tried to replace, but not the power cable, maybe I should do that. Any idea about the access sound the disk makes? This is not every time but a lot of times, see no logic in it.. – Kleajmp – 2014-10-22T13:01:08.140