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
In dracut the import of the pool takes place before the requred lv is active.
At boot time I got thrown in the rescue shell after a pool cannot be imported due to missing device.
In the shell I can import the pool without any issues and continue to boot further.
Describe how to reproduce the problem
I have reconfigured my disc due to the severe problems with swap on zvol. So I opted to an luks encrypted physical lvm volume (PV) with an logical volume for swap and one to house the zpool.
So my basic setup is:
With cry-VG-psyche_drive beeing the physical drive of my zpool.
There seem to be an runtime issue as the zpool import psyche seems to be run while the lvm activate has not yet finished/started.
I would have been tempted to simply rename contrib/dracut/90zfs to something like 95zfs, but I'm not knowlegable enough in the inner workings of dracut.
The text was updated successfully, but these errors were encountered:
System information
Describe the problem you're observing
In dracut the import of the pool takes place before the requred lv is active.
At boot time I got thrown in the rescue shell after a pool cannot be imported due to missing device.
In the shell I can import the pool without any issues and continue to boot further.
Describe how to reproduce the problem
I have reconfigured my disc due to the severe problems with swap on zvol. So I opted to an luks encrypted physical lvm volume (PV) with an logical volume for swap and one to house the zpool.
So my basic setup is:
With cry-VG-psyche_drive beeing the physical drive of my zpool.
There seem to be an runtime issue as the zpool import psyche seems to be run while the lvm activate has not yet finished/started.
I would have been tempted to simply rename contrib/dracut/90zfs to something like 95zfs, but I'm not knowlegable enough in the inner workings of dracut.
The text was updated successfully, but these errors were encountered: