Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 May 2019 03:38:55 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 237701] sysutils/smartmontools: Causing controller resets
Message-ID:  <bug-237701-7788@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 237701
           Summary: sysutils/smartmontools: Causing controller resets
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: danmcgrath.ca@gmail.com
                CC: samm@os2.kiev.ua
             Flags: maintainer-feedback?(samm@os2.kiev.ua)
                CC: samm@os2.kiev.ua

After updating to 2019Q2 (v7.0), I noticed that a pair of Dell PowerEdge 41=
0's
that have smartd running, not start adding some smartctl status to the daily
logs. Unfortunately, it also seems like that are generating a bunch of dmesg
errors recently too:

--
+[6527952] mpt0: request 0xfffffe00012a2610:49251 timed out for ccb
0xfffff8074e2ea000 (req->ccb 0xfffff8074e2ea000)
+[6527952] mpt0: attempting to abort req 0xfffffe00012a2610:49251 function 0
+[6527952] mpt0: request 0xfffffe00012a5888:49256 timed out for ccb
0xfffff800133f2800 (req->ccb 0xfffff800133f2800)
+[6527952] mpt0: request 0xfffffe00012b0d08:49257 timed out for ccb
0xfffff80013452000 (req->ccb 0xfffff80013452000)
+[6527952] mpt0: request 0xfffffe00012aeb30:49262 timed out for ccb
0xfffff802a97d2000 (req->ccb 0xfffff802a97d2000)
+[6527953] mpt0: mpt_wait_req(1) timed out
+[6527953] mpt0: mpt_recover_commands: abort timed-out. Resetting controller
+[6527953] mpt0: EvtLogData: IOCLogInfo: 0x00000000
+[6527953] mpt0:        EvtLogData: Event Data:
+[6527953] mpt0: mpt_cam_event: 0x1
+[6527953] mpt0: completing timedout/aborted req 0xfffffe00012a2610:49251
+[6527953] mpt0: completing timedout/aborted req 0xfffffe00012a5888:49256
+[6527953] mpt0: completing timedout/aborted req 0xfffffe00012b0d08:49257
+[6527953] mpt0: completing timedout/aborted req 0xfffffe00012aeb30:49262
---

Smart itself shows:
  SMART overall-health self-assessment test result: PASSED

but there is an error in the output:
  Read SMART Thresholds failed: Input/output error

I can only assume that whatever it is that is running to add the info to the
daily report is querying the system in a way that appears to possibly be
resetting the disk controller.

Any ideas or suggestions? Thought that I would point it out in case you wer=
en't
aware of the new change affecting older systems.

--=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>