From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 20:22:58 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDDEF16A420 for ; Mon, 27 Feb 2006 20:22:58 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D1D743D45 for ; Mon, 27 Feb 2006 20:22:58 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.4/8.12.11) with ESMTP id k1RKMsNA001068; Mon, 27 Feb 2006 13:22:54 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.4/8.12.5/Submit) id k1RKMseT001067; Mon, 27 Feb 2006 13:22:54 -0700 (MST) (envelope-from ken) Date: Mon, 27 Feb 2006 13:22:54 -0700 From: "Kenneth D. Merry" To: ticso@cicely.de Message-ID: <20060227202254.GA1016@nargothrond.kdm.org> References: <20060227201644.GR64548@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060227201644.GR64548@cicely12.cicely.de> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.87.1/1305/Mon Feb 27 12:07:49 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: Bernd Walter , freebsd-scsi@freebsd.org Subject: Re: Automatic unit start broken? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 20:22:59 -0000 On Mon, Feb 27, 2006 at 21:16:45 +0100, Bernd Walter wrote: > It seems that FreeBSD doesn't start disks anymore. That's strange, I don't think anything has changed in that area recently. > Disks which delayed start won't get probed by GEOM when they are not > ready when GEOM tries - at least one can delay booting in this case. > Disks which don't startup unless told never get working - I currently > start them manually in rc-scripts and tell GEOM to reprobe, but this > is not always an option, e.g. in case of / drive. > All in all this is very annoying since I have not much options about > changing the disk spin-up policy. What error code do your disks return? You will probably see some console output if GEOM has tried to read metadata off the disk and that initial read fails. If the drive returns 0x04,0x02 ("Logical unit not ready, initializing cmd. required"), CAM will attempt to spin the disk up automatically and retry the command. Ken -- Kenneth Merry ken@FreeBSD.ORG