yes, it works.... perfect.
I didn't dare to push the button ... but now i see the filesystem and can share them
Thanks a lot
yes, it works.... perfect.
I didn't dare to push the button ... but now i see the filesystem and can share them
Thanks a lot
1. Yes omv-extras are installed on OMV
2. Yes i have installed openmediavault-zfs plugin for OMV after installation omv + omv extras
3.
root@openmediavault:~# uname -a
Linux openmediavault 6.12.12+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.12-1~bpo12+1 (2025-02-23) x86_64 GNU/Linux
4.
root@openmediavault:~# zpool status
pool: mnnas
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: resilvered 10.3M in 00:00:14 with 0 errors on Sun Feb 2 12:23:30 2025
config:
NAME STATE READ WRITE CKSUM
mnnas ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
sde ONLINE 0 0 0
sdf ONLINE 0 0 0
sdg ONLINE 0 0 0
errors: No known data errors
Display More
can you explain how i install a proxmox Kernel... is there a how to?
From my current OMV 7.7.0-2 I have a ZFS pool that is mouted to /mnt. The Debian Update I was offered then destroyed my current version so that the NAS could no longer boot. A reinstallation of OMV 7.7.0-2 works, however, I can no longer release my ZFS pool for an NFS connection, since I only ever appear the other systems such as XFS, EXT4 etc. as release medium. Does anyone have any info for me how I can release the Pool, which is mounted /mnt via NFS?
Thank you..
Nachdem mir mein NAS letztens 64 Updates für Debian angeboten hatte ist mein Server danach nicht mehr gebootet. Eine Neuinstallation von omv 7.7.0-2 klappte zwar, auch die Neuinstallation des zfs Plugins ging und ich konnte meinen Pool auch wieder importieren... aber ich bringe nun keine Freigabe des Pools per NFS in meinem Netzwerk mehr hin, da ich über das omv GUI immer nur EXT4, XFS oder BTRFS Filesysteme hier freigeben kann. Hat sich da etwas in der letzten Zeit geändert oder habe ich einen Gedankenfehler?
Hi,
i think, that i have also this problem...
Fehler #0:
OMV\Config\DatabaseException: Failed to execute XPath query '//system/fstab/mntent[uuid='fb155b1d-1a3c-4e33-97a6-2578ea094971']'. in /usr/share/php/openmediavault/config/database.inc:78
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(231): OMV\Config\Database->get('conf.system.fil...', 'fb155b1d-1a3c-4...')
#1 [internal function]: OMVRpcServiceShareMgmt->get(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'get', Array, Array, 1)
#5 {main}
my pool is aviable, but the disk`s in the zfs pool are not seen in omv gui.
How has you solved the Problem? With delete the devices and fresh rescan of them?
Ich habe vor ca. 4 Wochen mein OMV 4.x genauso wie die es beschrieben hast verkleinert.. Und ich kann auch den nun freien noch unpartitionierten Bereich nutzen. Dieser Platz steht in OMV ohne Einschränkung zur Verfügung. Ich kann unter 4.0.14 arakis das also nicht nachvollziehen.
I have the same failure.. I read now in this board that the Problem can be solved with an second DNS Server entry for example 8.8.8.8 in the network configs...
For me, i have not tested this at the moment.. Because i installed my backup without plex..
You can test..
Hi,
i installed the plexserver and after register an Login on Webseite /myNASIP:32400 i get the Info on the right side of the window "Looking for Servers", but my Server seems not existing? only the website is aviable. So i can not finish the server installation.
So i cant`t get use Plexmediaserver. Must i install some more packages?
Hi Krisbee,
yes i have access to the ZFS pool with Kernel linux-image-4.9.0-4-amd64... there is no problem.
But i think if i install the upgrade Package i will get the same error while building the Kernel for 4.13 i posted..
Here the Log of Kernel built in first Installation if someone need this.
But i understand, i can built new Kernel 4.13.. if fail i can delete the 4.13 kernel incl. headers (But i don`t need the Kernel in the Moment)
So i disable the Line "deb http...." in
/etc/apt/sources.list.d/openmediavault-kernel-backports.list
Thats the entry i searched..
And after disable this entry and reboot and a refresh of the Updatelist i don`t get the new updates for the bpo Kernels.
Thats what i whised... Perfect thanks a lot
If disabling of the bpo repo make a problem.. let me know what i should do..
Here is the output from
root@openmediavaultnas:~# dpkg -l | grep linux-
root@openmediavaultnas:~# dpkg -l | grep linux-
ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel
ii firmware-linux-nonfree 20161130-3~bpo8+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
ii linux-base 4.5 all Linux image base package
ii linux-compiler-gcc-4.9-x86 4.9.51-1~bpo8+1 amd64 Compiler for Linux on x86 (meta-package)
ii linux-compiler-gcc-6-x86 4.9.51-1 amd64 Compiler for Linux on x86 (meta-package)
ii linux-headers-4.9.0-0.bpo.4-amd64 4.9.51-1~bpo8+1 amd64 Header files for Linux 4.9.0-0.bpo.4-amd64
ii linux-headers-4.9.0-0.bpo.4-common 4.9.51-1~bpo8+1 all Common header files for Linux 4.9.0-0.bpo.4
ii linux-headers-4.9.0-4-amd64 4.9.51-1 amd64 Header files for Linux 4.9.0-4-amd64
ii linux-headers-4.9.0-4-common 4.9.51-1 all Common header files for Linux 4.9.0-4
ii linux-headers-amd64 4.9+80+deb9u2 amd64 Header files for Linux amd64 configuration (meta-package)
ii linux-image-4.9.0-4-amd64 4.9.51-1 amd64 Linux 4.9 for 64-bit PCs
ii linux-image-amd64 4.9+80+deb9u2 amd64 Linux for 64-bit PCs (meta-package)
ii linux-kbuild-4.9 4.9.51-1 amd64 Kbuild infrastructure for Linux 4.9
ii linux-libc-dev:amd64 4.9.51-1 amd64 Linux support headers for userspace development
Display More
i don`t know why i get after apt-get update always
Ign:6 file:/var/cache/openmediavault/archives Translation-de
OK:7 http://packages.openmediavault.org/public arrakis InRelease
Ign:8 http://ftp.de.debian.org/debian stretch InRelease
OK:9 http://ftp.de.debian.org/debian stretch Release
OK:10 http://security.debian.org stretch/updates InRelease
OK:13 https://openmediavault.github.io/packages arrakis InRelease
Ign:14 https://dl.bintray.com/openmed…plugin-developers/arrakis stretch InRelease
Holen:15 https://dl.bintray.com/openmed…plugin-developers/arrakis stretch Release [4.389 B]
OK:15 https://dl.bintray.com/openmed…plugin-developers/arrakis stretch Release
Holen:11 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease [91,8 kB]
Es wurden 91,8 kB in 2 s geholt (41,0 kB/s).
Paketlisten werden gelesen... Fertig
the debian stretch-backports...
is there so,eting else i must do ?
In my source.list in /etc/apt/source.list
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20170731-21:43]/ s$
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20170731-21:43]/ st$
deb http://ftp.de.debian.org/debian/ stretch main
deb-src http://ftp.de.debian.org/debian/ stretch main
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# stretch-updates, previously known as 'volatile'
# deb http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free
# deb-src http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free
is no bpo source i mean..
here is the output..
root@openmediavaultnas:~# dpkg -l | grep linux
ii console-setup-linux 1.164 all Linux specific part of console-setup
ii firmware-linux 20161130-3~bpo8+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel
ii firmware-linux-nonfree 20161130-3~bpo8+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
ii libnvpair1linux 0.6.5.9-2~bpo8+1 amd64 Solaris name-value library for Linux
ii libselinux1:amd64 2.6-3+b3 amd64 SELinux runtime shared libraries
ii libuutil1linux 0.6.5.9-2~bpo8+1 amd64 Solaris userland utility library for Linux
ii libzfs2linux 0.6.5.9-2~bpo8+1 amd64 OpenZFS filesystem library for Linux
ii libzpool2linux 0.6.5.9-2~bpo8+1 amd64 OpenZFS pool library for Linux
ii linux-base 4.5 all Linux image base package
ii linux-compiler-gcc-4.9-x86 4.9.51-1~bpo8+1 amd64 Compiler for Linux on x86 (meta-package)
ii linux-compiler-gcc-6-x86 4.9.51-1 amd64 Compiler for Linux on x86 (meta-package)
ii linux-headers-4.9.0-0.bpo.4-amd64 4.9.51-1~bpo8+1 amd64 Header files for Linux 4.9.0-0.bpo.4-amd64
ii linux-headers-4.9.0-0.bpo.4-common 4.9.51-1~bpo8+1 all Common header files for Linux 4.9.0-0.bpo.4
ii linux-headers-4.9.0-4-amd64 4.9.51-1 amd64 Header files for Linux 4.9.0-4-amd64
ii linux-headers-4.9.0-4-common 4.9.51-1 all Common header files for Linux 4.9.0-4
ii linux-headers-amd64 4.9+80+deb9u2 amd64 Header files for Linux amd64 configuration (meta-package)
ii linux-image-4.9.0-4-amd64 4.9.51-1 amd64 Linux 4.9 for 64-bit PCs
ii linux-image-amd64 4.9+80+deb9u2 amd64 Linux for 64-bit PCs (meta-package)
ii linux-kbuild-4.9 4.9.51-1 amd64 Kbuild infrastructure for Linux 4.9
ii linux-libc-dev:amd64 4.9.51-1 amd64 Linux support headers for userspace development
ii util-linux 2.29.2-1 amd64 miscellaneous system utilities
ii zfsutils-linux 0.6.5.9-2~bpo8+1 amd64 command-line tools to manage OpenZFS filesystems
root@openmediavaultnas:~# dpkg -l | grep linux-image
ii linux-image-4.9.0-4-amd64 4.9.51-1 amd64 Linux 4.9 for 64-bit PCs
ii linux-image-amd64 4.9+80+deb9u2 amd64 Linux for 64-bit PCs (meta-package)
Display More
there is no Kernel 4.13 longer avaible... but in WebGUI i got always the *.bpo File for update
should i install all packages and then remove the Kernel again ?
But i think it should be possible to change the setting to get no bpo updates longer.. or not?
In omv GUI i can see 3 Kernels after Upgrade from 3.x to 4.x and following first update over the omv menu i see the new Kernel`s.
I`m right that kernel`s with bpo in wording are Backport Kernels? Do i need this kernels ? or can they deleted ?
What is to do, that i not get updates for these Backportkernels?
My Updatelist is full with "bpo" Updates
Now, i make the update over webgui and after reboot the zfs pool is aviable.
But i now get again the updates to Version "Installationskandidat: 4.13+86~bpo9+1"
And when i read, that this kernel is not stable why i get this as update? I think i use stable repos..
Output of zfs list and modprobe zfs
root@openmediavaultnas:~# zfs list
The ZFS modules are not loaded.
Try running '/sbin/modprobe zfs' as root to load them.
root@openmediavaultnas:~# /sbin/modprobe zfs
modprobe: FATAL: Module zfs not found in directory /lib/modules/4.9.0-0.bpo.4-amd64
looks like somthing is missing in kernel ?
I upgraded again from omv 3.0.90 by using cmd: omv-release-upgrade
After reboot, my zfs pool can`t get mounted..
I get this Error..
I hope this can be solved? Now solved
My output
root@openmediavaultnas:~# apt-cache policy linux-image-amd64
linux-image-amd64:
Installiert: 4.9+80+deb9u2
Installationskandidat: 4.13+86~bpo9+1
Versionstabelle:
4.13+86~bpo9+1 500
100 http://httpredir.debian.org/debian stretch-backports/main amd64 Pack ages
*** 4.9+80+deb9u2 500
500 http://ftp.de.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status
root@openmediavaultnas:~#
Display More
Hi,
first sorry for me english..
Today I upgraded my omv Version from 3.0.90 to 4.0.9-1 (Arrakis).. and this version is running now with Kernel 4.9.0-0.bpo.4-amd64.
Now i get the Info for new updates and so i get them and by the way i get Kernel 4.13 and there is now the problem, that ZFS will not run.
The update Log shows some errors and while build the Kernel 4.13 and the zfs Pool ist not aviable after boot this Kernel.
Here the Log from update..
So i set as prefered Kernel is 4.9.0-0.bpo.4-amd64 because here is ZFS running. Is there no support for 4.13 and ZFS Pool? And can I remove this Kernel so i don`t get updates for the Kernel 4.13?
Regards Manfred
Der ZFS Verbund läuft bestens.. das ist eine einzelne Festplatte die in keinem Raid Verbund läuft.. und das komische ist ja, dass die Festplatte ja als sda mit den Partitionen sda1 bis sda4 erkannt wird.. nur wird eben die alleine die sda4 Partition eingebunden.. alle anderen sind im omv3.x nicht verfügbar.
Nutze ich die alte omv Version kann ich drauf zugreifen.
evtl. verschiebe ich die Daten von der Festplatte unter der alten omv version auf den ZFS Verbund dann hätte ich zumindest die Daten gerettet. Falls noch jemand eine Lösung hat... wäre ich dankbar.
Hier noch meine alte fstab aus dem omv 2.x
da wurden die Festplatten anders eingelesen..
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=213af96c-ab71-4d95-ba01-65cd7b3c22ee / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=3acadbd1-8aee-48e4-af03-53bcdb7a81fd none swap sw 0 0
/dev/sdc1 /media/usb0 auto rw,user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
UUID=00d32ffe-bdaf-4586-a6c2-47b1e48a0804 /media/00d32ffe-bdaf-4586-a6c2-47b1e48a0804 xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=302c8b83-591c-4025-838d-fe95e391d76d /media/302c8b83-591c-4025-838d-fe95e391d76d xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=2da9444d-b6c9-4cda-9121-13c592103aaa /media/2da9444d-b6c9-4cda-9121-13c592103aaa xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=80210ece-32fe-4249-a9a8-b8e501f522db /media/80210ece-32fe-4249-a9a8-b8e501f522db xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=e4ebd7e8-3043-4a33-9c2a-f3a4c3df2ca4 /media/e4ebd7e8-3043-4a33-9c2a-f3a4c3df2ca4 xfs defaults,nofail,noexec,usrquota,grpquota 0 2
UUID=32de089a-16de-4428-9b04-da78909870b5 /media/32de089a-16de-4428-9b04-da78909870b5 xfs defaults,nofail,noexec,usrquota,grpquota 0 2
/media/00d32ffe-bdaf-4586-a6c2-47b1e48a0804/Filme/ /export/FilmeI none bind 0 0
/media/80210ece-32fe-4249-a9a8-b8e501f522db/Filme/ /export/FilmeII none bind 0 0
/media/e4ebd7e8-3043-4a33-9c2a-f3a4c3df2ca4/Filme/ /export/FilmeIII none bind 0 0
/media/32de089a-16de-4428-9b04-da78909870b5/Erotik /export/Erotik none bind 0 0
/mnt/Movie /export/Movie none bind 0 0
# <<< [openmediavault]
Wie sollte ich da am besten vorgehen?
Leider bekomme ich beim einhängen der sda eine Fehlermeldung von 3 der 4 Partitionen..
sda1 bis sda3 bringen diesen Fehler
Nur sda4 läßt sich einhängen..
Hat hier noch jemand einen Tip für das Problem?
ach ja, hier noch die /etc/fstab aus dem aktuellen omv 3.x in der die Rede ist
/etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=f84e7616-6f51-4d8b-91fc-363941b30797 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a2dd91c9-87bb-4b4b-a762-085daa49b30f none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
/dev/disk/by-label/HD103SI /srv/dev-disk-by-label-HD103SI xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/HD103UJ /srv/dev-disk-by-label-HD103UJ xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/WD30EZRX /srv/dev-disk-by-label-WD30EZRX xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
# <<< [openmediavault]