From owner-freebsd-fs@FreeBSD.ORG Mon May 17 18:57:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9CA21065678 for ; Mon, 17 May 2010 18:57:11 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from web.nitronet.pl (web.nitronet.pl [195.90.106.5]) by mx1.freebsd.org (Postfix) with ESMTP id A7FD78FC1B for ; Mon, 17 May 2010 18:57:11 +0000 (UTC) Received: from mailnull by web.nitronet.pl with virscan (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OE5V0-000M0l-G8 for freebsd-fs@freebsd.org; Mon, 17 May 2010 20:57:10 +0200 Date: Mon, 17 May 2010 20:57:10 +0200 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <1977671390.20100517205710@nitronet.pl> To: Jeremy Chadwick In-Reply-To: <20100517165352.GA12092@icarus.home.lan> References: <598841171.20100515193024@nitronet.pl> <4BF164DD.4060502@icyb.net.ua> <1554873904.20100517184702@nitronet.pl> <20100517165352.GA12092@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on web.nitronet.pl); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, Andriy Gapon Subject: Re: Root mount from ZFS takes forever...literally. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 18:57:12 -0000 > Are you *absolutely sure* the problem has to do with ZFS? I see you > mention PXE booting...... PXE boot was used as an emergency boot method to fix the problem. > This sounds much like an environment where serial console is set up > incorrectly; kernel messages will be seen up to the final "Mounting > root..." message, but everything past that goes to VGA console (or > serial console, depends on the configuration mishap). I thought so too at first, but then this doesn't explain lack of any disk activity after the message and network unavailability.