Seagate SAS drive temps not showing

[Martyy2k]

Hello, everyone, i have been using freenas/TrueNAS for a few years now and just love it. I have noticed lately after swapping out my Seagate ES drives for newer ES.3 ones that my disk temps are not showing for neither of the 7 disks installed (6 as raidZ2 and 1 as hot spare) In shell using smartctl -a /dev/da* i cannot get readings of temps on either one as seen in the reports (showing 0).
My system is virtualized but using passthrough for the controller, so all disk are directly available to only TrueNAS, system works perfectly well, no errors, no issues and it's been 3 years.

I also have my test centOS 7 VM that has access to the disks the same way TrueNAS does as it has access to the passthrough disks ( running either TrueNAS or shutting it down and running centos 7).

If i run same command in centos 7, i get full disk temp readings.
I am not an expert, but i tested to see if it was disk issues or something else. Here are comparison pictures showing shells, info and serials to confirm they are same disk(s), read of same passed through device in same configuration. Both CentOS and TrueNAS are virtualized.

Any insight form you knowledgeable folks is appreciated.

Many thanks!
Marty

 

[Mannekino]

If I remember correctly I read a comment earlier this week from @Chris Moore that he also had difficulty reading S.M.A.R.T. data from SAS drives and had given up on it.

 

[Martyy2k]

Hi Mannekino, i can read from my centos 7 instance and i noticed it uses Linux version r4883 [x86_64-linux-3.10.0-1160.11.1.el7.x86_64]. I managed to find the versions on smartmontool.org but am not sure how to compare them to see what might be omitted, removed or changes between versions, as i also just took notice that TrueNAS is r5022. Maybe something has been changed the has broken the functionality? Like i said, i am no expert, i am just trying to narrow down the issue as best i can. Having checked on both freebsd(TrueNAS) and CentOS 7, i know that my drives are reporting, so now its pointing towards a script change not parsing correctly the drives in newer version.

 

[jgreco]

SMART isn't guaranteed to be available on SAS drives; it is a feature that was designed for SATA. There are apparently SAS drives that do implement some version of SMART. It's interesting if you can read it on Linux but not FreeBSD. I would have expected that to be the same, since you're using the same tool...

 

[Martyy2k]

SMART isn't guaranteed to be available on SAS drives; it is a feature that was designed for SATA. There are apparently SAS drives that do implement some version of SMART. It's interesting if you can read it on Linux but not FreeBSD. I would have expected that to be the same, since you're using the same tool...

Hi jgreco, yes indeed, exactly my point! Same tool, 2 different OS's and same SAS drives! One works, other does not. Distinctions I found is versions revisions. Here is another screen shot from a CentOS 8 test, same thing as FreeBSD, it shows temps as 0 and does not dispplay any other data like it did in r4883. This revision shown is r5049. all test parameters are same, all OS's are VM's, full passthrough and same command: smartctl -a /dev/*** is used.

So I really believe something between r4883 and r5049 is breaking in FreeBSD and even in Linux versions. I do not know how to compare scripts and programing, far from it, but if someone can help out that is good at this maybe we can resolve it. I strongly think its a scripting/programing change in the newer revisions that is causing this bad parsing of SMART data in SAS drives as they worked great in revision r4883, check previos posts screen shots and you can see all the shown data.

I would be great to put the finger on the problem and be able to bring a solution.

regards,

Marty

 

[Martyy2k]

So folks, here is FreeNAS 11.1 U5 screenshots, i reinstalled it to test smartmontools:




See what I mean? It was using smartmontools r4083 and SAS drives report perfectly! This is still on same setup as always. So as soon as it was upgraded the smartmontools revision went to r5022 and then, disks report 0c instead of actual tempsof 33c.

 

[jgreco]

I would suggest submitting a bug report, focusing NOT on temperatures (which are known to be flaky) but rather on the SMART issue, with a note that it worked previously.

 

[Martyy2k]

I would suggest submitting a bug report, focusing NOT on temperatures (which are known to be flaky) but rather on the SMART issue, with a note that it worked previously.

OK, I will try, i cannot login to try and submit this issue. I thought maybe try here in forums as many are very good in programming and scripts and all, maybe someone could have taken a look to see if any modifications made could have caused the issues between R4883 and R5022.

Thanks!

 

[Johnnie Black]

It's a smatmontools bug, it should be fixed in a future release.

#1331 (smartctl 7.1 doesn't show attributes on Seagate SAS drives but 6.6 does) – smartmontools

www.smartmontools.org

Changeset 5074 – smartmontools

www.smartmontools.org

 

[Martyy2k]

It's a smatmontools bug, it should be fixed in a future release.

#1331 (smartctl 7.1 doesn't show attributes on Seagate SAS drives but 6.6 does) – smartmontools

www.smartmontools.org

Changeset 5074 – smartmontools

www.smartmontools.org

Thank you Johnnie for those links, its a great learning experience from this community to see the reporting, testing and narrowing down the bugs. I am not familiar with the process to report and search for these bug reports and all. I am learning some new stuff i suppose! At least i managed to track back and reproduce the issues and make sure it was out there.

thanks a bunch!

Marty