HI,
Device: /dev/sdb [SAT], unable to open device
SMART error (FailedOpenDevice) detected on host: host05
Device info:
ST186000NSM0007-2AS1101, S/N:ZJV214CX2, 12.0 TB
I am getting this error after removing the disk SDB out.
Solution I found,
By removing the old disk entries in smartmontools gonna help resolving this issue
sudo systemctl stop smartmontools
sudo killall smartd
Remove the CSV file.
and start the smartmontools
My doubt is , is it safe to execute the above stop, kill commands, are these gonna impact the prod server.
Please confirm. Thanks Thanks
smartmontools is just a daemon to monitor the health of disk drives.
If the disk that you removed was not mounted and/or in use by the system then production should not be affected.
However, it would be a good idea to remove the health monitoring function for the disk to stop the errors continuously being reported.
Does a file:
/etc/smartd.conf
exist?
If so, please post the contents of it.
kamals@gamma05:~$ sudo cat /etc/smartd.conf | grep -v '#'
DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner
All other lines are commented out. Thanks
Edit and insert 'ignore' command before DEVICESCAN:
/dev/sdb -d ignore
DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner
so to prevent smartmontools looking for this disk.
Restart the daemon:
/etc/rc.d/init.d/smartd stop
/etc/rc.d/init.d/smartd start
It shouldn't affect the production box, the SDA. It's only stops scanning the disk SDA for some time, right?
It only stops and then starts (ie, restart) the smartmontools daemon.
May 28 09:40:19 gamma05 systemd[1]: smartd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
May 28 09:40:19 gamma05 systemd[1]: smartd.service: Unit entered failed state.
May 28 09:40:19 gamma05 systemd[1]: smartd.service: Failed with result 'exit-code'.
SO I removed the sdb ignore. paramenter, then restart again.
That is not working