From owner-freebsd-questions@FreeBSD.ORG Wed Apr 15 15:33:19 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CDF0A72 for ; Wed, 15 Apr 2015 15:33:19 +0000 (UTC) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 40F24A3 for ; Wed, 15 Apr 2015 15:33:19 +0000 (UTC) Received: by wgin8 with SMTP id n8so51039866wgi.0 for ; Wed, 15 Apr 2015 08:33:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Jsb2IE5eN8Z4Wo4n8D3Uamb5+6iO9jhhdybXUJAyO9k=; b=0X1K62525o5fLDNwmOmlZ7kF+tnRKcX+PMK6VdOT3wk1fCnAQDJBx6aqV4++4PZah0 KdqOZPu3KnMHYfnKMwjaOmJsbJCjmr3Kb2K8H4ZcOHLi9ERU3mAv6UTuOK2M3vFZ64dw 96CM1ZmRgXOLXaHmSENwaIjEjXApT7Q6trOccbFr29Kbr4+zKjF/MWY3cyszOzpbiSi+ D0B6D7nRyfJgHmNN1YlkazVm6iKCONNhSczov3qVpV+LhwArr1WRkKC/XT30wWYNTKPA RTpL6ZledQpK4OzECplyMOewIyV2iPQ8AG1T899o0u+UwUg90HemL3HAGxZJbXTeDL+E eCzg== MIME-Version: 1.0 X-Received: by 10.180.96.200 with SMTP id du8mr44145588wib.54.1429111997752; Wed, 15 Apr 2015 08:33:17 -0700 (PDT) Received: by 10.28.21.82 with HTTP; Wed, 15 Apr 2015 08:33:17 -0700 (PDT) In-Reply-To: <05238e5a.6156fafe@fabiankeil.de> References: <552D135F.9010907@FreeBSD.org> <05238e5a.6156fafe@fabiankeil.de> Date: Thu, 16 Apr 2015 01:33:17 +1000 Message-ID: Subject: Re: mountroot prompt with error2, when trying to boot from a single drive in a 2-way mirror From: Yudi V To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 15:33:19 -0000 Hi Fabian, First, what is the recommended image hosting site. I don't think your conclusion is right. If you had a look at the console messages, it looks like the vdev is created but destroyed due to guid mismatch. I will repost the images once I know what service to use. Thanks! Yudi On 4/15/15, Fabian Keil wrote: > yudi v wrote: > >> It's not the BIOS settings, I checked. It picks up the other HDD in the >> mirror and goes through the boot code and then it fails at booting into >> zfs >> root pool. >> The error is: >> >> *Trying to mount root from zfs:osysPool/ROOT/default []... >> *> >> >> * Mounting from zfs:osysPool/ROOT/default failed with error 6.* >> >> it is something to do with the guid mismatch for ada2p3 and ada3p3, not >> sure why it's even trying to compare them as they are the two partitions >> in >> the mirror. >> Please see the below images for the relevant console messages. >> screen1: >> https://drive.google.com/file/d/1Q-F-8kF-Nevn5ijvFXLNuvtJOuRn7ztO2Q/view?usp=sharing >> screen2: >> https://drive.google.com/file/d/1ZGseshS0Uk0cc6Gli_-tywHNXO7sLQ_aVw/view?usp=sharing > > Please note that these resources aren't accessible without allowing > presumably non-free JavaScript from untrustworthy (YMMV) sources. > >> Is anything amiss in the above label info for these two drives? >> I have used these two drives before for testing and reinstalled the os >> and >> recreated the pools. >> Any suggestions on how to fix this. > > The problem could be the result of a known race condition that will prevent > the system from booting if the kernel looks for the root pool before its > vdevs are available. The less disks there are, the "better" the chances > that > ZFS "wins" the race. > > The vfs.mountroot.timeout is ignored for ZFS so the kernel only tries once. > For details and a patch to change this see: > https://lists.freebsd.org/pipermail/freebsd-fs/2015-March/020997.html > > As a workaround you can add a UFS root file system on a disk that > doesn't actually exist to vfs.root.mountfrom. It should be the first > one so you don't hit the spa_namespace_lock deadlock reported in: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198563 > > Fabian > -- Kind regards, Yudi