From owner-freebsd-stable@FreeBSD.ORG Tue Jan 17 00:54:12 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A10211065676 for ; Tue, 17 Jan 2012 00:54:12 +0000 (UTC) (envelope-from freebsd-stable@ch.pkts.ca) Received: from bluestreak.microbiology.ubc.ca (bluestreak.microbiology.ubc.ca [137.82.19.154]) by mx1.freebsd.org (Postfix) with ESMTP id 7E55B8FC12 for ; Tue, 17 Jan 2012 00:54:12 +0000 (UTC) Received: from fedora14-x86-64.shechinah.mi.microbiology.ubc.ca ([137.82.128.93]) (authenticated bits=0) by bluestreak.microbiology.ubc.ca (8.14.4/8.14.4) with ESMTP id q0GNxbnr017702 for ; Mon, 16 Jan 2012 15:59:38 -0800 Date: Mon, 16 Jan 2012 16:02:28 -0800 From: freebsd-stable@ch.pkts.ca To: freebsd-stable@freebsd.org Message-ID: <20120116160228.00d4b57f@fedora14-x86-64.shechinah.mi.microbiology.ubc.ca> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bluestreak.microbiology.ubc.ca Subject: "xpt_config still waiting" solved: bad disk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 00:54:12 -0000 Hi.. I just wanted to report a bug with FreeBSD 8.2-RELEASE-p5, as packaged with FreeNAS 8.0.3. A hard drive failed in a strange way, in that it was detected by the computer's BIOS and firmware, but did not reply to information requests from the kernel. The boot process stopped with a series of timeout messages, ending with the message: run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config Removing the affected hard drive fixed the problem; the other 5 identical drives (3TB Hitachi SATA) in the system were unaffected, and that SATA port was tested with a working drive and was ok. So, the problem is hard to reproduce without a drive damaged this particular way, but if you could allow booting to continue after this error is triggered, that'd be helpful for future users. Thanks. -- freebsd-stable@ch.pkts.ca -- just another bug reporter