LVM Thin metadata fail after replacement a failed raid controller

[Desler]

We have a crash in the raid controller. After replacing it and assembling a new raid from old disks (without reinitializing them), we were able to access the file system.
But to our disappointment, the volumes of lvm were not available to us. It seems that the metadata of thin volumes was violated.
What actions can be taken in this situation, and is it realistic to save the data?

# lvdisplay
  --- Logical volume ---
  LV Name                thin
  VG Name                data
  LV UUID                ohFNZx-W8IN-q0Zk-sXQo-eQgt-4pJV-yE1y18
  LV Write Access        read/write
  LV Creation host, time s-nl01-cnode-06, 2018-04-18 13:08:19 +0000
  LV Pool metadata       thin_tmeta
  LV Pool data           thin_tdata
  LV Status              NOT available
  LV Size                6.00 TiB
  Current LE             6144
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

  --- Logical volume ---
  LV Path                /dev/data/vm-105-disk-1
  LV Name                vm-105-disk-1
  VG Name                data
  LV UUID                hsixOJ-DVO1-2Ty1-wi27-fT2f-519p-BmwJSO
  LV Write Access        read/write
  LV Creation host, time s-nl01-cnode-06, 2019-06-18 13:09:32 +0000
  LV Pool name           thin
  LV Status              NOT available
  LV Size                500.00 GiB
  Current LE             500
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

lvs -a
  LV              VG   Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  [lvol0_pmspare] data ewi-------  16.00g
  thin            data twi---tz--   6.00t
  [thin_tdata]    data Twi-------   6.00t
  [thin_tmeta]    data ewi-------  16.00g
  vm-105-disk-1   data Vwi---tz-- 500.00g thin