Since I installed the OS (CentOS 5.3) on my server I am receiving this e-mail daily from cpanel:
S.M.A.R.T Errors on /dev/sda
From Command: /usr/sbin/smartctl -q errorsonly -H -l selftest -l error /dev/sda
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022 066 041 045 Old_age Always In_the_past 34 (0 82 37 33)
I installed hddtemp and it shows between 34 and 36 Celsius for sda at all times. It seems like this have happen in the past, but I don't know how to prevent from getting this information continuously.
What I doubt is that when the DC created this OS image, they had some problem with their HDD and now that shows to me too.
I need your advice.
Is this dangerous? Should I take it seriously or should I ignore it?
If I should ignore it, how to prevent from getting this old irrelevant information again?
But it says Airflow_Temperature_Cel. Not like bad sectors, but it has to do something with the TEMP. I installed hddtemp, the temp it shows is between 34 and 36 celsius which doesn't look bad.
Also, I changed the HDD couple of times. Everytime I reinstall the OS I start getting this error, that is why I think it's OS image problem.
Any help is appreciated.
Not that only I consider it, just
1. the DC changed that HDD 2 times on my request because smart was giving that error. Still, same problem appears.
2. I installed hddtemp. Hddtemp for /dev/sda show between 34 and 36 Celsius. I just setup Munin to generate graph for hddtemp, and after a day or two I will publish here it's graph to see for yourself.
All of this caused me to believe that there is nothing wrong with the drive itself, but somehow, during the OS installation, the image when was created that hdd had temp issue so now the notification is transfered to me.
Thanks for your advice, I will take a look at it.
All I want to achieve is to make sure that the hdd is OK, and to stop this notification for something that happen in the future (which didn't even happen on my server really).