CBT Error when powering on VM

rustylh

I had to power off a VM then power it back on. However, it will not power back on now displaying this error:
Changed block tracking disabled due to inconsistent metadata. Changed Block Tracking metadata is inconsistent for disk "%number%".

I, of course, jumped right to looking the error up and found an article saying the first step is to back up the VM. So, I am copying it using the "Copy VM..." in XCP-NG Center. This VM is 600GB so I assume it will take a long while. Either way, does someone know how to fix this and get the VM powered back on successfully? I appreciate any ideas and/or instructions. Unfortunately I do not have a Paid version of XOA. (in know dumb....)
Thank you!

olivierlambert

Hi,

XCP-ng Center isn't supported at all. The error message is coming from XCP-ng Center I assume? Have you try to start the VM with XO or XO Lite?

rustylh

Trying with XOA Lite. VM Acts like it's starting then just stops.

{
  "id": "0mfcgnd1b",
  "properties": {
    "method": "vm.start",
    "params": {
      "id": "14d739cc-ac03-591f-f9e2-0206000c4fc4",
      "bypassMacAddressesCheck": false,
      "force": false
    },
    "name": "API call: vm.start",
    "userId": "6b37221b-22b6-452b-ba2a-7bd46fc924a9",
    "type": "api.call"
  },
  "start": 1757416903103,
  "status": "failure",
  "updatedAt": 1757416903349,
  "end": 1757416903349,
  "result": {
    "code": "INTERNAL_ERROR",
    "params": [
      "Not_found"
    ],
    "call": {
      "duration": 242,
      "method": "VM.start",
      "params": [
        "* session id *",
        "OpaqueRef:570f1cc5-9197-4bd4-8fc3-f75f90e36e4b",
        false, false]
    },
    "message": "INTERNAL_ERROR(Not_found)",
    "name": "XapiError",
    "stack": "XapiError: INTERNAL_ERROR(Not_found)\n    at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)\n    at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/transports/json-rpc.mjs:38:21\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at processImmediate (node:internal/timers:454:9)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }
}

rustylh

The VM is now starting to the Alma boot page, goes past that then shows Paused. Then just goes back to a powered off state.

olivierlambert

Are you sure the VM operating system isn't crashing? Are you seeing anything during boot phase?

rustylh

It acts like it is starting normally and goes to the Kernel version selection for Alma, starts to boot then shows paused, then goes back to powered off state and shows the attached.

rustylh

rustylh

XOA Just shows it starting XOA VM Startup.png

rustylh

Does this help?

rustylh

That last power on attempt log

{
  "id": "0mfciiw3i",
  "properties": {
    "method": "vm.start",
    "params": {
      "id": "14d739cc-ac03-591f-f9e2-0206000c4fc4",
      "bypassMacAddressesCheck": false,
      "force": false
    },
    "name": "API call: vm.start",
    "userId": "6b37221b-22b6-452b-ba2a-7bd46fc924a9",
    "type": "api.call"
  },
  "start": 1757420053758,
  "status": "failure",
  "updatedAt": 1757420054029,
  "end": 1757420054029,
  "result": {
    "code": "INTERNAL_ERROR",
    "params": [
      "Not_found"
    ],
    "call": {
      "duration": 267,
      "method": "VM.start",
      "params": [
        "* session id *",
        "OpaqueRef:570f1cc5-9197-4bd4-8fc3-f75f90e36e4b",
        false,
        false
      ]
    },
    "message": "INTERNAL_ERROR(Not_found)",
    "name": "XapiError",
    "stack": "XapiError: INTERNAL_ERROR(Not_found)\n    at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)\n    at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/transports/json-rpc.mjs:38:21\n    at runNextTicks (node:internal/process/task_queues:60:5)\n    at processImmediate (node:internal/timers:454:9)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }

olivierlambert

@rustylh Can you try another kernel version or a safe mode if available in the Grub menu of your VM? It seems the OS cannot boot anymore, for whatever reason happened inside the VM.

rustylh

I tried the second Kernel. I can try safe from Grub. I am not familiar with that, but I will try.

rustylh

Same result

olivierlambert

To me, you have an issue inside your OS. You can try to mount the disk of this VM in another VM and try to check what's going on, maybe do a file system check or something.

rustylh

Ok, thank you for looking. Is there anything in my previous screen shots that sticks out? Something else I can try?

olivierlambert

I would check inside the OS that cannot boot anymore, running an fsck

That's what I would do

rustylh

Ok, this is weird. I just created a new VM with new name. It is booting and hung at the same message.
vdb vdb-5696: 19 xenbu_dev_prob on device/vdb/5696

Not sure what to think.

olivierlambert

That's an OS issue, as I said. You need to mount it in another VM as an extra drive, or use a LiveCD to explore the filesystem

rustylh

I understand. However, this is a bran new VM I just created with a new name.

AtaxyaNetwork

@rustylh How are you creating your VM ?