SEAGATE - S.M.A.R.T high value
![SEAGATE - S.M.A.R.T high value](/content/images/size/w1200/2019/05/iwh-row1-logo-629x237.png)
Hello, I just want to share my story behind the crazy smart info back from the smartctl command for my SEAGATE drives.
I have 3 IRONWOLF 6 TB version and I was scared about data loss. So I just try to read the S.M.A.R.T behind my drives.
First I did a smartctl --scan to scan all the drives from my controller (Dell H700)
![](https://blog.lbdg.me/content/images/2019/05/image-4.png)
I started with the drive 4, which is my WD RED
smartctl -ad megaraid,4 /dev/bus/2
The drive is perfectly detected, as you can see :
![](https://blog.lbdg.me/content/images/2019/05/putty_2019-05-03_19-12-22.png)
And the S.M.A.R.T infos are pretty good considering all the years I've used it.
![](https://blog.lbdg.me/content/images/2019/05/putty_2019-05-03_19-12-32.png)
SEAGATE
I continue my tests, with the IRONWOLF drives, command :
smartctl -ad megaraid,0 /dev/bus/2
![](https://blog.lbdg.me/content/images/2019/05/putty_2019-05-03_19-15-53.png)
This is the correct device, it seems everything is okay, so I read the S.M.A.R.T values
![](https://blog.lbdg.me/content/images/2019/05/image-5.png)
And WOW ! It looks like 2 450 112 642 seek error rate and 174 569 605 raw read error.
It was so crazy I couldn’t believe it. So I’ve looked a bit into it and found these informations on a forum
![](https://blog.lbdg.me/content/images/2019/05/image-6.png)
I dig into the SEAGATE S.M.A.R.T values and read about 48 bits storage. I read the man of smartctl and find a way to convert values to another format, with the -v option
![](https://blog.lbdg.me/content/images/2019/05/image-7.png)
I’ve checked a lot of formats and finally found the good one :
smartctl -ad megaraid,0 -v 1,raw48:54 /dev/bus/2
The first parameter apply the conversion to the field 1
I re-check my S.M.A.R.T value for the ID 1 and ... I have no raw read error on this disk
![](https://blog.lbdg.me/content/images/2019/05/image-9.png)
And my 4 295 032 833 Command Timeout ...
![](https://blog.lbdg.me/content/images/2019/05/image-10.png)
... Was 1 timeout
![](https://blog.lbdg.me/content/images/2019/05/putty_2019-05-03_19-25-55.png)