It doesn't ring a bell as it is for me.
What I see from the first log is the segfault on
blktap and in
xcp-rrdd-xenpm, likely that was while writing to a disk. In all cases, it is a
Given it happens on a single machine, I would venture it could be related to the disk controller, or disk itself, you could try to have a look at a
dmidecode to see if the controllers are the same as on othe machines (sometimes there are small discrepencies between supposedly identical hardware), and check the drives with
smartctl for any health issues. But especially as you were on raid1 originally, I doubt an issue with the drives themselves would lead to such an issue...