To the plugin dev team...
Any
I figured that was causing the problem. Thank you for confirming it. @subzero79 and I trying to come up with a good solution.
Any good solution in sight ? no pressure
To the plugin dev team...
Any
I figured that was causing the problem. Thank you for confirming it. @subzero79 and I trying to come up with a good solution.
Any good solution in sight ? no pressure
To the plugin dev team...
Any
Any good solution in sight ? no pressure
take a look at my GitHub. Three branches there to test.
Also take note the fix is still missing migration script. The migration script will have to insert the current mntent uuid into every dataset property associated with the mntent using postinst.
Hello guys,
I have similar issues as I did some updates on my NAS.
This is what I'm currently running.
root@NAS:/# uname -a
Linux NAS 4.16.0-0.bpo.1-amd64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) x86_64 GNU/Linux
My zfs devices also disappeared and the whole plug-in didn't work any longer. I tried to remove it and re-install. When I try I get this: (partly german output)
OpenZFS root filesystem capabilities for Linux - initramfs
Vormals nicht ausgewähltes Paket openmediavault-zfs wird gewählt.
Vorbereitung zum Entpacken von .../8-openmediavault-zfs_4.0.2-1_amd64.deb ...
Entpacken von openmediavault-zfs (4.0.2-1) ...
linux-headers-amd64 (4.16+93~bpo9+1) wird eingerichtet ...
libuutil1linux (0.7.6-1~bpo9+1) wird eingerichtet ...
libnvpair1linux (0.7.6-1~bpo9+1) wird eingerichtet ...
Trigger für libc-bin (2.24-11+deb9u3) werden verarbeitet ...
zfs-dkms (0.7.6-1~bpo9+1) wird eingerichtet ...
Loading new zfs-0.7.6 DKMS files...
Building for 4.16.0-0.bpo.1-amd64
Building initial module for 4.16.0-0.bpo.1-amd64
Error! Bad return status for module build on kernel: 4.16.0-0.bpo.1-amd64 (x86_64)
Consult /var/lib/dkms/zfs/0.7.6/build/make.log for more information.
Trigger für openmediavault (4.1.6) werden verarbeitet ...
Restarting engine daemon ...
libzpool2linux (0.7.6-1~bpo9+1) wird eingerichtet ...
libzfs2linux (0.7.6-1~bpo9+1) wird eingerichtet ...
zfsutils-linux (0.7.6-1~bpo9+1) wird eingerichtet ...
Created symlink /etc/systemd/system/zfs-import.target.wants/zfs-import-cache.service → /lib/systemd/system/zfs-import-cache.service.
Created symlink /etc/systemd/system/zfs-mount.service.wants/zfs-import.target → /lib/systemd/system/zfs-import.target.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-import.target → /lib/systemd/system/zfs-import.target.
Created symlink /etc/systemd/system/zfs-share.service.wants/zfs-mount.service → /lib/systemd/system/zfs-mount.service.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-mount.service → /lib/systemd/system/zfs-mount.service.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-share.service → /lib/systemd/system/zfs-share.service.
Created symlink /etc/systemd/system/multi-user.target.wants/zfs.target → /lib/systemd/system/zfs.target.
zfs-import-scan.service is a disabled or a static unit, not starting it.
Job for zfs-mount.service failed because the control process exited with error code.
See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
zfs-mount.service couldn't start.
Job for zfs-share.service failed because the control process exited with error code.
See "systemctl status zfs-share.service" and "journalctl -xe" for details.
zfs-share.service couldn't start.
zfs-zed (0.7.6-1~bpo9+1) wird eingerichtet ...
Created symlink /etc/systemd/system/zed.service → /lib/systemd/system/zfs-zed.service.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-zed.service → /lib/systemd/system/zfs-zed.service.
openmediavault-zfs (4.0.2-1) wird eingerichtet ...
modprobe: FATAL: Module zfs not found in directory /lib/modules/4.16.0-0.bpo.1-amd64
dpkg: Fehler beim Bearbeiten des Paketes openmediavault-zfs (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Trigger für libc-bin (2.24-11+deb9u3) werden verarbeitet ...
Trigger für openmediavault (4.1.6) werden verarbeitet ...
Restarting engine daemon ...
Fehler traten auf beim Bearbeiten von:
openmediavault-zfs
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f3aa0a76730>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f3aa0a76730>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
E: Sub-process /usr/bin/dpkg returned an error code (1)
Alles anzeigen
Any idea?
Cheers
That is not the same issue as described in this thread.
You have moved to the 4.16 kernel. That won’t work yet until the repo has the latest ZFS. Move back to 4.15 and it will spring back to life.
See the end of this thread: Is ZFS supported in Kernel 4.13-4.15?
https://forum.openmediavault.o…rted-in-Kernel-4-13-4-15/
Sent from my iPhone using Tapatalk
Ok, thank you!
I set the Kernel on OMV Extras to 4.15 and then to 4.14. On both versions I get this while installing zfs:
Building for 4.14.0-0.bpo.3-amd64 4.16.0-0.bpo.1-amd64
Module build for kernel 4.14.0-0.bpo.3-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
root@NAS:~# uname -r
4.14.0-0.bpo.3-amd64
Any hint?
---
After re-installing the headers for 4.15 i got the zfs back online.
This is a bit off-topic for this thread, but yeah you need to make sure that you have the headers.
In my experience, people asking for help getting ZFS [back] up and running usually have one of 3 problems:
1. Contrib in sources - plugin/install fails > Add contrib to sources
2. Headers - Module build fails > install headers
3. Wrong kernel - Upgraded kernel and module fails = pools that were working disappear > move to previous kernel
Glad you got it working Enjoy
Hi, I had the same problem with the GUI and the config.xml. I was seeing the same error when trying to change the sharedfolders and ACL was greyed out as well. Copied from an old config.xml the filesystem part of my ZFS mount and everything works fine. trying to leave my finger off the zfs plugin from now on.
Seems that the plugin is creating the problem. ah and forgot to say, my kernel is 4.9
Solution (?) / Workaround
Since the omv installer refused to install to my USB-Stick, I followed the tip to use the debian installer and install omv 4.1.3 afterwards.
Because I did not get zfs installed (kernel 4.16.something) I installed 4.9.x. Now zfs works with the above mentioned problems.
To solve the disappearing problem of my imported pool i followed the tip from https://superuser.com/question…-after-reboot-on-debian-8 :
Uncaught OMV\Config\DatabaseException: Fatal error 5: Extra content at the end of the document (line=4, column=3)
Add a new file in /etc/modprobe.d/ with the content:
Now I try to follow this to add my missing Pool to devices to my /etc/openmediavault/config.xml
: Finding the correct mntent UUID for a filesystem not in config.xml
Not sure if this will work, but I'll let you know.
Perhaps that helps someone.
Update: Aargh. can't start the GUI anymore, after editing config.xml. I tried to insert the mntend part manually. Uncaught OMV\Config\DatabaseException: Fatal error 5: Extra content at the end of the document (line=4, column=3) . Of course I haven't made a backup BEFORE. Also after removing the stuff, it does not work anymore.
OK. My story: My old OMV3 got broken,so I tried to install OMV4. That did not work (broken installer). Then I installed nas4free. After I got this working I created a ZFS pool (1 HDD) and some hours later I finally had everything installed but had to find out that i cannot use the cirtualbox extension pack! Damn!
So I came back to OMV4, finally got it working, imported the ZFS pool and now I am here because of the zfs-problem (see post above)
After I screwed up my config.xml and since there was nothing important installed so far, I installed everything completely new.
Now my pool exists after reboot, but unfortunately my zfs pool still does not appear in the devices list. I also cannot remove it because it is not in the mntend-section.
Nevertheless this might be helpful?
Here are my few notes how I did this:
PLEASE DO NOT DO PLAIN COPY & PASTE!!! Please just use it as a possible orientation.
#######################
# install debian 9
#######################
### install debian minimal on usbstick. Part: 1.prim ~8GB, bootflag ; Part5 Log. Swp
# https://forum.openmediavault.org/index.php/Thread/21234-Install-OMV4-on-Debian-9-Stretch/
#######################
# install omv 4
#######################
cat <<EOF >> /etc/apt/sources.list.d/openmediavault.list
deb http://packages.openmediavault.org/public arrakis main
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis main
## Uncomment the following line to add software from the proposed repository.
# deb http://packages.openmediavault.org/public arrakis-proposed main
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis-proposed main
## This software is not part of OpenMediaVault, but is offered by third-party
## developers as a service to OpenMediaVault users.
# deb http://packages.openmediavault.org/public arrakis partner
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis partner
EOF
export LANG=C
export DEBIAN_FRONTEND=noninteractive
export APT_LISTCHANGES_FRONTEND=none
apt-get --allow-unauthenticated install openmediavault-keyring
apt-get update
apt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option Dpkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" install postfix openmediavault
#######################
# install OMV extras
#######################
#download deb from webpage
# upload to omv, activate and install
#######################
# install ZFS (not very useful from here on?)
#######################
echo "options zfs zfs_autoimport_disable=0" > /etc/modprobe.d/zfs.conf
apt install linux-headers-$(uname -r) openmediavault-omvextrasorg
apt install openmediavault-zfs
#here create backup from config.xml
#get uuid
blkid|grep zfs
####################################
#another way to reinstall ???
# apt-get purge openmediavault
# apt-get install openmediavault
Alles anzeigen
I was really curious about ZFS and wanted to give it a try, but for now I will go back to a simple Ext4-Drive to get OMV work.
If anyhow the OMV-ZFS plugin works, please let me know.
Guys so there is some workaround to this problem? Right now I can't share my mirror
Why are they even treating the whole shared folder thing the way they are? When I use the docker ui plugin i can browse to any area of my box's filesystems. The issue lays with the way shared folders is parsing the filesystems. My issues started with removing (aka. zfs destroy <FILESYSTEM_I_DIDNT_WANT_ANYMORE) an unwanted FS via the CLI. In the FreeBSD world that type of zfs change is normal. The whole OMV is a fantastic piece of software albeit it's issues and idiosyncrasies. The Docker UI to me is really the hidden gem of this software, the ability to load up an Automated HTPC within docker in what took less time than it did to write this post is amazing. *Sits back and watches some TV*
My issues started with removing (aka. zfs destroy <FILESYSTEM_I_DIDNT_WANT_ANYMORE) an unwanted FS via the CLI. In the FreeBSD world that type of zfs change is normal.
Shared folders in OMV use ZFS filesystems in the same way Shared folders use any other filesystem type. If a shared folder is attached to a ZFS filesystem, named FILESYSTEM_I_DIDNT_WANT_ANYMORE , the shared folder must be deleted before deleting the filesystem named FILESYSTEM_I_DIDNT_WANT_ANYMORE. This is logical. Otherwise a lot of high level configuration work could be destroyed with a low level mistake, such as accidentally deleting a filesystem. In essence, configuration items should be cleanly reversed.
This is a requirement for the GUI, to maintain internal processes that operate in the background, for accurately reporting the state of the system. If you bypass processes that should be done in the GUI, by using the CLI, OMV's internal database gets out of sync with the actual state of the system. And,, that's when problems crop up.
In the bottom line, it's best to use the GUI when and where it's possible. For standard configuration changes, the CLI should be reserved as a last resort.
I'd agree with you on the Docker Plugin. That's a stellar piece of code. And while it does have some issues, I think the ZFS plugin is adequate for most users. (Let's set aside the ZFS package issues with the 4.16 kernel, the headers, etc.)
Guys so there is some workaround to this problem? Right now I can't share my mirror
up. There is some way to resolve this?
up. There is some way to resolve this?
What are you looking for? A resolution (may take awhile) or a work around (potentially available, if you're willing to rebuild).
Note; if you clone or at least backup your current boot drive, you'd be able to back out of the following.
______________________________________________________
Look at this post. -> OMV4 with kernel 4.9.0 and ZFS 0.7.9-2
Notes:
- Unless you have cutting edge hardware, kernel 4.9.0 will be fine.
(In your case, you may have been running kernel 4.9.0 on your server, with OMV3.)
- Start with a clean build
- I created a new ZFS pool (So I don't know what the effects of importing an existing pool would be.)
______________________________________________________
The referenced build was on actual hardware (not a VM), and since kernel 4.9.0 is the default kernel for Debian (9) Stretch, package upgrades should be fine.
So i got the same problem, no accessable pool in the drop down menu. I reinstalled everything with newest omv4 and kernel 4.9.0-6, Plugin seems to work and i can mount the pool and see it and the folders in the command line. What do i have to do to access my data again, i'm unterstanding what the problem is but i don't now how to fix that? Could somebody please help meand tell me what to do...
Alles anzeigenWhat are you looking for? A resolution (may take awhile) or a work around (potentially available, if you're willing to rebuild).Note; if you clone or at least backup your current boot drive, you'd be able to back out of the following.
______________________________________________________
Look at this post. -> OMV4 with kernel 4.9.0 and ZFS 0.7.9-2
Notes:
- Unless you have cutting edge hardware, kernel 4.9.0 will be fine.
(In your case, you may have been running kernel 4.9.0 on your server, with OMV3.)
- Start with a clean build
- I created a new ZFS pool (So I don't know what the effects of importing an existing pool would be.)
______________________________________________________
The referenced build was on actual hardware (not a VM), and since kernel 4.9.0 is the default kernel for Debian (9) Stretch, package upgrades should be fine.
I can't delete my data right now Is this the only work around? If I boot with a kernel different from 4.16 can I resolve this?
Also after reading the post about BTRFS and OMV5 it's probably safer to go with BTRFS in case I will format my HDD
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!