Storage corruption detected for `trace.saved_traces`

Installation
1 
The trace.saved_traces storage could not be parsed and has been renamed to /config/.storage/trace.saved_traces.corrupt.2025-03-15T14:16:03.547137+00:00 to allow Home Assistant to continue.

A default trace.saved_traces may have been created automatically.

If you made manual edits to the storage file, fix any syntax errors in /config/.storage/trace.saved_traces.corrupt.2025-03-15T14:16:03.547137+00:00, restore the file to the original path /config/.storage/trace.saved_traces, and restart Home Assistant. Otherwise, restore the system from a backup.

Select Submit below to confirm you have repaired the file or restored from a backup.

The exact error was: Error while loading /config/.storage/trace.saved_traces: unexpected character: line 5168 column 23 (char 196608)

image
image705×559 20.9 KB

if it try to restore backup.

logs

image
image1093×670 321 KB

2

Hello yousaf465,

What kind of Hard drive are you using? It is OK?

3

HAOS is installed as a VM on proxmox on a SSD. rest of LXC containers and VM are working fine.

4

Do you regularly snapshot your VM? I think something has you corrupted there, do a smart check on that drive if you can.

5

I do HAOS backup to google drive. I want to setup NFS share to a 2TB HDD connected to same proxmox as second/local copy.

6

The by far biggest advantage of putting HA into a VM is to snapshot it, then in the event of a crash you can be back up in about 2 minutes.

I don’t know what’s going on, but if it were me I’d check that the drive is ok with actual data (not just the fact that other containers seem to still be working), and if it is rebuild the VM.

7

I rebuilt the VM and restored a backup from other instance of HAOS and it worked fine, but when I tried to restore this instance in a new vm , this happens.