@rzr Updates installed everywhere (on top of the previous updates). Rolling pool reboot worked this time (with correct prep).

@poddingue Since setting NBD=1, I have not seen the problem.

SR is NFS on dual 40G ethernet with a TrueNAS scale 25.10 server using all NVMe SSD, so storage performance is as good as I can make it.

I'll have to enable NBD=2 again to see if it still happens and if I can find the relevant part of the logs. As this is a random problem I can't recreate it on a normal test environment.

@All-Ki Thanks for your work!

ProLiant DL360p Gen8

UID Light        | 0x01              | ok
Sys. Health LED  | no reading        | ns
01-Inlet Ambient | 33 degrees C      | ok
02-CPU 1         | 55 degrees C      | ok
03-CPU 2         | 50 degrees C      | ok
04-P1 DIMM 1-6   | 45 degrees C      | ok
05-P1 DIMM 7-12  | 44 degrees C      | ok
06-P2 DIMM 1-6   | 38 degrees C      | ok
07-P2 DIMM 7-12  | 43 degrees C      | ok
08-P1 Mem Zone   | 42 degrees C      | ok
09-P1 Mem Zone   | 45 degrees C      | ok
10-P2 Mem Zone   | 39 degrees C      | ok
11-P2 Mem Zone   | 40 degrees C      | ok
12-HD Max        | 35 degrees C      | ok
13-Chipset 1     | 52 degrees C      | ok
14-Chipset1 Zone | 45 degrees C      | ok
15-P/S 1 Inlet   | 34 degrees C      | ok
16-P/S 1 Zone    | 40 degrees C      | ok
17-P/S 2 Inlet   | 42 degrees C      | ok
18-P/S 2 Zone    | 43 degrees C      | ok
19-PCI #1        | disabled          | ns
20-PCI #2        | disabled          | ns
21-VR P1         | 60 degrees C      | ok
22-VR P2         | 56 degrees C      | ok
23-VR P1 Mem     | 39 degrees C      | ok
24-VR P1 Mem     | 36 degrees C      | ok
25-VR P2 Mem     | 32 degrees C      | ok
26-VR P2 Mem     | 36 degrees C      | ok
27-VR P1Mem Zone | 38 degrees C      | ok
28-VR P1Mem Zone | 36 degrees C      | ok
29-VR P2Mem Zone | 31 degrees C      | ok
30-VR P2Mem Zone | 33 degrees C      | ok
31-HD Controller | 71 degrees C      | ok
32-HD Cntlr Zone | 52 degrees C      | ok
33-PCI 1 Zone    | 43 degrees C      | ok
34-PCI 1 Zone    | 46 degrees C      | ok
35-LOM Card      | 70 degrees C      | ok
36-PCI 2 Zone    | 50 degrees C      | ok
37-System Board  | 52 degrees C      | ok
38-System Board  | 45 degrees C      | ok
39-Sys Exhaust   | 43 degrees C      | ok
40-Sys Exhaust   | 46 degrees C      | ok
41-Sys Exhaust   | 46 degrees C      | ok
42-SuperCAP Max  | 33 degrees C      | ok
Fan Block 1      | 94.86 percent     | ok
Fan Block 2      | 94.86 percent     | ok
Fan Block 3      | 94.86 percent     | ok
Fan Block 4      | 94.86 percent     | ok
Fan Block 5      | 94.86 percent     | ok
Fan Block 6      | 94.86 percent     | ok
Fan Block 7      | 94.86 percent     | ok
Fan Block 8      | 94.86 percent     | ok
Power Supply 1   | 205 Watts         | ok
Power Supply 2   | 210 Watts         | ok
Power Meter      | 430 Watts         | ok
Power Supplies   | 0x01              | ok
Fans             | 0x02              | ok
Memory           | 0x40              | ok
C1 P1I Bay 1     | 0x01              | ok
C1 P1I Bay 2     | 0x01              | ok
C1 P1I Bay 3     | 0x01              | ok
C1 P1I Bay 4     | 0x01              | ok
C1 P2I Bay 5     | 0x01              | ok
C1 P2I Bay 6     | 0x01              | ok
C1 P2I Bay 7     | 0x01              | ok
C1 P2I Bay 8     | 0x01              | ok

ProLiant DL360 Gen10

UID              | 0x01              | ok
SysHealth_Stat   | 0x01              | ok
01-Inlet Ambient | 19 degrees C      | ok
02-CPU 1         | 52 degrees C      | ok
03-CPU 2         | 63 degrees C      | ok
04-P1 DIMM 1-6   | disabled          | ns
05-PMM 1-6       | disabled          | ns
06-P1 DIMM 7-12  | 44 degrees C      | ok
07-PMM 7-12      | disabled          | ns
08-P2 DIMM 1-6   | disabled          | ns
09-PMM 1-6       | disabled          | ns
10-P2 DIMM 7-12  | 48 degrees C      | ok
11-PMM 7-12      | disabled          | ns
12-HD Max        | 35 degrees C      | ok
13-Exp Bay Drive | disabled          | ns
14-Stor Batt 1   | 18 degrees C      | ok
15-Front Ambient | 24 degrees C      | ok
16-VR P1         | 48 degrees C      | ok
17-VR P2         | 54 degrees C      | ok
18-VR P1 Mem 1   | 31 degrees C      | ok
19-VR P1 Mem 2   | 29 degrees C      | ok
20-VR P2 Mem 1   | 35 degrees C      | ok
21-VR P2 Mem 2   | 36 degrees C      | ok
22-Chipset       | 42 degrees C      | ok
23-BMC           | 79 degrees C      | ok
24-BMC Zone      | 49 degrees C      | ok
26-HD Cntlr Zone | 40 degrees C      | ok
29-I/O Zone      | 37 degrees C      | ok
30-PCI 1         | disabled          | ns
31-PCI 1 Zone    | 45 degrees C      | ok
32-PCI 2         | disabled          | ns
33-PCI 2 Zone    | 44 degrees C      | ok
34-PCI 3         | disabled          | ns
35-PCI 3 Zone    | disabled          | ns
37-Rear HD Max   | disabled          | ns
38-Battery Zone  | 43 degrees C      | ok
39-P/S 1 Inlet   | 42 degrees C      | ok
40-P/S 2 Inlet   | 48 degrees C      | ok
41-P/S 1         | 46 degrees C      | ok
42-P/S 2         | 55 degrees C      | ok
43-E-Fuse        | 45 degrees C      | ok
44-P/S 2 Zone    | 53 degrees C      | ok
49-CPU 1 PkgTmp  | 84 degrees C      | ok
50-CPU 2 PkgTmp  | 94 degrees C      | ok
61-AHCI HD Max   | disabled          | ns
69-PCI 1 M2      | disabled          | ns
70-PCI 1 M2 Zn   | disabled          | ns
71-PCI 2 M2      | disabled          | ns
72-PCI 2 M2 Zn   | disabled          | ns
73-PCI 3 M2      | disabled          | ns
74-PCI 3 M2 Zn   | disabled          | ns
Fan 1            | 0x01              | ok
Fan 1 DutyCycle  | 26.26 percent     | ok
Fan 1 Presence   | 0x02              | ok
Fan 2            | 0x01              | ok
Fan 2 DutyCycle  | 23.52 percent     | ok
Fan 2 Presence   | 0x02              | ok
Fan 3            | 0x01              | ok
Fan 3 DutyCycle  | 23.52 percent     | ok
Fan 3 Presence   | 0x02              | ok
Fan 4            | 0x01              | ok
Fan 4 DutyCycle  | 23.52 percent     | ok
Fan 4 Presence   | 0x02              | ok
Fan 5            | 0x01              | ok
Fan 5 DutyCycle  | 23.52 percent     | ok
Fan 5 Presence   | 0x02              | ok
Fan 6            | 0x01              | ok
Fan 6 DutyCycle  | 24.30 percent     | ok
Fan 6 Presence   | 0x02              | ok
Fan 7            | 0x01              | ok
Fan 7 DutyCycle  | 24.30 percent     | ok
Fan 7 Presence   | 0x02              | ok
Power Supply 1   | 0x01              | ok
PS 1 Input       | 200 Watts         | ok
Power Supply 2   | 0x01              | ok
PS 2 Input       | 190 Watts         | ok
Power Meter      | 400 Watts         | ok
Fans             | 0x01              | ok
Power Supplies   | 0x01              | ok
Memory Status    | 0x40              | ok
Megacell Status  | 0x04              | ok
Intrusion        | Not Readable      | ns
CPU Utilization  | 252 unspecified   | ok
PS 1 Output      | 190 Watts         | ok
PS_Volt_Out_01   | 12 Volts          | ok
PS_Volt_In_01    | 205 Volts         | ok
PS_Curr_Out_01   | 15.80 Amps        | ok
PS_Curr_In_01    | 1 Amps            | ok
PS 2 Output      | 180 Watts         | ok
PS_Volt_Out_02   | 12 Volts          | ok
PS_Volt_In_02    | 204 Volts         | ok
PS_Curr_Out_02   | 15.10 Amps        | ok
PS_Curr_In_02    | 0.90 Amps         | ok
27.1-LOM-Communi | 68 degrees C      | ok
28.1-LOM Card-I/ | 84 degrees C      | ok
25.1-HD Controll | 39 degrees C      | ok
25.2-HD Controll | 45 degrees C      | ok
25.3-HD Controll | 41 degrees C      | ok
LOM_Link_P1      | 0x02              | ok
LOM_Link_P2      | Not Readable      | ns
LOM_Link_P3      | Not Readable      | ns
LOM_Link_P4      | Not Readable      | ns
ALOM_Link_P1     | 0x02              | ok
ALOM_Link_P2     | 0x02              | ok
Dr_Stat_1I1_B001 | 0x01              | ok
Dr_Stat_2I1_B005 | 0x01              | ok
CPU_Stat_C1      | 0x80              | ok
CPU_Stat_C2      | 0x80              | ok

I found the first step. It's looking for the vendor as the whole name proliant dl360p gen8

Then I have a few working, and several that don't.

Works: Total Power, CPUs Temp, Fans Speed.

@olivierlambert With the new IPMI plugin for XO I was hoping to see support for HP servers. But at least it seems I can add it to my installation and then post my results.

I added "hp" as a vendor and all of the plugin settings (if you leave it blank there is an error when saving).

But I still see no sensor data for the hosts in XO.

Any thoughts on what I should add? check? do? to make it work?

@florent As a note, I'm using Debian as the base OS for XO. Other OS, like Ubuntu may have other name conflicts...

As for links, the dropdown box should show the link and it's destination). As a link, I don't think you need to "follow" it when selected (like a directory would), it's just a file. I did not check other non-standard files (like devices).

If I select a directory to restore then it would be good if the links are included. Both tar and zip do support links, so they should be restorable.

@florent Ubuntu LVM file restore is working! (commit 38931)

Now for another important issue I noticed with file restore (not directly LVM).

Symbolic links don't show up. They should be restorable alone, but more importantly you need to be able to see and follow them for directories.

For example. In Ubuntu, /bin is a link to /usr/bin. It is important to be able to click on /bin as a link to /usr/bin so files can be found in the backup. Another example is /vmlinuz that is a link to boot/vmlinuz-5.10.0-44-amd64. At worst the file restore should show a link (and it's destination), even if I can't restore the link. This is not just a LVM issue.

@florent LVM restore still failed for me (fix_flr commit b7230). Trying file restore from Ubuntu 22 VM (on S3 delta backup). Single VDI, 3 partitions (bios, uefi boot, LVM root). Accessing the LVM root.

Jun  5 15:26:28 xo2 kernel: [16230.122916] loop5: detected capacity change from 0 to 21474836480
Jun  5 15:26:35 xo2 xo-server[4046]: 2026-06-05T19:26:35.793Z xo:api WARN admin | backupNg.listFiles(...) [146ms] =!> Error: Command failed: mount --options=loop,ro,sizelimit=20397948928,offset=1075838976 --source=/tmp/ouit10u6k3f/vhd0 --target=/tmp/d4l0v4n01h
Jun  5 15:26:35 xo2 xo-server[4046]: mount: /tmp/d4l0v4n01h: unknown filesystem type 'LVM2_member'.

@rzr Installed and running. Not expecting any issues because I'm not using SMB/CIFS, ice card, or CPU with affected microcode.

Rolling pool reboot failed me again... This time it got stuck evacuating a host with no VMs.

@bleader A note on the option screen VM restart required to use new value is good enough. No realtime/live change needed. I'm just looking for quick easy GUI option rather than XPC CLI.

@olivierlambert Any chance of revisiting this issue and allowing a VM VIF MTU to be changed from XO? If not in the main display (where it shows the MTU), then in the Advanced settings window (which seems like a good and easy place to have the MTU option).

I have a small XCP server that has MTU 9000 set on the main (and only) interface but most VMs need to be set to 1500. The windows Xen network driver just inherits the MTU from XCP. Yes, you can use the CLI in Windows or XCP to change it, but it would be nice to have it in XO for that VIF (VM restart required).

@rzr Update installed and running on pools. Normal operations seem good. Had some issues with rolling pool reboot, but that happens a lot (unrelated to updates). An updated bind-utils would be nice, and any other SSL affected packages.

@pierrebrunet It's a warning. Backup job is successful.

@pierrebrunet The error happens using Wasabi and MinIO. The pbt_fix_warning_backup still has the error (but no 404 error):

Clean VM directory 
 missing target of alias

Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.571Z xo:backups:MixinBackupWriter INFO Disk chain needs merging { count: 1 }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.571Z xo:backups:MixinBackupWriter INFO merging disk chain {
Jun 01 11:23:22 xo2 xo-server[4216]:   chain: [
Jun 01 11:23:22 xo2 xo-server[4216]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd',
Jun 01 11:23:22 xo2 xo-server[4216]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152256Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]:   ]
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.741Z xo:backups:MixinBackupWriter WARN missing target of alias {
Jun 01 11:23:22 xo2 xo-server[4216]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.741Z xo:backups:MixinBackupWriter INFO removing alias with missing target {
Jun 01 11:23:22 xo2 xo-server[4216]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T152042Z.alias.vhd'
Jun 01 11:23:22 xo2 xo-server[4216]: }
Jun 01 11:23:22 xo2 xo-server[4216]: 2026-06-01T15:23:22.866Z xo:backups:worker INFO backup has ended

@pierrebrunet XO updated to master daefcab, same issue (delta backup S3, problem at merge).

I tried running backup several times to see if the error would clear (it did not). I tried deleting the backup and starting with a new full, error happened at the merge again.

Jun 01 10:07:24 xo2 xo-server[9341]: 2026-06-01T14:07:24.037Z xo:backups:MixinBackupWriter INFO Disk chain needs merging { count: 1 }
Jun 01 10:07:24 xo2 xo-server[9341]: 2026-06-01T14:07:24.039Z xo:backups:MixinBackupWriter INFO merging disk chain {
Jun 01 10:07:24 xo2 xo-server[9341]:   chain: [
Jun 01 10:07:24 xo2 xo-server[9341]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T134029Z.alias.vhd',
Jun 01 10:07:24 xo2 xo-server[9341]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T134306Z.alias.vhd'
Jun 01 10:07:24 xo2 xo-server[9341]:   ]
Jun 01 10:07:24 xo2 xo-server[9341]: }
Jun 01 10:07:24 xo2 xo-server[9341]: 2026-06-01T14:07:24.318Z xo:backups:MixinBackupWriter WARN unhandled error while checking alias {
Jun 01 10:07:24 xo2 xo-server[9341]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260601T134029Z.alias.vhd',
Jun 01 10:07:24 xo2 xo-server[9341]:   err: NotFound: UnknownError
Jun 01 10:07:24 xo2 xo-server[9341]:       at S3RestXmlProtocol.handleError (/opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1850:27)
Jun 01 10:07:24 xo2 xo-server[9341]:       at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
Jun 01 10:07:24 xo2 xo-server[9341]:       at async S3RestXmlProtocol.deserializeResponse (/opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:424:13)
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:27:24
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:387:20
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:64:28
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:91:20
Jun 01 10:07:24 xo2 xo-server[9341]:       at async /opt/xo/xo-builds/xen-orchestra-202606010843/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:5:26
Jun 01 10:07:24 xo2 xo-server[9341]:       at async S3Handler._getSize (/opt/xo/xo-builds/xen-orchestra-202606010843/@xen-orchestra/fs/dist/s3.js:304:20) {
Jun 01 10:07:24 xo2 xo-server[9341]:     '$fault': 'client',
Jun 01 10:07:24 xo2 xo-server[9341]:     '$retryable': undefined,
Jun 01 10:07:24 xo2 xo-server[9341]:     '$metadata': {
Jun 01 10:07:24 xo2 xo-server[9341]:       httpStatusCode: 404,
Jun 01 10:07:24 xo2 xo-server[9341]:       requestId: '18B4FA31C10C3A3E',
Jun 01 10:07:24 xo2 xo-server[9341]:       extendedRequestId: 'a18350611414fa9366e109699727e695e309120afc9803fcaff78a199f9bc4d6',
Jun 01 10:07:24 xo2 xo-server[9341]:       cfId: undefined,
Jun 01 10:07:24 xo2 xo-server[9341]:       attempts: 1,
Jun 01 10:07:24 xo2 xo-server[9341]:       totalRetryDelay: 0
Jun 01 10:07:24 xo2 xo-server[9341]:     }
Jun 01 10:07:24 xo2 xo-server[9341]:   }
Jun 01 10:07:24 xo2 xo-server[9341]: }
Jun 01 10:07:24 xo2 xo-server[9341]: 2026-06-01T14:07:24.490Z xo:backups:worker INFO backup has ended

@rzr nslookup is broken, but it was before this update too.

nslookup vates.com 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   vates.com
Address: 104.21.52.238
Name:   vates.com
Address: 172.67.205.118

openssl_link.c:132: INSIST(dst__memory_pool != ((void *)0)) failed, back trace
#0 0x7fb705ab80e7 in ??
#1 0x7fb705ab803a in ??
#2 0x7fb7066c5780 in ??
#3 0x7fb704ed0df6 in ??
#4 0x7fb704f17464 in ??
#5 0x7fb704f17732 in ??
#6 0x7fb704f16b8d in ??
#7 0x7fb703681bd9 in ??
#8 0x7fb703681c27 in ??
#9 0x7fb70366a44c in ??
#10 0x405818 in ??
Aborted (core dumped)

@pierrebrunet I still see the same error....

 Clean VM directory 
 unhandled error while checking alias

@julienXOvates Correct, latest XO branch is the problem. It was fine before...

{
  "data": {
    "mode": "delta",
    "reportWhen": "never"
  },
  "id": "1780192695536",
  "jobId": "d6c0a656-62c5-4c39-a57a-f246b39f1cef",
  "jobName": "minio-test",
  "message": "backup",
  "scheduleId": "bd4ef436-fd85-4f16-bf9e-71d1d0c8586f",
  "start": 1780192695536,
  "status": "success",
  "tasks": [
    {
      "id": "0mpt4ron3-juzrilzvn0s",
      "start": 1780192697727,
      "status": "success",
      "tasks": [
        {
          "id": "0mpt4ron9-pxah6gpi19",
          "start": 1780192697733,
          "status": "success",
          "end": 1780192698044,
          "result": {
            "merge": false,
            "size": 0
          },
          "message": "clean-vm"
        },
        {
          "id": "0mpt4rpwm-ujzdf5a8ad",
          "start": 1780192699366,
          "status": "success",
          "end": 1780192700817,
          "result": "0d3f6e5e-fd58-7368-7d54-c892809927b6",
          "message": "snapshot"
        },
        {
          "id": "0mpt4rr0x-sfehspx3ey",
          "start": 1780192700817,
          "status": "success",
          "tasks": [
            {
              "id": "0mpt4rsdg-t05980lobz",
              "start": 1780192702564,
              "status": "success",
              "end": 1780192702622,
              "result": {
                "size": 43008
              },
              "message": "transfer"
            },
            {
              "id": "0mpt4rts7-5p0b0d1r94y",
              "start": 1780192704391,
              "status": "success",
              "tasks": [
                {
                  "id": "0mpt4rtvx-0rtl320os8g",
                  "start": 1780192704525,
                  "status": "success",
                  "end": 1780192704782,
                  "message": "merge"
                }
              ],
              "warnings": [
                {
                  "data": {
                    "alias": "/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260531T015641Z.alias.vhd",
                    "err": {
                      "$fault": "client",
                      "$metadata": {
                        "httpStatusCode": 404,
                        "requestId": "18B483D548936DAB",
                        "extendedRequestId": "a18350611414fa9366e109699727e695e309120afc9803fcaff78a199f9bc4d6",
                        "attempts": 1,
                        "totalRetryDelay": 0
                      },
                      "name": "NotFound",
                      "message": "UnknownError"
                    }
                  },
                  "message": "unhandled error while checking alias"
                }
              ],
              "end": 1780192704964,
              "result": {
                "merge": true,
                "size": 8235471872
              },
              "message": "clean-vm"
            }
          ],
          "end": 1780192704964,
          "message": "export",
          "data": {
            "id": "9890e0c4-ba3a-4810-8245-a49fdf16b16e",
            "isFull": false,
            "type": "remote"
          }
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        },
        {
          "message": "will delete snapshot data"
        },
        {
          "data": {
            "vdiRef": "OpaqueRef:50cca589-9c8c-478c-dac8-56debab464bb"
          },
          "message": "Snapshot data has been deleted"
        }
      ],
      "end": 1780192704964,
      "message": "backup VM",
      "data": {
        "id": "a081f208-4e40-2ca5-c68e-86106af5a8ef",
        "type": "VM",
        "name_label": "Utest"
      }
    }
  ],
  "end": 1780192704964,
  "infos": [
    {
      "data": {
        "vms": [
          "a081f208-4e40-2ca5-c68e-86106af5a8ef"
        ]
      },
      "message": "vms"
    }
  ]
}

May 30 21:58:24 xo2 xo-server[1180]: 2026-05-31T01:58:24.525Z xo:backups:MixinBackupWriter INFO Disk chain needs merging { count: 1 }
May 30 21:58:24 xo2 xo-server[1180]: 2026-05-31T01:58:24.526Z xo:backups:MixinBackupWriter INFO merging disk chain {
May 30 21:58:24 xo2 xo-server[1180]:   chain: [
May 30 21:58:24 xo2 xo-server[1180]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260531T015641Z.alias.vhd',
May 30 21:58:24 xo2 xo-server[1180]:     '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260531T015759Z.alias.vhd'
May 30 21:58:24 xo2 xo-server[1180]:   ]
May 30 21:58:24 xo2 xo-server[1180]: }
May 30 21:58:24 xo2 xo-server[1180]: 2026-05-31T01:58:24.788Z xo:backups:MixinBackupWriter WARN unhandled error while checking alias {
May 30 21:58:24 xo2 xo-server[1180]:   alias: '/xo-vm-backups/a081f208-4e40-2ca5-c68e-86106af5a8ef/vdis/d6c0a656-62c5-4c39-a57a-f246b39f1cef/cbb7809e-8296-4dc6-8200-ed1f42e50c68/20260531T015641Z.alias.vhd',
May 30 21:58:24 xo2 xo-server[1180]:   err: NotFound: UnknownError
May 30 21:58:24 xo2 xo-server[1180]:       at S3RestXmlProtocol.handleError (/opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1850:27)
May 30 21:58:24 xo2 xo-server[1180]:       at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
May 30 21:58:24 xo2 xo-server[1180]:       at async S3RestXmlProtocol.deserializeResponse (/opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:424:13)
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:27:24
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:387:20
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:64:28
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:91:20
May 30 21:58:24 xo2 xo-server[1180]:       at async /opt/xo/xo-builds/xen-orchestra-202605291150/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:5:26
May 30 21:58:24 xo2 xo-server[1180]:       at async S3Handler._getSize (/opt/xo/xo-builds/xen-orchestra-202605291150/@xen-orchestra/fs/dist/s3.js:304:20) {
May 30 21:58:24 xo2 xo-server[1180]:     '$fault': 'client',
May 30 21:58:24 xo2 xo-server[1180]:     '$retryable': undefined,
May 30 21:58:24 xo2 xo-server[1180]:     '$metadata': {
May 30 21:58:24 xo2 xo-server[1180]:       httpStatusCode: 404,
May 30 21:58:24 xo2 xo-server[1180]:       requestId: '18B483D548936DAB',
May 30 21:58:24 xo2 xo-server[1180]:       extendedRequestId: 'a18350611414fa9366e109699727e695e309120afc9803fcaff78a199f9bc4d6',
May 30 21:58:24 xo2 xo-server[1180]:       cfId: undefined,
May 30 21:58:24 xo2 xo-server[1180]:       attempts: 1,
May 30 21:58:24 xo2 xo-server[1180]:       totalRetryDelay: 0
May 30 21:58:24 xo2 xo-server[1180]:     }
May 30 21:58:24 xo2 xo-server[1180]:   }
May 30 21:58:24 xo2 xo-server[1180]: }
May 30 21:58:24 xo2 xo-server[1180]: 2026-05-31T01:58:24.964Z xo:backups:worker INFO backup has ended

@julienxovates Let me know if you want me to test a different branch.

@olivierlambert With the new XO update (Master, commit 79b87) I now see the warning/error:

When doing S3 delta backups and it does a merge. When there is no merge, there is no error.

The file it is looking for 20260529T174722Z.alias.vhd was there, but was removed by XO.

I think it 's related to @pierrebrunet 100f11308a5a0dbf7e067317dc778241efdaab5c