[SOLVED] Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.

gjkrisa

Member
Apr 2, 2023
40
2
13
i had proxmox host installed as ext4 and i wanted to change it to zfs so i could snapshot it to my zfs tank/mirror but after reinstalling and trying to zpool import -f Mirror i get errors that keep me from rebooting and if i force it then it will not boot.
is this a bug? is this fixable?

Sep 27 19:58:55 proxmox systemd[1]: Started user@0.service - User Manager for UID 0.
Sep 27 19:58:55 proxmox systemd[1]: Started session-1.scope - Session 1 of User root.
Sep 27 19:58:55 proxmox login[2103]: ROOT LOGIN ON pts/0
Sep 27 19:59:18 proxmox zed[2439]: eid=8 class=pool_import pool='Mirror'
Sep 27 19:59:18 proxmox zed[2437]: eid=7 class=config_sync pool='Mirror'
Sep 27 19:59:18 proxmox zed[2455]: eid=10 class=config_sync pool='Mirror'
Sep 27 19:59:19 proxmox systemd[2111]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 19:59:19 proxmox systemd[1]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 19:59:19 proxmox systemd[1]: Caught <ABRT>, from our own process.
Sep 27 19:59:19 proxmox systemd[1]: Caught <ABRT>, dumped core as pid 2501.
Sep 27 19:59:19 proxmox systemd[1]: Freezing execution.
Sep 27 19:59:19 proxmox systemd-logind[1372]: Removed session 2.
Sep 27 19:59:19 proxmox (sd-pam)[2113]: pam_unix(systemd-user:session): session closed for user root
Sep 27 19:59:19 proxmox (sd-pam)[2113]: pam_systemd(systemd-user:session): Failed to release session: No session '2' known
Sep 27 19:59:19 proxmox (udev-worker)[2438]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 19:59:19 proxmox systemd-udevd[771]: zfs-7: Worker [2438] terminated by signal 6 (ABRT).
Sep 27 19:59:19 proxmox (udev-worker)[2440]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 19:59:19 proxmox systemd-udevd[771]: zfs-8: Worker [2440] terminated by signal 6 (ABRT).
Sep 27 19:59:19 proxmox (udev-worker)[2502]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 19:59:19 proxmox systemd-udevd[771]: zfs-9: Worker [2502] terminated by signal 6 (ABRT).
Sep 27 19:59:47 proxmox chronyd[1462]: Selected source 173.11.101.155 (2.debian.pool.ntp.org)
Sep 27 20:00:40 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Connection refused
Sep 27 20:00:57 proxmox login[2103]: pam_unix(login:session): session closed for user root
Sep 27 20:00:57 proxmox pvedaemon[1762]: <root@pam> end task UPID:proxmox:00000830:00002557:68D8C08F:vncshell::root@pam: OK
Sep 27 20:01:22 proxmox dbus-daemon[1352]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Sep 27 20:01:22 proxmox systemd-logind[1372]: Failed to abandon session scope, ignoring: Connection timed out
Sep 27 20:01:22 proxmox systemd-logind[1372]: Session 1 logged out. Waiting for processes to exit.
Sep 27 20:01:48 proxmox dbus-daemon[1352]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Sep 27 20:02:13 proxmox dbus-daemon[1352]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Sep 27 20:02:13 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Sep 27 20:02:50 proxmox systemd-udevd[771]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Sep 27 20:03:40 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Sep 27 20:05:30 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Sep 27 20:06:40 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Sep 27 20:08:30 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
Sep 27 20:09:40 proxmox systemd-journald[746]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
 
ok i fixed it
it was created becasue i asked chat gpt to help me make a backup and it had me make a mount point that my Mirror/backup would mount to / "root directory for rpool"
so to find this:
zfs list -r -o name,mountpoint
i saw that i had one looked like this:
Name: Mountpoint
Mirror/ROOT/pve-1 /
so to fix that and keep it.
zfs set mountpoint=/mnt/Mirror/oldroot Mirror/ROOT/pve-1
or chat gpt says i can destroy it by:
zfs destroy -r Mirror/ROOT/pve-1
 
Last edited: