Posts by mbourd25

Hi ryecoaaron

Quote

Nope. That is from Debian 10/OMV 5.

It has been removed and ran commands omv-salt deploy run apt and omv-aptclean repos to reconfigure and update the repositories.

Quote

Is it causing a problem? Do you have a wifi adapter in the system? What is the output of: dpkg -l | grep -E "wireless-regdb|crda"

I ran this command and no information is listed.

Hi ryecoaaron , I just upgraded my server to OMV 7 and everything went very smooth except a couple of situations. I uninstalled the old beta Snapraid version, like you told me and reinstalled and the old array disappeared.

But now, I get these error messages.

1. I get this message for repositories:

http://packages.azlux.fr/debian/dists/buster/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Do I need this repository?

2. I keep getting this error, twice, when I boot up:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

How can I fix this. I looked at the Debian wiki at https://wiki.debian.org/Firmware, and the explanation seem to think you know which firmware you are missing. Is there a way to find out which firmware I'm missing?

Thanks in advance.

Thanks again for your help ryecoaaron , I thought both scripts were the same.

All plugins are now showing has being from version 7.

Hi, I upgrade OMV from version 6 to 7 but all the plugins are still at version 6.

I tried multiple ways to fix this. I even followed these instructions from this thread, RE: OMV migrated to V7 but plugins are still in V6. But it is still displaying plugins for version 6.

I also reran the fix6to7upgrade script, sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash. It is still showing version 6 plugins.

Here is the output from the web page for plugins in my OMV 7

Here's the output from command dpkg -l | grep openme

Here's the output from command dpkg -l | grep openme

Any help would be great. Let me know if more information is required.

Hi, just to let everyone know I ran the fix6to7upgrade script from web site https://github.com/OpenMediaVa…-Developers/installScript and ran the wget script command directly on the Raspberry Pi, sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash and everything is fixed now.

Thanks to everyone who created this script.

Hi, I got the same "502 Bad Gateway" error after upgrading to OMV7 on my Raspberry Pi when trying to login using the web page. But I'm also unable to log in using SSH. It will not accept the password.

What option do I have to fix this?

Thanks in advance.

Awesome. Thanks again. I'll keep you informed on how to upgrade went.

From the list of plugins that I sent you, should I remove any other plugin before proceeding with the upgrade to OMV 7?

I should follow these steps to do the upgrade?

1. Backup the OS drive (this is always a good idea, not only for upgrades)
2. Make sure, you have enough free space on your OS drive
3. If you installed software from foreign repos make sure they have a release for bullseye or remove the repos / software
4. Go to the cli (Putty, ssh, keyboard) and run these commands (In case of errors stop and ask on the forum before making things worse)
   1. Make sure your current install is correct all configs can be deployed by running sudo omv-salt stage run deploy
   2. Get the current install up to date: sudo omv-upgrade
   3. Do the release upgrade by running sudo omv-release-upgrade
      If you see an error message from patch which says a patch has already been applied, ignore it. (this is the only error to be ignored)
5. Wait for the last script to finish and reboot.
6. Refresh/clear browser cache (Crtl-Shift R on most browsers)
7. Check if all services and docker containers are running as you expect.
8. If you see Linux image Updates you can not install on the UI, go to the cli and run omv-upgrade once more.

Thanks again for your help ryecoaaron. It is truly appreciated.

Hi ryecoaaron, That's my next goal, to upgrade to OMV 7.x. But had to replace my data drives since they started to give me SMART errors. WD Red hard drives are over 8 years old.

Replaced them with brand new WD Red Pro.

Here's the output from command dpkg -l | grep openme

rc  omvextras-unionbackend             5.0.2        all   union filesystems backend plugin for openmediavault
ii  openmediavault                     6.9.16-1     all   openmediavault - The open network attached storage solution
ii  openmediavault-backup              6.1.1        all   backup plugin for OpenMediaVault.
ii  openmediavault-clamav              6.0.7-2      all   openmediavault ClamAV plugin
ii  openmediavault-fail2ban            6.0.3        all   OpenMediaVault Fail2ban plugin
ii  openmediavault-flashmemory         6.2          all   folder2ram plugin for openmediavault
ii  openmediavault-kernel              6.4.10       all   kernel package
ii  openmediavault-keyring             1.0.2-2      all   GnuPG archive keys of the openmediavault archive
ii  openmediavault-mergerfs            6.3.8        all   mergerfs plugin for openmediavault.
ii  openmediavault-nut                 6.0.7-1      all   openmediavault Network UPS Tools (NUT) plugin
ii  openmediavault-omvextrasorg        6.3.6        all   OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-resetperms          6.0.3        all   Reset Permissions
ii  openmediavault-rsnapshot           6.0.2        all   OpenMediaVault rsnapshot backup plugin.
ii  openmediavault-sharerootfs         6.0.3-1      all   openmediavault share root filesystem plugin
ii  openmediavault-snapraid            6.2.1        all   snapraid plugin for OpenMediaVault.

Hi gang, I created a new Snapraid array with new disks that I added to my OMV 6.0 installation to replace my older hard drives which they were setup with Mergerfs and Snapraid. I removed the Mergerfs setup and removed the Snapraid for my first array and OMV still uses my first Snapraid setup. Now I tried to delete my first array but I keep getting this error message,

Quote

Failed to execute XPath query '//services/snapraid/drives/drive[uuid='114a88d2-53ed-11ed-8eee-b3f2573b9c38']'.

OMV\Config\DatabaseException: Failed to execute XPath query '//services/snapraid/drives/drive[uuid='114a88d2-53ed-11ed-8eee-b3f2573b9c38']'. in /usr/share/php/openmediavault/config/database.inc:88

Stack trace:

#0 /usr/share/openmediavault/engined/rpc/snapraid.inc(172): OMV\Config\Database->get('conf.service.sn...', '114a88d2-53ed-1...')

#1 [internal function]: OMVRpcServiceSnapRaid->deleteArray(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('deleteArray', Array, Array)

#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('SnapRaid', 'deleteArray', Array, Array, 1)

#5 {main}

Display More

Is there a way I can delete my first array and have Snapraid point to the second array?

Here is my Snapraid.conf file content.

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

autosave 0
#####################################################################
# OMV-Name: DISK01  Drive Label: DISK01
content /srv/dev-disk-by-uuid-c0732fc4-6d0f-4898-a7d6-1cfc96625f59/snapraid.content
disk DISK01 /srv/dev-disk-by-uuid-c0732fc4-6d0f-4898-a7d6-1cfc96625f59
#####################################################################
# OMV-Name: DISK02  Drive Label: DISK02
content /srv/dev-disk-by-uuid-10994e9d-cb49-41c8-8f7d-da2815f0b096/snapraid.content
disk DISK02 /srv/dev-disk-by-uuid-10994e9d-cb49-41c8-8f7d-da2815f0b096
#####################################################################
# OMV-Name: PARITY1  Drive Label: PARITY1
parity /srv/dev-disk-by-uuid-27a7ad0c-8f34-4df0-8acf-6da1544221ef/snapraid.parity


exclude *.unrecoverable
exclude lost+found/
exclude aquota.user
exclude aquota.group
exclude /tmp/
exclude .content
exclude *.bak
exclude /snapraid.conf*

Any help would be great. Let me know if more information is required.

Thanks in advance.

Found the problem. The Portainer from omv-extras was enabled. That's not from me, since I install Portainer using docker-compose.

Thanks macom for your help.

There is only Portainer using port 9000. Very strange.

I wonder if it's conflicting with itself.

Hi macom, there are no other services running on port 9000. That is very strange.

Is there a way I can find out if there is another service running on port 9000?

Thanks.

Hi macom, I attached the error in a text file.

Thanks for your help.

error-message.txt

Hi gang, I am still getting this error since I also had the Testing Repo check mark on. Mine was on to be able to use the latest Snapraid.

I attached the screenshot of the error.

Any help would be appreciated. Thanks.

Hi mortee, I get the same error from the same package.

Hi chente, separating both the Movies and TV shows folder is just a personal preference.

I used to just have one folder before.

Thanks ryecoaaron for your help. When I'll reboot my server, I'll check to see if I see the message.

I updated the grub file, /etc/default/grub, to have command selinux=0 in line, GRUB_CMDLINE_LINUX_DEFAULT="quiet selinux=0".

ryecoaaron, I was just curious as to why it just suddenly showed up since I haven't installed anything on my OMV server in a very long time and the only thing I do to it are updates.

The other day, it was the first time I rebooted my system in over 4 months. That's when I noticed that error message.

Looking at /etc/default/grub, this is my GRUB_CMDLINE_LINUX_DEFAULT="quiet".

ryecoaaron, ran the command sudo grep -v '#' /etc/selinux/semanage.conf, this is the output.

module-store = direct

expand-check=0