Critical failure in systemd, zpool is unusable

K

Kingneutron

Renowned Member
Feb 21, 2024
1,240
475
93
github.com
After removing a failing cache drive, proxmox 9.1.4 with kernel 6.17.4-2-pve

This happened after an update, so (On Monday) I rolled the system snapshot back to Friday and it has been running OK all week until this test.

2026-01-23T19:20:50.418577-07:00 proxmox-mac3 pvestatd[2535]: zfs error: cannot open 'ztosh16': no such pool#012
2026-01-23T19:20:52.931377-07:00 proxmox-mac3 zed: eid=172 class=pool_import pool='ztosh16'
2026-01-23T19:20:52.931497-07:00 proxmox-mac3 zed: eid=171 class=config_sync pool='ztosh16'
2026-01-23T19:20:53.183547-07:00 proxmox-mac3 zed: eid=174 class=config_sync pool='ztosh16'
2026-01-23T19:20:53.766609-07:00 proxmox-mac3 kernel: zd80: p1 p2 p3
2026-01-23T19:20:53.901604-07:00 proxmox-mac3 kernel: zd112: p1 p2
2026-01-23T19:20:54.012635-07:00 proxmox-mac3 kernel: zd128: p1 p2 < p5 >
2026-01-23T19:20:54.162606-07:00 proxmox-mac3 kernel: zd144: p1 p2
2026-01-23T19:20:54.226603-07:00 proxmox-mac3 kernel: zd160: p1 p2 p3
2026-01-23T19:20:54.320992-07:00 proxmox-mac3 lvm[1973832]: /dev/zd160p3 excluded: device is rejected by filter config.
2026-01-23T19:20:54.330630-07:00 proxmox-mac3 kernel: zd192: p1 p2 < p5 >
2026-01-23T19:20:54.376608-07:00 proxmox-mac3 kernel: zd208: p1 p2 p3
2026-01-23T19:20:54.452310-07:00 proxmox-mac3 lvm[1973858]: /dev/zd208p3 excluded: device is rejected by filter config.
2026-01-23T19:20:54.497606-07:00 proxmox-mac3 kernel: zd256: p1
2026-01-23T19:20:54.649608-07:00 proxmox-mac3 kernel: zd272: p1 p2 p3
2026-01-23T19:20:54.769606-07:00 proxmox-mac3 kernel: zd288: p1
2026-01-23T19:20:54.867608-07:00 proxmox-mac3 kernel: zd304: p1
2026-01-23T19:20:55.171635-07:00 proxmox-mac3 systemd[1]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.171889-07:00 proxmox-mac3 systemd[2735]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.173136-07:00 proxmox-mac3 systemd[1]: Caught <ABRT>, from our own process.
2026-01-23T19:20:55.181570-07:00 proxmox-mac3 systemd[1]: Caught <ABRT>, dumped core as pid 1973899.
2026-01-23T19:20:55.181733-07:00 proxmox-mac3 systemd[1]: Freezing execution.
2026-01-23T19:20:55.218545-07:00 proxmox-mac3 (udev-worker)[1973719]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.219053-07:00 proxmox-mac3 systemd-udevd[668]: zfs-18: Worker [1973719] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.398866-07:00 proxmox-mac3 (udev-worker)[1973842]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.399063-07:00 proxmox-mac3 systemd-udevd[668]: zfs-19: Worker [1973842] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.474805-07:00 proxmox-mac3 (udev-worker)[1973717]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.474961-07:00 proxmox-mac3 systemd-udevd[668]: zfs-20: Worker [1973717] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.506445-07:00 proxmox-mac3 (udev-worker)[1973790]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.506638-07:00 proxmox-mac3 (udev-worker)[1973845]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.506862-07:00 proxmox-mac3 (udev-worker)[1973846]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.506899-07:00 proxmox-mac3 systemd-udevd[668]: zfs-21: Worker [1973790] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.506937-07:00 proxmox-mac3 systemd-udevd[668]: zfs-22: Worker [1973845] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.507010-07:00 proxmox-mac3 systemd-udevd[668]: zfs-23: Worker [1973846] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.661950-07:00 proxmox-mac3 (udev-worker)[1973841]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.662130-07:00 proxmox-mac3 systemd-udevd[668]: zfs-24: Worker [1973841] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.683258-07:00 proxmox-mac3 (udev-worker)[1973902]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.683391-07:00 proxmox-mac3 systemd-udevd[668]: zfs-25: Worker [1973902] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.720323-07:00 proxmox-mac3 (udev-worker)[1973903]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.720383-07:00 proxmox-mac3 systemd-udevd[668]: zfs-26: Worker [1973903] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.720555-07:00 proxmox-mac3 (udev-worker)[1973904]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.720674-07:00 proxmox-mac3 systemd-udevd[668]: zfs-27: Worker [1973904] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.762551-07:00 proxmox-mac3 (udev-worker)[1973907]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:55.762613-07:00 proxmox-mac3 systemd-udevd[668]: zfs-28: Worker [1973907] terminated by signal 6 (ABRT).
2026-01-23T19:20:55.940176-07:00 proxmox-mac3 systemd-udevd[668]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
2026-01-23T19:20:57.426364-07:00 proxmox-mac3 pvestatd[2535]: status update time (8.915 seconds)

Do you see that "Freezing execution"? There is NO recovery from that short of a full reboot. Systemd lost its damn mind.

I will attempt to import the zpool on another system, as it is unusable on my mac mini now
 
I think I figured out what happened. I did an rpool backup to ztosh16, which was fine until a reboot. Then the backup rpool datasets mounted over root and confused everything.

Was able to delete the rpool backup on another system and now ztosh16 appears to be doing fine back on its home server.
 
  • Like
Reactions: Onslow
You must log in or register to reply here.
Top Bottom
Back