VMware Cloud Community
matthiaslink77
Contributor
Contributor

Disable smart detection for specific drives

Hello,

I am trying to disable smart detection for the internal usb thumb drive ESXI has been installed to, as well as for the HP SmartArray Controller, as syslog reports both drivers not to be smart capable.

Every 30 minutes I get these annoying messages with catagory emergency in my syslog-server:

libsmartsata: Not an ATA SMART device:mpx.vmhba32:C0:T0:L0

libsmartsata: Not an ATA SMART device:naa.600508b1001c88c15725091c52c742d7

I already tried to modify the /usr/lib/vmware/vm-support/bin/smartinfo.sh script, but after a reboot, everything is back at default contents, so no chance here.

An /etc/smartd.conf does not exist, so how may I disable these two drivers from being checked all the time?

Thanks a lot and

best regards,

Matthias.

10 Replies
randm
Contributor
Contributor

I am getting the same problem for the internal MicroSD card in my HP MicroServer which I use to boot up ESXI. Does anyone have a solution to this (i.e. disable checking the internal MicroSD card)?

0 Kudos
hdcd
Contributor
Contributor

Did you ever find a solution to this? Didn't have any problem until I updated the blades with the 6.x 1/7/2015 update. Thanks.

VMWareJason
Contributor
Contributor

same issue here. Every 30 minutes. any suggestions?

smartd: libsmartsata: SG_IO ioctl ret:0 status:2 host_status:0 driver_status:0

0 Kudos
vrangler
Contributor
Contributor

Hi,

It's an old thread.

But esxi 6.5 is still doing it. And not even about a device. It's logging a syslog emergency repeatedly to tell me it is done checking: 'smartd: libsmartsata: closing fd:5' 😕

This turns up in my root consoles on the syslog server and everything.

Can this particular message be set to info or even debug, in some way? As it is not very informative at all.

Thanks..

0 Kudos
ApexIT
Contributor
Contributor

Anyone fix this issue of smart detection?

Error:

smartd: libsmartsata: SG_IO ioctl ret:0 status:2 host_status:0 driver_status:0

Running esxi 6.5.0 5310538 on Dell servers.

0 Kudos
ApexIT
Contributor
Contributor

went to support, will let you know.

0 Kudos
alicytec
Contributor
Contributor

I am having the same issue

Anyone manage to fix this?

0 Kudos
threeonesix
Contributor
Contributor

ditto

0 Kudos
dodexahedron
Contributor
Contributor

If you do not want to monitor SMART status of any local or remote devices and know what it means to stop doing so, here is a kb article that tells you how to do it: VMware Knowledge Base

Under the Resolution heading, it is option 1.

As of ESXi 6.5 U1, the procedure listed there works:

Option 1

Disable the SMART daemon (smartd). However, this affects local data capture of SMART data for internal drives.

Note: VMware recommends against disabling smartd if possible.

To stop and disable smartd on an ESXi Host:

  1. Connect to the ESXi host through an SSH or a local console session using root credentials. For more information, see Using ESXi Shell in ESXi 5.x and 6.0 (2004746).
  2. Stop the smartd service using this command:

    /etc/init.d/smartd stop

  3. Disable the service using this command:

    chkconfig smartd off

This applies for local devices as well as remote iSCSI devices that do not support SMART monitoring, so, while the linked article may not perfectly match your hardware, that's still what SCSI command 0x85 is - an ATA passthrough command that was not supported by the end device. You may also see this if your array tries to issue UNMAP to an older SATA SSD that does not support TRIM.

0 Kudos
kottapar
Contributor
Contributor

We're also having the same problem with this message popping up right whenever I'm editing a logstash filter or something else. Finally after some looking around and the suggestion above not to disable smartd, we supressed it from being printed to console on the syslog server.

Ours is a RHEL server so I edited the /etc/systemd/journald.conf and uncommented

"ForwardToWall=yes" and changed it to "ForwardToWall=no".

I've been monitoring it for the last one hour and it looks like this fixed it. I found the fix at https://stackoverflow.com/questions/41444630/how-to-avoid-broadcast-messages-from-syslog-printed-on-...

Edit : I've also had to comment "*.emerg  :Omusrmsg:*" in /etc/rsyslog.conf and restart rsyslog. Now it completely stopped them from popping up on the console. Hope this helps.

0 Kudos