From owner-freebsd-questions@FreeBSD.ORG Mon Feb 3 17:07:07 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0693435 for ; Mon, 3 Feb 2014 17:07:07 +0000 (UTC) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 777801C9D for ; Mon, 3 Feb 2014 17:07:07 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id h16so8349358oag.24 for ; Mon, 03 Feb 2014 09:07:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=z5uejXlSQ1HgUQAMfYDWyA4+8ivwtZqEgefSzp/eSag=; b=idGMDevHIfLIzWSLHjACXezO0K0ZbxAyXyG7EKycd/lNvouj2a7QD0XTZxKMJGnaEp /gEIRHR4g79CkSXZWZhxMZqTFOi+PGZZBs/Dv5HAUyNB0Z2cvwLmpoOVj9//rr3wr6gV OroDFbLEiIGLQQaYOwa77OqMEG+SLrhcpglzdUI+DDQQdxV/jpwd6XGDyGhrSaeMAPj1 uUhzZ3T3HA7F7l/NEvAo8YCZHjQo7W5vSMnZqFOzx87y7q38t3Vq5y456uSXkI9ZUf1+ e1/DLcbW6E054enax3VqiQvg1KLCmdIvxDLNjXlRnql+dDi3p7Yp2o9IEtLbCkP8ShtZ JbvA== X-Received: by 10.60.98.40 with SMTP id ef8mr31400971oeb.13.1391447226569; Mon, 03 Feb 2014 09:07:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.167.34 with HTTP; Mon, 3 Feb 2014 09:06:46 -0800 (PST) In-Reply-To: <64791.5198.bm@smtp119.sbc.mail.gq1.yahoo.com> References: <64791.5198.bm@smtp119.sbc.mail.gq1.yahoo.com> From: n j Date: Mon, 3 Feb 2014 18:06:46 +0100 Message-ID: Subject: Re: The best approach to upgrade to freebsd 10 ? To: User Questions Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Feb 2014 17:07:07 -0000 On Mon, Feb 3, 2014 at 1:40 PM, Thomas Mueller wrote: > > A few days ago I did the (freebsd-update) upgrade of my VPS. I've been > > using FreeBSD since 4.8 and been running various releases and doing > > upgrades since then. This last upgrade (9.2-->10.0) was probably the > worst, > > though I accept the blame for not reading /usr/src/UPDATING carefully. > Here > > are the problems I ran into: > > > 1) unable to boot after first stage of upgrade with "mounting ufs... > error > > 19". This is explained in UPDATING entry 20110424 - basically, disk > device > > names have been changed and the system was not able to find boot > partition > > ad0s1a as it was renamed to ada0s1a. This is an old entry, but there were > > symbolic links to old device names throughout 9.x enabling the old > > configuration to work which I guess was removed on 20130404 ("Legacy ATA > > stack... completely removed from sources"). > > > 2) network not working. I can't find this exactly in the UPDATING notes, > > but there was a lot of talk on Xen-related changes so I guess it was not > > much of a surprise. My NIC was renamed from re0 to xn0 hosing the > > ifconfig_re0 entries in rc.conf and ipfw "via" rules. > > > 3) not actually a problem per se, but building a custom kernel with > > IPFIREWALL_FORWARD option I was using before failed with "unknown > option". > > Again, this is in UPDATING entry 20121102 - option removed, functionality > > enabled by default. Finally! > > > So take care if you share any of the above. 1) and 2) are especially > > problematic if you are running upgrade remotely. > > > Regards, > -- > > Nino > > You mention re0 being renamed to xn0. > > I couldn't find any device xn or xn0 in FreeBSD 11-current, though I found > xe and xen. > > I figured if it were in 10-STABLE, it would also be in 11-HEAD. > > For a moment, I thought maybe the reason why I couldn't connect Ethernet > on MSI Z77 MPOWER motherboard was needing to use a driver other than re, > but nothing so simple. > > There is still device re. > > Did you make a typo with xn0? > No, ifconfig says xn0: xn0: flags=8843 metric 0 mtu 1500 Also in dmesg.boot: xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:XX:XX:XX xenbusb_back0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 So it's xn0 in my case, not xe. Regards, -- Nino