From owner-freebsd-questions@FreeBSD.ORG  Wed Apr  2 10:48:29 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 11E3CB9F
 for <freebsd-questions@freebsd.org>; Wed,  2 Apr 2014 10:48:29 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id CEA1BB11
 for <freebsd-questions@freebsd.org>; Wed,  2 Apr 2014 10:48:28 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 24B423AE6E
 for <freebsd-questions@freebsd.org>; Wed,  2 Apr 2014 03:48:21 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-questions@freebsd.org
Subject: CAM status: CCB request completed with an error
Date: Wed, 02 Apr 2014 03:48:21 -0700
Message-ID: <87850.1396435701@server1.tristatelogic.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 10:48:29 -0000


What the bleep is a "CCB request", and why would it fail, over and over and over
again, ad infinitum?

Obviously, this has something to do with the second drive in my system, but I
mean seriously (?) Come on!  Did somebody fail to implement some logic that
would recognize when there have been several thousand such errors already
logged and then, you know, avoid filling up /var/log/messages with even more
of these utterly incomprehensible (and thus utterly useless) error messages?


Apr  2 03:40:31 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f ff 0 0 1 0 
Apr  2 03:40:31 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:31 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:40:37 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f ff 0 0 1 0 
Apr  2 03:40:37 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:37 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:40:42 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f ff 0 0 1 0 
Apr  2 03:40:42 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:42 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:40:48 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f ff 0 0 1 0 
Apr  2 03:40:48 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:48 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:40:53 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f ff 0 0 1 0 
Apr  2 03:40:53 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:53 segfault kernel: (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Apr  2 03:40:59 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f fe 0 0 1 0 
Apr  2 03:40:59 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:40:59 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:04 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f fe 0 0 1 0 
Apr  2 03:41:04 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:04 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:10 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f fe 0 0 1 0 
Apr  2 03:41:10 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:10 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:15 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f fe 0 0 1 0 
Apr  2 03:41:15 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:15 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:21 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f fe 0 0 1 0 
Apr  2 03:41:21 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:21 segfault kernel: (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Apr  2 03:41:26 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f c1 0 0 1 0 
Apr  2 03:41:26 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:26 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:31 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f c1 0 0 1 0 
Apr  2 03:41:31 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:31 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:37 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f c1 0 0 1 0 
Apr  2 03:41:37 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:37 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:42 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f c1 0 0 1 0 
Apr  2 03:41:42 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:42 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:48 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f c1 0 0 1 0 
Apr  2 03:41:48 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:48 segfault kernel: (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Apr  2 03:41:53 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f f5 0 0 1 0 
Apr  2 03:41:53 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:53 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:41:59 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f f5 0 0 1 0 
Apr  2 03:41:59 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:41:59 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:42:04 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f f5 0 0 1 0 
Apr  2 03:42:04 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Apr  2 03:42:04 segfault kernel: (da0:umass-sim0:0:0:0): Retrying command
Apr  2 03:42:10 segfault kernel: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1e 6f f5 0 0 1 0 
Apr  2 03:42:10 segfault kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error