Pool import failed after hardware change

TrueNAS General
1

Recently I moved my homelab from another location to my home. During this time, my hardware is way too overkill for truenas and decided to downgrade.
Previous working system has two pools, 4 nvme’s and 8 sas disks IIRC truenas core 13.0u4
New system is with same disks and only cpu+ram+motherboard downgraded. SAS hba is same but disk order changed during hw installation on hba ports. Also on previous system disks are connected to hba via sas expander midplane, now its connected directly hba with sff8643 breakout cable.
new os is scale 25.04.2.3.

I am able to import nvme pool without any problem but my sas pool didn’t show up on import screen and there’s a error appears that saying:

Disk(s): sda, sdb, sdc, sde, sdd, sdf, sdg, sdh are formatted with Data Integrity Feature (DIF) which is unsupported.

am I doing wrong something or data is gone?

2

Some disks have extra checksums, for end to end data verification. This is generally used by hardware RAID devices. What it does is add the checksum to the disk sector for disk writes. For a 512 byte sector, this means something like adding an 8 byte checksum to make a 520 byte sector. (Something similar happens when using 4096 byte sectors…)

Your old version of TrueNAS supported this, but the new version appears not to support this. ZFS never needed or supported DIF formatted disks, as ZFS was designed with a much beefier checksum stored outside of the disk sector. (Storing the block checksum outside of the sector will catch drive firmware bugs that mis-write a sector in the wrong place.)

Unfortunately, you can’t fix this easily. But, the good news is that your data is likely intact.

The way to handle this is to boot an OS that supports:

  1. DIF
  2. ZFS
  3. SG Format or other tool to low level format the disks, to remove DIF

Then, assuming you have a redundant pool, (RAID-Zx or Mirrors):

  1. Remove 1 disk from the pool
  2. Re-format that disk to normal sector size, (512 or 4096)
  3. Replace the disk, which will have to do a full re-silver of the data for that disk
  4. Repeat until all the disks are done

While the data on the disks is almost certainly good, without DIF driver support on the new OS, the disks are basically un-readable.

I can’t give exact steps, even though I have done this before, it was a very long time ago and different OS.

3

Thanks for the reply, it seems booting from old disk, expect everything is ok and pull the data to another disk is better option. These disks pulled from dell r750xs and didn’t expect they are using 520b format.