search

dasJ / sd-zfs

Compatibility between systemd and ZFS roots
MIT License
43 stars 13 forks source link

Filesystems not mounted #1

Closed lnicola closed 7 years ago

lnicola commented 8 years ago

I tried sd-zfs, but my root fs ended up in /sysroot/pool/fs instead of /sysroot, so switching the root didn't work. I'm using non-legacy mounts.

lnicola commented 8 years ago

Looks like my mountpoint was not set to / on my root filesystem. Not I can boot, but my other ZFS filesystems don't seem to get mounted, including /home, which makes things awkward. I'll try to look more into it.

dasJ commented 8 years ago

Does the current master work for you? I basically rewrote everything

dasJ commented 8 years ago

Sorry, the current AUR package will not work, I'll fix it asap

lnicola commented 8 years ago

All right, just ping me when it's fixed.

dasJ commented 8 years ago

Alright, can you test this PKGBUILD (including the preset file)?

Please re-read the readme, it has changed a lot and is not completely compatible to the previous version.

lnicola commented 8 years ago

All right, so I booted with root=zfs:pool/fs and everything seems fine!

dasJ commented 8 years ago

So can this be closed?

lnicola commented 8 years ago

Only after you push the new PKGBUILD to AUR 😁.

dasJ commented 8 years ago

That's fair. I'll release the new version once my own machine can boot. I'm currently having issues with encryption.

On Mon, Nov 7, 2016, 19:19 Laurentiu Nicola notifications@github.com wrote:

Only after you push the new PKGBUILD to AUR 😁.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/dasJ/sd-zfs/issues/1#issuecomment-258917029, or mute the thread https://github.com/notifications/unsubscribe-auth/AEvdx9bLueHRIe7rs44eeWKLTd_f58-Yks5q72ubgaJpZM4J9J3c .

dasJ commented 8 years ago

@lnicola So I just pushed to the AUR, I hope everything works now :shipit:

lnicola commented 8 years ago

Just checked that it's fine, thanks for your work.

obma commented 8 years ago

Sorry for reopening, but it seems I'm running into the same/smiliar issue - with the newest version from the AUR installed (1.0.0-1; first download and install today).

I have a rootfs filesystem with mountpoint / and seperate filesystems for /home, /boot, /root, /srv and /var (non-legacy) - and a /boot.sd to boot the initramfs from. On boot sysroot.mount fails. Importing the pool manually (zpool import -N mypool) and restarting sysroot.mount makes it possible to boot, but the other mountpoints aren't mounted then.

dasJ commented 8 years ago

@obma The problem is that mount(8) discards the output of the ZFS mounting tool. Can you execute mount.initrd_zfs directly (in the recovery shell)?

For me systemd executes:

mount -t initrd_zfs tank/root /sysroot -o zfsutil

So I execute in the shell:

mount.initrd_zfs tank/root /sysroot -o zfsutil

Note I removed the -t parameter.

obma commented 8 years ago

I switched back to not using systemd in the initrd and use the zfs hook for now (as I do on my older machines) - HOOKS="base udev autodetect modconf block keyboard zfs filesystems"

But I can test your suggestion on the weekend - if it helps you figuring out what's going on there.

dasJ commented 8 years ago

Thank you, I really hope I can fix it 😃

dasJ commented 7 years ago

Closing this for now. Please open a new issue once you could further investigate your problem. The cause of your problem is another than the cause of the OP.