Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Dec 2017 13:44:11 +0000
From:      Grzegorz Junka <list1@gjunka.com>
To:        Shane Ambler <FreeBSD@ShaneWare.Biz>, freebsd-questions@freebsd.org
Subject:   Re: ZFS and replaced motherboard
Message-ID:  <a066b200-53d9-0a15-f36f-4be403f4cf99@gjunka.com>
In-Reply-To: <68d134bb-7b69-39c5-edaf-4ed5129be2ad@ShaneWare.Biz>
References:  <0743dee8-be50-9952-953f-f060a33edba9@gjunka.com> <68d134bb-7b69-39c5-edaf-4ed5129be2ad@ShaneWare.Biz>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On 23/10/2017 04:52, Shane Ambler wrote:
> 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
>

Hi Shane,
Thank you for the tip. I just tried it by setting in the command line (I 
didn't want to restart the server). It worked with NVMe disks but not 
with SATA disks:

root@server:~ # sysctl -a | grep disk_ident
kern.geom.label.disk_ident.enable: 0

root@server:~ # zpool status
   pool: tank1
  state: ONLINE
   scan: resilvered 780K in 0h0m with 0 errors on Sun Sep 10 08:44:03 2017
config:

         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 0
             diskid/DISK-WD-WCC1U4176715p3  ONLINE       0     0 0
             diskid/DISK-WD-WCC1U3531030p3  ONLINE       0     0 0
             diskid/DISK-WD-WCC1U3565183p3  ONLINE       0     0 0

errors: No known data errors

   pool: tank5
  state: ONLINE
   scan: none requested
config:

         NAME        STATE     READ WRITE CKSUM
         tank5       ONLINE       0     0     0
           mirror-0  ONLINE       0     0     0
             nvd1    ONLINE       0     0     0
             nvd0    ONLINE       0     0     0

errors: No known data errors

Why only NVMe? Would adding to bootloader.conf change anything?

Thanks
GrzegorzJ



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?a066b200-53d9-0a15-f36f-4be403f4cf99>