I will try with apt install -f
I will try with apt install -f
For a couple of days I notice I have same updates available .
But when try to update it will not install.
Have attached pictures.
Is there a way to fix this?
I hade the same problem.
I removed docker from omv-extras reboot and reinstall in the same directory.
now i m running 5:20.10.16~3-0~debian-bullseye
After changing the power adapter and
adding "denyinterfaces veth*" at the end of /etc/dhcpcd.conf
Having upp and running for 3 days.
My setup Raspberry pi4, OMV6 it have worked very well.
After 22 May everyday between time 15-16 OMV becomes unreachable on the network.
Powering off on then it will work for 24 hours.
I have attached a messages file. I have to delete same lines from 22 May because it was too big.
Please anyone can see what's wrong.
Today a change the power adapter
Thanks for the explanation
I see this when updating OMV.
Is there a way to fix it ? Tanks
Failed to stop ntp.service: Unit ntp.service not loaded. Unit ntp.service does not exist, proceeding anyway. Created symlink /etc/systemd/system/ntp.service → /dev/null. Failed to stop systemd-timesyncd.service: Unit systemd-timesyncd.service not loaded. Unit systemd-timesyncd.service does not exist, proceeding anyway. Created symlink /etc/systemd/system/systemd-timesyncd.service → /dev/null.
I have a similar task, but I was not able to set up a VM network with docker and host
Will take a look
Just notice when updating from 6.0.21 to 6.0.22 several errors
Is it a problem?
OMV6 seem to work well.
Here are the logs
Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: openmediavault 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 2410 kB of archives. After this operation, 2048 B of additional disk space will be used. Get:1 http://packages.openmediavault.org/public shaitan/main armhf openmediavault all 6.0.22-1 [2410 kB] apt-listchanges: Reading changelogs... Preconfiguring packages ... Fetched 2410 kB in 0s (7958 kB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 107938 files and directories currently installed.) Preparing to unpack .../openmediavault_6.0.22-1_all.deb ... Unpacking openmediavault (6.0.22-1) over (6.0.21-1) ... Setting up openmediavault (6.0.22-1) ... Creating configuration database ... Migrating configuration database ... Setting up Salt environment ... [ERROR ] Command '/usr/bin/patch' failed with return code: 1 [ERROR ] stdout: patching file /tmp/__salt.tmp.0_s2exwk (read from /lib/python3/dist-packages/salt/modules/network.py) Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.dy8f55kh [ERROR ] retcode: 1 [ERROR ] Command '/usr/bin/patch' failed with return code: 1 [ERROR ] stdout: patching file /tmp/__salt.tmp.cm5ukis9 (read from /lib/python3/dist-packages/salt/fileserver/roots.py) Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.eqm9pn52 [ERROR ] retcode: 1 Processing system modifications ... Processing triggers for rsyslog (8.2102.0-2) ... Processing triggers for openmediavault (6.0.22-1) ... Restarting engine daemon ... Updating workbench configuration files ... END OF LINE
It's one of the three options in the drop down "Method" list when you configure IPv4 and/or IPv6 for any interface.I
I don't have three option in the drop down Method. Will test with another browser.
The How2 does not cover the case of a bridge on a bond. The IP must move from the bond to the bridge, but in this case you do not delete the bond interface. On the bond interface select disable for the "method" and then save, but do not apply. Then create your bridge selecting the bond as the interface and the IP method and details you want. Save, and now apply the configuration changes.
how do you do "On the bond interface select disable for the "method" "?
Sorry I find thanks
Can you please clear your browser cache and then check whether the file system is still displayed twice?
Is the duplicate file system the root file system? I'm asking, not that follow the wrong direction.
I had reset the browser but it did not help.
Here is after I perform the above .
Please report which plugins you are using and which OMV version you are running.
I assume you are using the sharedrootfs plugin. The mentioned issue should be fixed in openmediavault 6.0.13.
Hi I m using 6.0.21-1 (Shaitan)
Yes I m using sharedroofts plugin.
I solved it.
Uninstalled sharedrootfs plugin, one problem ,
I m using KVM plugin and it gets automatically uninstalled.
After some rebooting and add OMV-Extra settings and add testing repo it was possible to install
I found this in the fstab section of config.xml. It seemed to me to be out of place so I removed it and ran omv-salt deploy run fstab. This cleared the problem. No idea how or even when that content came into config.xml.
Hi, did you have duplicate entries?
The file location is /etc/openmediavault/config.xml ?