Last week write access to my NVMe ssd running Qubes 4.3 was lost with data corruption (on the dom0 root volume) preventing boot. Installing Qubes on another NVMe ssd and proceeding to debug, I determined the data corruption was too pervasive. I successfully made disk images of my various private volumes (no recent backups, oops). After I finished that, my fresh Qubes install on the second NVMe ssd crashed in the same way, still booting but with some data corruption. On subsequent boots it continued to crash in the same way. Switching to plain Debian Trixie on one of the drives resolved the crashing issue so I suspect I’ve run into a regression in Qubes or Xen.
Right now I don’t have access to logs since the systems couldn’t write any information after the drives crashed and there doesn’t appear to be anything leading up to the problem in them. I’ll figure out a way to produce the problem again and preserve logs, could someone point out which ones in particular I should gather?
Hardware:
Originally an Asrock X670E Taichi, tried again with the same result with an Asrock X870E Taichi
AMD 7950X3D CPU
SkHynix P41 1TB SSD, Crucial T710 4TB SSD