Beiträge von QWERTY1965

Zitat von ryecoaaron

OMV 5 should really be /usr merged (not necessarily have usrmerge installed). There are only a few packages on OMV 5 (nut is one) that need usrmerge. And Volker has said he does not want to automatically install usrmerge on upgrades.

in OMV 6 (fresh install) /usr/bin/mount exists (check it out for yourself).

OMV5 don't have it and I don't have never installed usrmerge.

Now /usr/bin/mount it is missing in my system after migration.

root@OMV6new:~# cat /etc/monit/conf.d/openmediavault-filesystem.conf | grep mount
# Try to auto-mount a filesystem if it is missing. Alert if the filesystem
check program mountpoint_srv_dev-disk-by-uuid-652f2774-bceb-43af-af08-a5d53f3a72af with path "/bin/mountpoint '/srv/dev-disk-by-uuid-652f2774-bceb-43af-af08-a5d53f3a72af'"
then exec "/usr/bin/mount '/srv/dev-disk-by-uuid-652f2774-bceb-43af-af08-a5d53f3a72af'"

root@OMV6new:~# ls -al /usr/bin/mount
-rwsr-xr-x 1 root root 55528 28 lug 20.09 /usr/bin/mount

root@OMV6new:~# dpkg -S /usr/bin/mount
dpkg-query: nessun percorso corrispondente a /usr/bin/mount

Hello,

I have bad news only.

I performed these steps:

- restored OMV5 system from clonezilla backup

- uninstalled all OVM plugins from the web interface

- run apt update && apt -y upgrade

- run omv-release-upgrade

omv-release-upgrade went into error, again, in the same way as 1 week ago and with the same 2 errors (see photo).

1st error it's caused by missing folder /lib/python3/ in the system.

Workarounds applied to the tray to complete the update are:

scp -r root@192.168.1.142: /lib/python3/.  /lib # 192.168.1.142 is a fresh VMWare installation of OMV6

apt-get install --reinstall openmediavault

for the 2nd error steps are:

nano /etc/monit/conf.d/openmediavault-filesystem.conf

and replacing "/usr/bin/mount" with "/bin/mount"

After reboot the system with OMV6 is on, but the plugin list are always the 5.x

Now I have 2 ways:

1) continue to help developers community, if they need my tests ( VOTDEV in first )

2) give up and perform a new fresh OMV6 install

Zitat von gderf

Did you uninstall all OMV 5 plugins that do not have a released OMV 6 version of the plugin before performing the upgrade?

No I did not. It's a mistake, but I didn't (and I don't think I'll be the only one).

I think there must be a solution, specially now that I removed all plugin.

I have re-done installation just now, as you request, but nothing is changed.

P.S.

I'm beginner on the forum, but I am not linux noobie. I've been using OMV for years (since OVM 0.4).

I haven't ovm extras installed now and nothing changes also I install it.

root@nas:~# cat /etc/apt/sources.list.d/omvextras.list

cat: /etc/apt/sources.list.d/omvextras.list: File o directory not exists

dpkg -C return nothing

root@nas:~# dpkg -C

root@nas:~#

root@nas:~# dpkg -l | grep openmediavault

ii openmediavault 6.0.4-3 all openmediavault - The open network attached storage solution

ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

Hi all,

after running omv-release-upgrade from 5.6.20 to OMV 6.x (RC1), I solved varius issues and the system is on.

Now I have a problem to solve: the plugin are still on 5.x.

I manually removed all .deb plugins and purged.

I also have removed and purged openmediavault-omvextrasorg but nothing is changed (see attached img).

At least I tried to reinstall (apt reinstall openmediavault), but nothing.

What I can do now?

PS

1) I also have a OS full backup done before the upgrade (clonezilla) so I can re-run the omv-release-upgrade.

2) I can describe to volker (or others) issues I already solved (#1 not existing salt modules Error that interrupted migration and #2 wrong path of mount in /etc/monit/conf.d)