zpool online in old zfs version yet faulted in newer zfs version

[GhostSBH]

I'm upgrading my OS (GhostBSD). I have a 3-disc single pool for my data (not the OS).
The old zfs OS shows no error (online). Scrub shows no errors corrected. I used zpool clear 'poolname' to reset any error flags.
The new zfs OS shows the second disc of the pool faulted with 'too many errors'. I cannot import the pool.
Question:
Are there specific get or set flags I need to manage to get the pool importable from the old zfs to the new zfs?
Are there known migration issues between 2.1.13 -> 2.2.7?
Thx

Detail:
Old zfs = 2.1.13
New zfs = 2.2.7
iostat -n 4 shows all discs present in both OSs
History for 'poolname' shows just the import export, scrubs events in the old OS.
I'm just swapping the OS disc in the box, not moving any cabling for the 3-disc pool.

[amotin]

It's definitely not normal for just a ZFS update. There must be something bigger. But here is not enough data to say anything.

[GhostSBH]

Thanks for trying Alexander....

I note that /var/db/zfsd/cases is empty - so no unresolved old zfs issues.

Any hints at where to investigate next greatly appreciated.

Steve

[GhostSBH]

OK - so I did some more experimenting...
Using live media [USB ISOs] I can import the pool without error warnings into zfs-2.1.11 and zfs-2.1.13 versions of GhostBSD OSs.
However, I get an invalid label error [ZFS-8000-5E] for the second disc with zfs-2.2.2 onwards to current zfs-2.2.7.
I did not try to force the import [-f].
It seems to be an upwards compatibility issue of zfs itself.
Do any actions come to mind in getting around this upwards compatibility issue?