ZFS and replaced motherboard
Grzegorz Junka
list1 at gjunka.com
Sun Oct 22 12:43:25 UTC 2017
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
More information about the freebsd-questions
mailing list