From owner-freebsd-questions@freebsd.org Wed Sep 12 02:00:40 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 904C510A5CC1 for ; Wed, 12 Sep 2018 02:00:40 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29F0A9438E for ; Wed, 12 Sep 2018 02:00:40 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-ua1-x932.google.com with SMTP id f4-v6so291440uao.10 for ; Tue, 11 Sep 2018 19:00:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XTUV1F/16F63MWaDF2XWqC8b1GSMFZc8us7YAaiZMKw=; b=cKZRmpvz+DUIDX+RkMnaSU8gABDDiuPou8m7R2xGn2JfYNZQWprRoTqoUf79TxVbBh bd1t/IE3zSr18KzHOjYMf/28KUQZm6YzwjM9uNIQLOv0tHHVvberHsDX6pY993krVZVh QbV70bHUL0ewt+/kfqYzAMY0O1ARfAKPS1chxI4GuuAKVinMPApC8YGfDVve5IMsgkfs YyUq9B2bRXL2iqkAIIYJ5EgqUhttuRKBvtH6Am+0b8Zmaau6lj7MfXwmyos2XXrPgOwr FEt2GNIca+6cpyhizcKVrfTPhVXpdIR8VubqhnOc2gNB05h37sX/jTaFzRO9VSmfXwqw +7ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XTUV1F/16F63MWaDF2XWqC8b1GSMFZc8us7YAaiZMKw=; b=bLcGEs/pR1Gw8ehxAXPeJ5ZdwqS8B/lMEOwuzWfKFu+bXMD0Hj9zPbluCNoCUfM8rg RjYGMcd9s/zygc5U0d60s6Z4iWcG4gw01ZMtRI1aD+JELWAnrkIgwGE/0t2V+/MqDONX UyFhO78t+t6mZZqHd/640v2yMcOD9bhsQi7Wu/qY4K09sNIhTpr/HXgW7KgFKy3fhY+H B8wza990Osi9sUiUtEcTZgAx9i9ngPBbReTmDw2BRL8QwQBaZFnzfxSrt1/U+99u8wG3 SVmIg7iixihdztDVYj5wsfHDdJSRBcxNeuq6+x4tUcOz2zlQ/hqpxEdwt834mhJiTj9j mSEQ== X-Gm-Message-State: APzg51DOO/eIHTQtXw2hycMp5bQJSjPDzfH4tSh8EISdAQOQzkeNtP0p zRxibkTVPzkQcOo26e1IGaHfRu7LWFDrARTO7PWRqQ== X-Google-Smtp-Source: ANB0VdYs/oBoMvIdJtrwkXUZdB3ceExBdsqBOYEj5f0XfAU9GwjU7R8TCO5rpqPsx4B671ANqH0ssb8b5M0NDplGfDI= X-Received: by 2002:a9f:3110:: with SMTP id m16-v6mr10278010uab.48.1536717639631; Tue, 11 Sep 2018 19:00:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rick Miller Date: Tue, 11 Sep 2018 22:00:30 -0400 Message-ID: Subject: Re: HELP upgrade 10.3 to 11.2, now it won't boot! To: wfdudley@gmail.com Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2018 02:00:40 -0000 Glad it worked! On Tue, Sep 11, 2018 at 9:58 PM William Dudley wrote: > Rick, > > The problem was that my root partition had an "old" name: /dev/ad0s1a, > instead of the > "new" name, /dev/ada0s1a. I booted a live CD and fixed it, and now it's > booting. > > That scared the crap out of me. > > I'm not running ZFS -- I try to be as conservative as possible, not > wanting to get bitten > by experimental new tech. So the boot drive is PATA, UFS. I have a > gmirror running > on some SATA drives where the data is actually stored. > > Thanks very much for your help -- you had the answer. > > If you're ever in central New Jersey, let me buy you a beer. Or > equivalent. > > Bill Dudley > > > This email is free of malware because I run Linux. > > On Tue, Sep 11, 2018 at 9:52 PM, Rick Miller wrote: > >> >> >> On Tue, Sep 11, 2018 at 9:28 PM William Dudley >> wrote: >> >>> This was a straight upgrade using freebsd-upgrade. I don't do source >>> builds anymore, since freebsd-upgrade was "reliable". >>> >>> What is the boot loader expecting to find in /etc/fstab ? >>> >>> I can boot live media and fix that, if I know what to change it to. >>> >> >> The device for / in /etc/fstab must be valid. Do you know your partition >> layout? The device in fstab must be the device with root. Check the devices >> returned from '?' at the mountroot prompt. Unfortunately, the circumstances >> surrounding our experiences with this error are quite different and fixing >> the two are different. >> >> Is this ZFS? Are there options to boot an alternate kernel? Tried that? >> Failing that, boot to external media to verify and validate /etc/fstab. >> >> >>> Thanks, >>> Bill Dudley >>> >>> >>> >>> This email is free of malware because I run Linux. >>> >>> On Tue, Sep 11, 2018 at 9:24 PM, Rick Miller >>> wrote: >>> >>>> >>>> >>>> On Tue, Sep 11, 2018 at 8:27 PM William Dudley >>>> wrote: >>>> >>>>> I started the upgrade from 10.3 to 11.2. >>>>> >>>>> I followed all the instructions and all "looked OK" until I got to >>>>> the reboot. >>>>> >>>>> Now the system won't boot. >>>>> >>>>> copied from a photo of the screen: >>>>> >>>>> Mounting from ufs:/dev/ad01e failed with error 19. >>>>> >>>>> (something)dev variables: >>>>> (something)ufs.root.mountfrom=ufs:/dev/ad0s1e >>>>> (something)ufs.root.mountfrom.options=rw >>>>> >>>>> (something)ual root filesystem specification: >>>>> : [options] >>>>> Mount using filesystem >>>>> and with the specified (optional) option list. >>>>> >>>>> e.g. ufs:/dev/da0s1a >>>>> zfs:tank >>>>> cd9660:/dev/cd0 r0 >>>>> >>>>> and obviously, more stuff intended to be helpful printed below that. >>>>> >>>> >>>> Ugh! This error is the bane of my existence! AFAIK, mountroot() error >>>> 19 means the root filesystem cannot be found. vfs.root.mountroot, which is >>>> expected to contain the root filesystem, is derived from /etc/fstab unless >>>> explicitly defined in loader(8)*. Theoretically, you can boot to whatever >>>> root filesystem you may have by defining vfs.root.mountfrom at this prompt. >>>> >>>> Entering '?' at this prompt outputs a list of geom managed disk >>>> devices. The root filesystem is expected to be on one of these. >>>> >>>> It's unclear how the upgrade was attempted (e.g. freebsd-update(8) or >>>> source update). I've observed this error most when PXE booting bootonly >>>> media, never during an OS upgrade. >>>> >>>> You may be able to resolve it by booting the system to external media >>>> and mounting the disk with the root filesystem and modifying /etc/fstab. >>>> >>>> * https://twitter.com/hostileadmin/status/1035887403821686784 >>>> >>>> -- >>>> Rick >>>> >>> >>> >> >> -- >> Take care >> Rick Miller >> > > -- Take care Rick Miller