Open mcint opened 8 months ago
I bumped into the same thing following the same how-to guide using Ubuntu 24.04 server image in an Aarch64 VM.
# zpool export -a
cannot export 'rpool': pool is busy
# uname -a
Linux testvm 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:32:42 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
In my case these were the processes listed by the command:
# grep rpool /proc/*/mounts | cut -d/ -f3 | uniq | xargs ps
PID TTY STAT TIME COMMAND
975 ? Ss 0:00 /usr/lib/systemd/systemd-resolved
976 ? Ssl 0:00 /usr/lib/systemd/systemd-timesyncd
1267 ? Ss 0:00 /usr/lib/systemd/systemd-networkd
1302 ? S<s 0:00 /usr/lib/systemd/systemd-logind
1309 ? Ssl 0:00 /usr/lib/polkit-1/polkitd --no-debug
1393 ? Ssl 0:00 /usr/sbin/ModemManager
Killing them allowed zpool export -a
to succeed.
I ran into this as well running Ubuntu 24.04 LTS server via a Live USB. If you remove polkitd
and add gpg-agentd
, the blocking processes for me were the same as @jstasiak. I this this may be related to doing the setup in an SSH session. Once I killed the blocking processes, the SSH session was killed, and I was able to successfully run zpool export -a
from the server's physical terminal.
As a note for anyone stumbling on this: I stopped the systemd sockets and services for all the processes unrelated to networking or SSH that had systemd services, and then ran a one-line systemctl stop <service1> && systemctl stop <service2> && kill -9 <PID>
for the remaining processes. The last command killed the SSH session, so I went over to the physical server and ran the final zpool export -a
at the server's terminal and it ran successfully. I was then able to reboot the server and continue.
System information
Describe the problem you're observing
Following openzfs "root on zfs" docs, I ran into an issue during step 5 grub installation at item 10 (or for practical scrolling purposes, just before step 6 first boot similar to #9606.
Killing these (and then fixing my display and NetworkManager, worked to fix my problem, but reporting as a rough edge.
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs