ZFS and replaced motherboard

[Shane Ambler]

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