You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I've had an SLOG SSD brown-out on me and I've needed to force detach the device. I've since replaced the single SLOG with a mirrored SLOG, but I can't remove the old device. I've temporarily worked around the missing SLOG by zpool offline -f <pool> <dev> but removing it is probably the right thing to do.
All my attempts have been rebuffed by zpool no matter where from: initramfs, in a recovery boot, or under normal situations. It returns me cannot remove <guid>: Mount encrypted datasets to replay logs. despite having zfs mount -a.
The last request for information was #8748 (comment) where logs were requested. I've done that on my machine, it's quite long but the lines leading up to the -EBUSY look like:
This is running zfs 2.3.3 (dkms) on Ubuntu 24.04. Any help to debug this would be appreciated (and hopefully we can find a fix; otherwise I'd have to replicate my entire pool which may not be a bad idea...)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Related: #8748
Recently I've had an SLOG SSD brown-out on me and I've needed to force detach the device. I've since replaced the single SLOG with a mirrored SLOG, but I can't remove the old device. I've temporarily worked around the missing SLOG by
zpool offline -f <pool> <dev>
but removing it is probably the right thing to do.All my attempts have been rebuffed by zpool no matter where from: initramfs, in a recovery boot, or under normal situations. It returns me
cannot remove <guid>: Mount encrypted datasets to replay logs.
despite havingzfs mount -a
.The last request for information was #8748 (comment) where logs were requested. I've done that on my machine, it's quite long but the lines leading up to the -EBUSY look like:
This is running zfs 2.3.3 (dkms) on Ubuntu 24.04. Any help to debug this would be appreciated (and hopefully we can find a fix; otherwise I'd have to replicate my entire pool which may not be a bad idea...)
Beta Was this translation helpful? Give feedback.
All reactions