Upgrade to Bluefin changed Sector size on NVDIMM

Gabriele1111

Cadet
Joined
Mar 18, 2022
Messages
3
HI, don't know if you can help me, I have an Intel system with 4x nvdimm and I was using 2 of them as Dedup Vdev, all working fine. Last week I upgraded to Bluefin and now the pool is offline. The 2 nvdimm in the Dedup vdev seem empty in Bluefin, the sector size has changed from 4096 bytes in Angelfish to 512 bytes in Bluefin.

Is there an easy way out or do I have to recreate the Pool and restore from Backup?

Angelfish:
Disk /dev/pmem0: 126 GiB, 135291469824 bytes, 33030144 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D82CE487-DAB6-48F7-AF94-7505AD887747

Device Start End Sectors Size Type
/dev/pmem0p1 6 33030138 33030133 126G Solaris /usr & Apple ZFS

Bluefin:

GPT PMBR size mismatch (33030143 264241143) will be corrected by write.
Disk /dev/pmem0: 126 GiB, 135291465728 bytes, 264241144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000000000


Device Boot Start End Sectors Size Id Type
/dev/pmem0p1 1264241143264241143126G eeGPT

Partition 1 does not start on physical sector boundary
 
Top