Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 May 2019 11:42:39 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 237701] sysutils/smartmontools: Causing controller resets
Message-ID:  <bug-237701-7788-hV9yROzUmT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-237701-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-237701-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237701

--- Comment #1 from Dan McGrath <danmcgrath.ca@gmail.com> ---
It seems that the system has been much better since removing the line:
  daily_status_smart_devices=3D"...."

from the /etc/periodic.conf. I suspect that past issues with these systems
(Zabbix alerts during maintenance times) may have actually been coming from=
 IO
stall outs during the periodic runs that were invoking the smart status.

Interestingly enough, running `smartctl -i /dev/da#` alone doesn't cause the
problems, but it was only a recent update to the smartmontools that started=
 to
populate the daily logs, which in turn caused the errors, that started to
reveal a potentially old bug.

For some extra background, these R410's have HW Raid capable HBA cards in t=
hem,
but were configured as non raid, which appeared to pass it through fine (at
least enough to give me output in smartctl.=20

My guess is smartctl doesn't like something about these particular devices.=
 The
are technically in IR mode, not IT, yet allow SMART to be queried. Maybe th=
ere
is some issue with this? I don't know, you guys are the experts, so I can o=
nly
give some historical insights and technical info.

Hope it helps!

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237701-7788-hV9yROzUmT>