Upgrade from OMV5 to OMV6 wont work

darkopi · 6. März 2024

I can not upgrade OMV5 to OMV6 on Odroid HC2.

After run omv-release-upgrade I got this:

The repository 'http://apt.armbian.com buster Release' no lo

nger has a Release file.

N: Updating from such a repository can't be done securely, and

is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user c

onfiguration details.

ryecoaaron · 6. März 2024

Read this thread - Seemingly cannot update and upgrade anymore due to repository having no release file (OMV6 on Armbian on Odroid HC1)

This should work with minor changes for the OMV 5 to 6 upgrade. I recommend doing a second upgrade (or install fresh) and going to OMV 7 since Armbian doesn't support Debian 11 bullseye (needed for OMV 6) anymore.

darkopi · 6. März 2024

Can You help me with that?

What I can do?

Fresh install is not good option 🤕

ryecoaaron · 6. März 2024

Zitat von darkopi

Can You help me with that?
What I can do?

Did you read the thread? porg has listed all of the steps very nicely later in the thread.

macom · 6. März 2024

If I understand post #39 correctly, the mirrors are available again. Did you try after the post?

darkopi · 6. März 2024

I did all steps from post #29 and I upgrade OMV5 to OMV6 (armbian to from buster to bullseye) but in one moment when i was trying to confirm changes in OMV6 gui OdroidHC2 was disconnected from network and now I can not access OdroidHC2.

OMV gui and ssh wont work.

EDIT:

Fresh install is on the way

darkopi · 7. März 2024

After fresh install OMV7 I have strange problem.

Hdd wont mount in OMV7 but I see in ssh that hdd is mounted.

Code

~# lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda    8:0    0  1.8T  0 disk
└─sda1
       8:1    0  1.8T  0 part /srv/dev-disk-by-uuid-38fe70be-70
ba-d601-10b8-70be70bad601
mmcblk0
     179:0    0 14.8G  0 disk
└─mmcblk0p1
     179:1    0 14.7G  0 part /var/folder2ram/var/cache/samba
                              /var/folder2ram/var/lib/monit
                              /var/folder2ram/var/lib/rrdcached
                              /var/folder2ram/var/spool
                              /var/folder2ram/var/lib/openmedia
vault/rrd
                              /var/folder2ram/var/tmp
                              /var/folder2ram/var/log

Alles anzeigen

fstab

Code

UUID=83630b40-b297-4624-bf44-feede454fdd0        /    ext4    noatime,nodiratime,defaults,commit=600,errors=remount-ro    0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/38fe70be-70ba-d601-10b8-70be70bad601        /srv/dev-disk-by-uuid-38fe70be-70ba-d601-10b8-70be70bad601    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
# <<< [openmediavault]

darkopi · 23. März 2024

My bed. Hdd was not mounted.

Hdd need to be sdb...

After some time and testings I can confirm that problem is wireguard plugin.

After wireguard plugin installation my hdd become missing.

Only fresh omv installation is fix for that.

I need wireguard and I do not know how to fix this.

chente · 23. März 2024

Zitat von darkopi

After some time and testings I can confirm that problem is wireguard plugin.

How did you come to that conclusion? The Wireguard plugin does nothing with filesystem mounts.

darkopi · 25. März 2024

Five times I have the same problem.

After wireguard plugin is installed my hdd is missing from OMV.

Fresh install without wireguard plugin and all is ok.

I think that is something related to wireguard plugin and armbian

ryecoaaron · 25. März 2024

Zitat von darkopi

After wireguard plugin is installed my hdd is missing from OMV.
Fresh install without wireguard plugin and all is ok.
I think that is something related to wireguard plugin and armbian

Armbian is debian. So, this is unlikely to be the problem. The plugin does try to load the wireguard module in the kernel but definitely nothing with storage like chente said. I would like to see the output from the wireguard plugin installed from the command line. And without logs (like dmesg), no one can tell why a hard drive would go missing.

Jetzt mitmachen!