Hello,
i recently had to replace a Harddisk due to a bad sector count. So i got myself a new 4Tb WD Red drive, installed it and the raid synced without any problems.
Icurrently have 5 HDDs installed.
2x WD Red 4TB (Raid 1)
2x WD Red 3Tb (Raid1)
1x Seagte 80Gb (System Disk)
Yesterday the system sent me an email saying the ATA Error count from the new disk has incerased from 0 to 1. I tried to investigate the issui by using "smartctl -dev/sdb" and it confirmed the error.
The other SMART Values are excellent so i decied to take a look at the other disks. And heres the thing: Most of the times when i try to read the SMART values from within the omv gui..the ATA error count increases by 1. After my testing i now have abot 20 ATA Errors on every device. However when i use the smartclt -a on the console, the error count keeps the same and is not increasing. I read through a lot of other forum posts bit i reaqlly cant imagin that all 4 Drives are bad or that all 4 Sata cables are somehow damaged. Especially since the error or only increasing when reading the SMART data from within the GUI.
Regarding to the smart values from smartctl the errors always occur when reading or writing Smart logs.
Here is one example output:
- When the command that caused the error occurred, the device was active or idle.
- After command completion occurred, registers were:
- ER ST SC SN CL CH DH
- -- -- -- -- -- -- --
- 04 51 01 00 00 00 00 Error: ABRT
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- --------------------------------------
- b0 d5 01 e1 4f c2 00 08 00:21:46.061 SMART READ LOG
- b0 d6 01 e0 4f c2 00 08 00:21:46.061 SMART WRITE LOG
- b0 d6 01 e0 4f c2 00 08 00:21:46.028 SMART WRITE LOG
- b0 d5 01 e0 4f c2 00 08 00:21:46.028 SMART READ LOG
I recently (2 weeks ago) updated from omv 3x to omv4. May this the reason? Regarding to the forum I may not be the only one with this problems. However i was not able to find a solution.
Du you guys have any Idea whats causing the problem? Is far as i can tell there are noe errors in the syslog.
Thanks