Date: Mon, 25 Apr 2016 09:32:30 -0600 From: Scott Long <scott4long@yahoo.com> To: Dan Langille <dan@langille.org> Cc: freebsd-scsi@freebsd.org Subject: Re: terminated ioc 804b scsi 0 state c xfer 0 Message-ID: <B27E370A-53B2-46B8-8663-F3AA4D389A64@yahoo.com> In-Reply-To: <2E8752E5-76AF-4042-86D9-8C6733658A80@langille.org> References: <2E8752E5-76AF-4042-86D9-8C6733658A80@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Dan, Can you share the entire console log for the uptime? What you=E2=80=99ve = pasted is missing the initial messages of the problem. the = =E2=80=9Cterminated ioc=E2=80=9D messages are likely because the driver = has decided to reset the drive and terminate all outstanding I/O to it. = In other words, they=E2=80=99re red herrings. The reason for the driver = deciding to do the reset is likely earlier in the log. Thanks, Scott > On Apr 24, 2016, at 7:35 AM, Dan Langille <dan@langille.org> wrote: >=20 > More of the pasted output is also at = https://gist.github.com/dlangille/1fa3135334089c6603e2ec5da946d9ae = <https://gist.github.com/dlangille/1fa3135334089c6603e2ec5da946d9ae>; and = added smartctl output. >=20 > I have a FreeBSD 10.2-RELEASE-p14 box in which there is an LSI SAS2008 = card. It's running a zfs root system. >=20 > This morning the system was unresponsive via ssh. Attempts to log in = at the console did not yield a password prompt. >=20 > A power cycle brought the system online. Inspecting = /var/log/messages, I found about 63,000 entries similar to those which = appear below. >=20 > zpool status of all are OK. A scrub is in progress for one pool (since = before this issue arose). da7 is in that pool. >=20 >=20 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8d 90 c6 18 00 00 10 00 length 8192 SMID 774 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b d9 97 70 00 00 20 00 length 16384 SMID 614 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b d9 97 50 00 00 20 00 length 16384 SMID 792 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b d9 97 08 00 00 20 00 length 16384 SMID 974 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b 6f ef 50 00 00 08 00 length 4096 SMID 674 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): WRITE(10). CDB: 2a 00 = 8b 0f a2 48 00 00 18 00 length 12288 SMID 177 terminated ioc 804b scsi 0 = state c xfer 12288 > Apr 24 11:25:55 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = ab 8f a1 38 00 00 08 00 length 4096 SMID 908 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:56 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b d9 97 70 00 00 20 00 length 16384 SMID 376 terminated ioc 804b scsi 0 = state c xfer 0 > Apr 24 11:25:56 knew kernel: (da7:mps1:0:17:0): READ(10). CDB: 28 00 = 8b d9 97 50 00 00 20 00 length 16384 SMID 172 terminated ioc 804b scsi 0 = state c xfer 0 >=20 > Is this a cabling issue? The drive is a SATA device (smartctl output = in the URL above). Anyone familiar with these errors? >=20 > --=20 > Dan Langille - BSDCan / PGCon > dan@langille.org >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to = "freebsd-scsi-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B27E370A-53B2-46B8-8663-F3AA4D389A64>