Internal error: Not_found after Vinchin backup
-
This snapshot has been purged of it's data. It only contains metadata and changed blocks.
-
Any ideas if I can remove those? I appreciate the help!
-
Okay, what abut the remove button on the right? Does it work to remove it?
-
@olivierlambert Sorry do you mean the destroy VI button. Will that cause any issues with the actual VM?
-
I don't think so, it's just a snasphot.
-
@olivierlambert Is there anything scheduled by default in xcp-ng on Sundays? Or how often does it coalesce. Just trying to figure out why every Sunday these issues happen.
-
There's no schedule in XCP-ng. It's more about when you remove snapshots (without CBT). You can check about coalesce inside the /var/log/SMlog and try to watch what's going on on Sunday.
-
@olivierlambert Ok. Why does XOA show some with CBT and some without? How does that get set? I apologize, I am just trying to narrow this down. I appreciate all the help.
-
I suppose those snapshots were done via Vinchin, so I can't tell. You can clean all snapshots to get back on something clean before trying anything else.
-
@olivierlambert Ok, will do. Synology says that xcp-ng is sending LUN disconnects to the LUN based on the dmesg on on the Synology.
iSCSI:target_core_tmr.c:629:core_tmr_lun_reset LUN_RESET: TMR starting for [fileio/Synology-VM-LUN/9c706a83-1e77-47a8-a5c5-18cfe815459d], tas: 1
-
So I just click "Destroy VDI" on the snapshot?
-
Sorry I'm just a bit confused because it is showing no snapshots on the VM view
-
Yes, destroy those CBT snapshots. It's not visible in VM/snapshots because they are CBT, not "real" VM snap that you can rollback.
-
@olivierlambert I did that on one and noticed a task API call: sr.scan I opened the raw log and seeing errors. AttachedSR Scan Errors.txt
-
Is that due to the Master being disconnected from the SR. That is the one I was referring to in my previous Topic post "Pool Master".
-
Just keeps bouncing over and over
-
So even taking Vinchin out of the picture for now, I am still worried that xcp-ng will run the Garbage Collection and disconnect the ST, brining the VM down again.
-
Ignore the XO tasks panel, it's not important. About the rest, please use it and report if you continue to have issues.
-
I deleted the snapshot from this one vm.
However, that one remains in the list on here:
-
You can check if coalesce is running if you see that garbage collection is planned on XO/SR view.
