From owner-freebsd-questions@FreeBSD.ORG Fri Dec 28 00:24:40 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0770C16A417 for ; Fri, 28 Dec 2007 00:24:40 +0000 (UTC) (envelope-from kdk@daleco.biz) Received: from ezekiel.daleco.biz (southernuniform.com [66.76.92.18]) by mx1.freebsd.org (Postfix) with ESMTP id A412513C442 for ; Fri, 28 Dec 2007 00:24:39 +0000 (UTC) (envelope-from kdk@daleco.biz) Received: from localhost (localhost [127.0.0.1]) by ezekiel.daleco.biz (8.13.8/8.13.8) with ESMTP id lBS0OapB037625; Thu, 27 Dec 2007 18:24:36 -0600 (CST) (envelope-from kdk@daleco.biz) X-Virus-Scanned: amavisd-new at daleco.biz Received: from ezekiel.daleco.biz ([127.0.0.1]) by localhost (ezekiel.daleco.biz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oC-nUc7GmryE; Thu, 27 Dec 2007 18:24:29 -0600 (CST) Received: from archangel.daleco.biz (dsl.daleco.biz [209.125.108.70]) by ezekiel.daleco.biz (8.13.8/8.13.8) with ESMTP id lBS0ONu7037620; Thu, 27 Dec 2007 18:24:24 -0600 (CST) (envelope-from kdk@daleco.biz) Message-ID: <47744232.4040209@daleco.biz> Date: Thu, 27 Dec 2007 18:24:18 -0600 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.2) Gecko/20070418 SeaMonkey/1.1.1 MIME-Version: 1.0 To: Terry Sposato References: <001201c848d2$0a899560$1f9cc020$@com> In-Reply-To: <001201c848d2$0a899560$1f9cc020$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 'User Questions' Subject: Re: Kernel Log Messages in Security Output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2007 00:24:40 -0000 Terry Sposato wrote: > Hi, > > Just got the following in my security run output and wondering what exactly > it means: > > +++ /tmp/security.zNWgsW2T Fri Dec 28 03:01:05 2007 > +(da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > +(da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error > +(da0:umass-sim1:1:0:0): SCSI Status: Check Condition > +(da0:umass-sim1:1:0:0): NOT READY asc:3a,0 > +(da0:umass-sim1:1:0:0): Medium not present > +(da0:umass-sim1:1:0:0): Unretryable error Opened disk da0 -> 6 > +(da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > +(da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error > +(da0:umass-sim1:1:0:0): SCSI Status: Check Condition > +(da0:umass-sim1:1:0:0): NOT READY asc:3a,0 > +(da0:umass-sim1:1:0:0): Medium not present > +(da0:umass-sim1:1:0:0): Unretryable error Opened disk da0 -> 6 > > If anyone can shed some light on it or point me to some documentation that > would be great. > As far as I can tell the machine is running fine. There is hardware raid > setup with mirroring on this box. > There are no errors on the physical machine itself. > > Regards, > > Terry Does this error also occur at bootup? "Medium not present" seems to indicate something like "I'm trying a CDROM drive but it's empty", or, since this is apparently umass(4) talking, "there's this unformatted thumb drive stuck in my USB slot", or something like that. What, if anything, *is* plugged into the USB ports? What does `camcontrol devlist -v" say? Could maybe also be some unsupported device that *looks* like a umass(4)device, too, but I'm not guru enough to guess much about that. It's just that the error looks a lot like what I described above. Maybe FBSD senses something interesting with the HW Raid? HTH, if grasping at straws is your hobby, Kevin Kinsey -- If your mother knew what you're doing, she'd probably hang her head and cry.