![]() ![]() The mount still fails with an unable to open the dataset message. It now looks like the ZFS module does get loaded ahead of the systemd module loader service modules, and ahead of the mount command. ![]() If I add zfs to /etc/initramfs-tools/module, then update-initramfs -c -k all then update-grub, I see a change in behavior. Without any of those three lines, I don't see the 'Inserted module zfs' line, but I do see the companion line 'ZFS: loaded module' that comes after the module is installed.Īnyway, it appears that all of these attempts to force an early module load are not effective. When these are present, I see the line 'Inserted module zfs', but it comes after the failed attempt to mount the drive. There are three different ways that I can see the zfs module insertion in my boot: modules_load=zfs in my kernel boot command line, or adding the zfs line to /etc/modules-load.d/nf, or creating /etc/modules-load.d/zfs.conf with that line. So a workaround would be to use links instead of mounts - and if I can't solve this problem that's what I'll do. Part of the use case might clear up why I want legacy mounts - I have bind mounts that are being mounted in the ZFS file system. What little information is floating around out there seems to primarily deal with using zfs for the root file system, and in many cases that is a lot more complicated. From what I can see, it seems like installing zfs-initramfs is supposed to help with this - but how? I haven't been able to find a simple how-to for dealing with this. I can see the two events in the boot printout, it's pretty obvious what the problem is - but not the fix. Of course, later in the boot process the ZFS modules are loaded and it can be mounted properly. Process: 464 ExecMount=/bin/mount vagrant /home/vagrant -t zfs (code=exited, status=2)Īpr 30 11:41:07 ubuntu mount: The ZFS modules are not loaded.Īpr 30 11:41:07 ubuntu mount: Try running '/sbin/modprobe zfs' as root to load them.Īpr 30 11:41:07 ubuntu systemd: home-vagrant.mount: Mount process exited, code=exited status=2Īpr 30 11:41:07 ubuntu systemd: home-vagrant.mount: Failed with result 'exit-code'.Īpr 30 11:41:07 ubuntu systemd: Failed to mount /home/vagrant. ![]() It's obvious what the problem is - during startup the attempt to mount the drive is taking place before the ZFS modules are loaded: $ systemctl status home-vagrant.mountĪctive: failed (Result: exit-code) since Thu 11:41:07 PDT 24s ago If I set my legacy mount as noauto and then manually mount after startup, everything works fine.īut when I remove noauto, I fail to automatically mount at boot. However, I have a use case that would be helped if I could use legacy mounts that auto mount at boot time. Everything works fine when creating and mounting file systems using normal mountpoints. I'm using zfs on a generic Ubuntu 18.04 system. ![]()
0 Comments
Leave a Reply. |