From owner-freebsd-questions@freebsd.org Wed Sep 12 01:58:20 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 A245510A5BE0 for ; Wed, 12 Sep 2018 01:58:20 +0000 (UTC) (envelope-from wfdudley@gmail.com) Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 3A0799429C for ; Wed, 12 Sep 2018 01:58:20 +0000 (UTC) (envelope-from wfdudley@gmail.com) Received: by mail-yb1-xb2f.google.com with SMTP id e18-v6so240785ybq.5 for ; Tue, 11 Sep 2018 18:58:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Iz/ysFR1qWZeMbtjU3ocbKgKoheq3W1eJfmreMpxaXQ=; b=jaldCY/j1w5Rdi+koCYYehzrSn6N6LoO1PItoWhn298/eBPJy7pMTweZXOQWmHkOq4 QqCm/Dld7Ec/JGEYm+j2jzCYeDvP7d7kb+AwXwgnCqcMv1Bj8qjeqTsQ0m5e/H7nCPmm NC2Y/ndrCHM8OHZ3BTQL3dKxDA6+yNP/MAJhF9g9q1cGS5NowM6B7Degr7RYcbxJBnVZ 1Q7H6X0YRj6PtLvcgMD/BCtYKMeOTil0RIlPpm4nBpRUl44webKAFaeOgMFfiIgOTWCr TD1KGLTvdSNXS14an6Tq+i2MDQAq8Fsj3q0c24ma/Evb2INmhqvJpR2nt52RoUGzCVWJ 4FQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Iz/ysFR1qWZeMbtjU3ocbKgKoheq3W1eJfmreMpxaXQ=; b=OPjvSqpc7qYGPAKm9PmpqYImozFWcwcq+0qo5BEUbM2It/GPJiZ2N+Hu6fKUkzAm9c 8+bOIWWuZwWj1J0YRUuyWdwFwuIkANJ5lcj/P1ZqtmVGQG6EgZiB56u9dekxa4Q+NP7j yggocjaJ7Fe+FWixULqnkDOPo+P7ONQ38LFp3AUfdb5DOXBY6zXTYFqIDL1SKDDbB1E/ BcCMTnhyfeSwDOkclmBWuxtoRal5e4GX7SphhMI9/A18vmaycGba7pdPVW7SbmjVCjXF ciIOn70mQjOITmKcZhRMOf6FX0TGJ/agFYviFsz6UDR1haYcRe+HyLE4Xm4CIymJwOvC qtxA== X-Gm-Message-State: APzg51BOf3sWjPo6Bd1HJhLNGrq8rAM1QcnuXglPY88egjiM2wXomdXe Q6Psrw0d96rjPROPc/NEIBAeXfIWwVjbFJI9RUc= X-Google-Smtp-Source: ANB0VdYVbhOpfzKnr/cv7Y7n6jtKh9E99UppvHft83xeUDX0KmYbSacUnkswjhWkSfU7uBZOQ/2Hvj5dG0ZgQM7Tt40= X-Received: by 2002:a0d:d849:: with SMTP id a70-v6mr14454021ywe.506.1536717499557; Tue, 11 Sep 2018 18:58:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:9003:0:0:0:0:0 with HTTP; Tue, 11 Sep 2018 18:58:18 -0700 (PDT) In-Reply-To: References: From: William Dudley Date: Tue, 11 Sep 2018 21:58:18 -0400 Message-ID: Subject: Re: HELP upgrade 10.3 to 11.2, now it won't boot! To: Rick Miller , 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 01:58:20 -0000 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 >