From owner-freebsd-questions@freebsd.org Sun Oct 22 12:43:25 2017 Return-Path: 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 92A17E51FDB for ; Sun, 22 Oct 2017 12:43:25 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E1BB64E93 for ; Sun, 22 Oct 2017 12:43:24 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v9MChMOQ087705 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 22 Oct 2017 12:43:22 GMT (envelope-from list1@gjunka.com) To: freebsd-questions@freebsd.org From: Grzegorz Junka Subject: ZFS and replaced motherboard Message-ID: <0743dee8-be50-9952-953f-f060a33edba9@gjunka.com> Date: Sun, 22 Oct 2017 12:43:22 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB-large X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 12:43:25 -0000 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). However, there is one thing that differs from the old system and that's how those disks are reported:         NAME                               STATE     READ WRITE CKSUM         tank1                              ONLINE 0     0     0           raidz2-0                         ONLINE 0     0     0             diskid/DISK-WD-WCC1U3689037p3  ONLINE 0     0     0             diskid/DISK-WD-WCC1U3680535p3  ONLINE 0     0     0             diskid/DISK-WD-WCC1U4178255p3  ONLINE 0     0   336             diskid/DISK-WD-WCC1U4176715p3  ONLINE 0     0     0             diskid/DISK-WD-WCC1U3531030p3  ONLINE 0     0     0             diskid/DISK-WD-WCC1U3565183p3  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:         NAME                            STATE     READ WRITE CKSUM         tank5                           ONLINE       0     0     0           mirror-0                      ONLINE       0     0     0             diskid/DISK-S1XXNYAH300115  ONLINE       0     0     0             diskid/DISK-S1XXNYAH300143  ONLINE       0     0     0 They should be showing as nvd0 and nvd1. How to correct this? Does this need to be corrected? GrzegorzJ