Date: Sun, 22 Oct 2017 13:08:18 -0400 (EDT) From: DTD <doug@safeport.com> To: Matthias Fechner <idefix@fechner.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: pkg upgrade problem as freebsd-update Message-ID: <alpine.BSF.2.00.1710221308030.59952@bucksport.safeport.com> In-Reply-To: <031c6f11-1dfa-be99-2fde-56cdc889c393@fechner.net> References: <alpine.BSF.2.00.1710211413310.59952@bucksport.safeport.com> <031c6f11-1dfa-be99-2fde-56cdc889c393@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Oct 2017, Matthias Fechner wrote: > Am 21.10.2017 um 20:17 schrieb DTD: >> I just upgraded a system to 10.4 with freebsd-update. in doing: >> >> pkg upgrade -n' >> >> Installed packages to be UPGRADED: >> vim-lite: 8.0.0102 -> 8.0.1159 >> libiconv: 1.14_9 -> 1.14_11 >> >> Installed packages to be REINSTALLED: >> ezjail-3.4.2 (ABI changed: 'freebsd:9:x86:64' -> >> 'freebsd:10:x86:64') >> >> file /bin/sh >> /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD >> 10.4, FreeBSD-style, stripped > try: > pkg-static upgrade > > Gru? > Matthias > Thanks _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 From owner-freebsd-questions@freebsd.org Mon Oct 23 04:57:25 2017 Return-Path: <owner-freebsd-questions@freebsd.org> Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7D15E4053B for <freebsd-questions@mailman.ysv.freebsd.org>; Mon, 23 Oct 2017 04:57:25 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail02.adl2.internode.on.net (ipmail02.adl2.internode.on.net [150.101.137.139]) by mx1.freebsd.org (Postfix) with ESMTP id 7B9D02093 for <freebsd-questions@freebsd.org>; Mon, 23 Oct 2017 04:57:22 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 220-253-32-111.dyn.iinet.net.au (HELO leader.local) ([220.253.32.111]) by ipmail02.adl2.internode.on.net with ESMTP; 23 Oct 2017 15:22:11 +1030 Subject: Re: ZFS and replaced motherboard To: Grzegorz Junka <list1@gjunka.com>, freebsd-questions@freebsd.org References: <0743dee8-be50-9952-953f-f060a33edba9@gjunka.com> From: Shane Ambler <FreeBSD@ShaneWare.Biz> Message-ID: <68d134bb-7b69-39c5-edaf-4ed5129be2ad@ShaneWare.Biz> Date: Mon, 23 Oct 2017 15:22:10 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <0743dee8-be50-9952-953f-f060a33edba9@gjunka.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 23 Oct 2017 04:57:25 -0000 On 22/10/2017 23:13, Grzegorz Junka wrote: > I have replaced a motherboard with almost an identical (the new one only > doesn't have a LSI SAS2 controller, which wasn't used anyway). > > So, I was surprised to see that ZFS automatically recognized the pool > after I booted up the system on the new motherboard despite the fact > that accidentally some SATA ports have been swapped (i.e. disks weren't > connect to the same SATA ports as on the old motherboard). ZFS is recognised by info stored on the disk. The same pool should be able to be imported on different hardware and systems - like Illlumos or Solaris/sparc64 > However, there is one thing that differs from the old system and that's > how those disks are reported: > diskid/DISK-WD-WCC1U3689037p3 ONLINE 0 0 0 > Ignore the checksum error, that's because one disk wasn't connected > properly for a couple of minutes but then was reconciled. The issue is > that these disks no longer show as ada1, ada2, ada3, ada4, ada5, ada6. Why? > > The same with the M.2 nvm-e disks: > diskid/DISK-S1XXNYAH300115 ONLINE 0 0 0 > They should be showing as nvd0 and nvd1. How to correct this? Does this > need to be corrected? It doesn't have to be corrected, but it can be easier for us to read. Try adding kern.geom.label.disk_ident.enable=0 to /boot/loader.conf -- FreeBSD - the place to B...Storing Data Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1710221308030.59952>