Do you try to mount from a Linux client and OMV is 192.168.1.99?
i am trying to connect an ovm raid disk on a linux pc, yes ovm is 192.168.1.99
Thank's
Do you try to mount from a Linux client and OMV is 192.168.1.99?
i am trying to connect an ovm raid disk on a linux pc, yes ovm is 192.168.1.99
Thank's
I don't have a web gui, why can't I edit fstab ?
I can mount the disk from the terminal by running this command
sudo mount -t cifs -o username = tim, password = wsxtgb //192.168.1.99/Movies / home / tim / Movies
but if i try to put this line in /etc/fstab at boot it doesn't connect the disk on strtup
//192.168.1.99/Movies /home/tim/Movies cifs auto,_netdev,username=tim,password=wsxtgb,uid=tim,gid=tim 0 0
what am I doing wrong ?
Thanks for the help
Hi,
it is possible to install transmission without container, I use the OMV5 X86 version.
thank's
Problem solved, the cause was the configuration of the network interface. Rerun the configuration of the network interface via omv-firstaid everything works correctly. Thanks everyone for the help.
root@Jarvis:~# cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
# No DNS servers known.
root@Jarvis:~# ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Jan 20 11:25 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
root@Jarvis:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-resolved.service.d
└─resolvconf.conf
Active: active (running) since Thu 2022-01-20 14:46:05 CET; 4 days ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wi…rk-configuration-managers
https://www.freedesktop.org/wi…/writing-resolver-clients
Main PID: 446 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 2339)
Memory: 2.1M
CGroup: /system.slice/systemd-resolved.service
└─446 /lib/systemd/systemd-resolved
I removed the usb backup plugin and tried to reinstall openmediavault but it gives error on Host name lookup failure, how can i fix it?
root@Jarvis:~# apt-get install --reinstall openmediavault
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1729 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 58444 files and directories currently installed.)
Preparing to unpack .../openmediavault_5.6.24-1_all.deb ...
Unpacking openmediavault (5.6.24-1) over (5.6.24-1) ...
Setting up openmediavault (5.6.24-1) ...
Creating configuration database ...
Migrating configuration database ...
Setting up Salt environment ...
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
[ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure
Processing system modifications ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for openmediavault (5.6.24-1) ...
Restarting engine daemon ...
Monit: the monit HTTP interface is not enabled, please add the 'set httpd' statement and use the 'allow' option to allow monit to connect
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
root@Jarvis:~#
Alles anzeigenGhibli69 I asked you about ssh access on the weekend, but you did not see my message, in time
This week I am away from my omv, so I can not help to repair the config.xml (got no reference with me)
For anyone who wants to try:
- The update broke, but we were able to get most of the packages updated.
- 1 package (I thing openmediavault-usbbackup) is still at 4 -> needs to be removed apt-get remove -f openmediavault-usbbackup, but check the package before (dpkg -l |grep openm)
- The config.xml only got partially updated, so one has to fix the errors in the file manually or run the migrations one by one (they are here: ls -1 /usr/share/openmediavault/confdb/migrations.d | sort) omv-salt stage run deploy will show them
- OP is not sure where he started the upgrade but claims to have startet a 5.x when all this started. config.xml has ( had ?) entries which should have been migrated by 5.0.0
For a complete re-install just apt-get purge openmediavault-plugins and openmediavault. maybe apt-get install --reinstall openmediavault will work too.
But be carefull that this does not reconfigure the network / sshd so you hook it off the network (server is remote). Allways kep a second ssh window open.
All above written by memory, so take it with a grain of salt.
this is the output
root@Jarvis:~# dpkg -l |grep openm
ii openmediavault 5.6.24-1 all openmediavault - The open network attached storage solution
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ic openmediavault-usbbackup 4.0.5-1 all OpenMediaVault USB/eSATA backup plugin
but i can't uninstall usbbackup plugin
root@Jarvis:~# apt-get remove -f openmediavault-usbbackup
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'openmediavault-usbbackup' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
how can i uninstall it?
if i can't restore xml config file, can i reinstall OMV from SSH?
to reach the server in ssh I can give you a teamviewer connection on my pc, send me a message in private and I give you access
If you remove (instead of purge) openmediavault-usbbackup, it won't remove the config.xml entries but it will stop causing other problems.
I think this would be much easier to fix with ssh access instead of forum back-and-forth. I would just change the config.xml things manually.
There is no way to determine what version the config.xml is from since it is not versioned. You might be able to tell by some elements.
This is the config.xml file, can this be useful?
I tried to start from 4.0.6 but always error
This
Codeoot@Jarvis:/# dpkg -l | grep openm ii openmediavault 5.6.24-1 all openmediavault - The open network attached storage solution ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ic openmediavault-usbbackup 4.0.5-1 all OpenMediaVault USB/eSATA backup plugin
tells me, you have been trying a release update or your system got corrupted long ago.
You can try to start with 4.0.6 and 4.0.17, then 5.0.0
I think so
This
Codeoot@Jarvis:/# dpkg -l | grep openm ii openmediavault 5.6.24-1 all openmediavault - The open network attached storage solution ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ic openmediavault-usbbackup 4.0.5-1 all OpenMediaVault USB/eSATA backup plugin
tells me, you have been trying a release update or your system got corrupted long ago.
You can try to start with 4.0.6 and 4.0.17, then 5.0.0
root@Jarvis:/# dpkg -l | grep openm
ii openmediavault 5.6.24-1 all openmediavault - The open network attached storage solution
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ic openmediavault-usbbackup 4.0.5-1 all OpenMediaVault USB/eSATA backup plugin
root@Jarvis:/#
always error
I haven't performed release upgrade, but can I start from conf_4.0.6 ?
root@Jarvis:/# cat /etc/openmediavault/config.xml | awk '/<interfaces>/,/<\/interfaces>/'
<interfaces>
<!--
<interface>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<type>ethernet|bond|vlan|wireless|...</type>
<devicename>xxx</devicename>
<method>dhcp|static|manual</method>
<address>xxx.xxx.xxx.xxx</address>
<netmask>xxx.xxx.xxx.xxx</netmask>
<gateway>xxx.xxx.xxx.xxx</gateway>
<method6>auto|dhcp|static|manual</method6>
<address6>xxxx:xxxx:...:xxxx</address6>
<netmask6>0-128</netmask6>
<gateway6>xxxx:xxxx:...:xxxx</gateway6>
<dnsnameservers></dnsnameservers>
<dnssearch></dnssearch>
<mtu>0...n</mtu>
<wol>0|1</wol>
<options></options>
<comment>xxx</comment>
# Optional arguments by type:
# - ethernet
# - bond
<slaves>((eth|wlan)\d+,)*(eth|wlan)\d+</slaves>
<bondprimary>(eth|wlan)\d+</bondprimary>
<bondmode>0|1|2|3|4|5|6</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
# - vlan
<vlanid>1-4095</vlanid>
<vlanrawdevice>(eth|wlan|bond)\d+</vlanrawdevice>
# - wireless
<wpassid>xxx</wpassid>
<wpapsk>xxx</wpapsk>
</interface>
-->
<interface>
<uuid>67a4672e-81ca-4acd-8941-d5b266f351ad</uuid>
<type>ethernet</type>
<devicename>enp6s0</devicename>
<method>static</method>
<address>192.168.39.182</address>
<netmask>255.255.255.0</netmask>
<gateway>192.168.39.1</gateway>
<method6>manual</method6>
<address6></address6>
<netmask6>64</netmask6>
<gateway6></gateway6>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnssearch></dnssearch>
<mtu>0</mtu>
<wol>1</wol>
<comment></comment>
<slaves></slaves>
<bondprimary></bondprimary>
<bondmode>1</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
<vlanid>1</vlanid>
<vlanrawdevice></vlanrawdevice>
<wpassid></wpassid>
<wpapsk></wpapsk>
</interface>
<interface>
<uuid>b37fe9de-8dec-4f8f-ad43-a243ab0fe405</uuid>
<type>ethernet</type>
<devicename>enp6s0</devicename>
<method>static</method>
<address>192.168.39.182</address>
<netmask>255.255.255.0</netmask>
<gateway></gateway>
<method6>manual</method6>
<address6></address6>
<netmask6>64</netmask6>
<gateway6></gateway6>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnssearch></dnssearch>
<mtu>0</mtu>
<wol>0</wol>
<comment></comment>
<slaves></slaves>
<bondprimary></bondprimary>
<bondmode>1</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
<vlanid>1</vlanid>
<vlanrawdevice></vlanrawdevice>
<wpassid></wpassid>
<wpapsk></wpapsk>
</interface>
<interface>
<uuid>1c207fdc-a6b7-441f-8d22-ae05f1b24528</uuid>
<type>ethernet</type>
<devicename>enp6s0</devicename>
<method>static</method>
<address>192.168.39.182</address>
<netmask>255.255.255.0</netmask>
<gateway></gateway>
<method6>manual</method6>
<address6></address6>
<netmask6>64</netmask6>
<gateway6></gateway6>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnssearch></dnssearch>
<mtu>0</mtu>
<wol>0</wol>
<comment></comment>
<slaves></slaves>
<bondprimary></bondprimary>
<bondmode>1</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
<vlanid>1</vlanid>
<vlanrawdevice></vlanrawdevice>
<wpassid></wpassid>
<wpapsk></wpapsk>
</interface>
<interface>
<uuid>3ebae1a4-62fc-4083-b39e-12a858d18dd0</uuid>
<type>ethernet</type>
<devicename>enp6s0</devicename>
<method>static</method>
<address>192.168.39.182</address>
<netmask>255.255.255.0</netmask>
<gateway></gateway>
<method6>manual</method6>
<address6></address6>
<netmask6>64</netmask6>
<gateway6></gateway6>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnssearch></dnssearch>
<mtu>0</mtu>
<wol>0</wol>
<comment></comment>
<slaves></slaves>
<bondprimary></bondprimary>
<bondmode>1</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
<vlanid>1</vlanid>
<vlanrawdevice></vlanrawdevice>
<wpassid></wpassid>
<wpapsk></wpapsk>
</interface>
<interface>
<uuid>49b39081-6ce3-4be3-aa84-11dd4a1cedef</uuid>
<type>ethernet</type>
<devicename>enp6s0</devicename>
<method>static</method>
<address>192.168.39.182</address>
<netmask>255.255.255.0</netmask>
<gateway></gateway>
<method6>manual</method6>
<address6></address6>
<netmask6>64</netmask6>
<gateway6></gateway6>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnssearch></dnssearch>
<mtu>0</mtu>
<wol>0</wol>
<comment></comment>
<slaves></slaves>
<bondprimary></bondprimary>
<bondmode>1</bondmode>
<bondmiimon>0</bondmiimon>
<bonddowndelay>0</bonddowndelay>
<bondupdelay>0</bondupdelay>
<vlanid>1</vlanid>
<vlanrawdevice></vlanrawdevice>
<wpassid></wpassid>
<wpapsk></wpapsk>
</interface>
</interfaces>
root@Jarvis:/#
root@Jarvis:/# cat /etc/openmediavault/config.xml | awk '/<dnsnameservers>/,/<\/dnsnameservers>/'
<dnsnameservers></dnsnameservers>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnsnameservers>8.8.8.8</dnsnameservers>
<dnsnameservers>8.8.8.8</dnsnameservers>
root@Jarvis:/#
root@Jarvis:/# ping http://www.google.com
ping: http://www.google.com: Temporary failure in name resolution
root@Jarvis:/#
Zoki can i try from conf_4.0.6?