Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Dec 2007 18:24:18 -0600
From:      Kevin Kinsey <kdk@daleco.biz>
To:        Terry Sposato <terry@sucked-in.com>
Cc:        'User Questions' <freebsd-questions@freebsd.org>
Subject:   Re: Kernel Log Messages in Security Output
Message-ID:  <47744232.4040209@daleco.biz>
In-Reply-To: <001201c848d2$0a899560$1f9cc020$@com>
References:  <001201c848d2$0a899560$1f9cc020$@com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



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