Posts by Soma

Quote from Rien Timmer

have installed OMV and connected two ntfs disk. Created smb shares for both of them.

Only way to Access is with a root USER.

You can not have a M$ file system working proper on Linux.

Formar them with a Linux FS to use it properly

sudo omv-changebackports NO

sudo omv-upgrade

ls -al /srv/dev-disk-by-uuid-92401814-b838-4ee6-b2e8-98b7bc281a29/appdata2/

See if the notifications were flushed.
If it still sends out the old message, try to disable the filesystem notification event and re-enable them again to trigger a cleanup:

What is the output of:

sudo systemctl status monit.service

sudo omv-salt deploy run monit

Quote from Jeole

Happy New Year folks!

I have added the outputs of the command to a pastebin file as it exceeds 10000 characters

https://pastebin.com/fqs2SkDU

Err:10 https://deb.debian.org/debian stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY 78DBA3BC47EF2265 NO_PUBKEY 762F67A0B2C39DE4

You have a wrong REPO (stable is Trixie and you are on bookworm)

sudo grep -r stable /etc/apt/*

Quote from chente

Are you sure your system is 64-bit? You have 32-bit repositories configured.

This is a known issue, even on pure 64bit OS:
sudo apt update doesn't support architecture 'armhf - General - openmediavault

kurac338

If you are sure you have a 64bit PiOS, then look on the above thread and follow post #17:
RE: sudo apt update doesn't support architecture 'armhf

Quote from toppi

Issue resolved itself and I was able to upgrade container.io

Yep, the package is now available on the REPOS:

beytarj

The package is available on the REPOS:

You can try now the sudo omv-upgrade

As you already saw, the package is missing from the REPOS (for whatever reason):

It is probably some SYNC issue on the REPOS and better to wait a while longer till it fixes itself and try later.

On a side note, you already have the compose plugin installed, according to:

Quote from beytarj

root@test7:~# dpkg -l | grep openm

ii openmediavault 7.7.24-6 all openmediavault - The open network attached storage solution

ii openmediavault-compose 7.6.13 all OpenMediaVault compose plugin

ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive

ii openmediavault-omvextrasorg 7.0.6 all OMV-Extras.org Package Repositories for OpenMediaVault

ii openmediavault-sharerootfs 7.0-1 all openmediavault share root filesystem plugin

ii openmediavault-wetty 7.0.1-1 all openmediavault WeTTY (Web + TTY) plugin

Display More

Quote from toppi

Someone any ideas? Or is it a temporary problem with packet source?

Same issue ongoing here:
Cannot install openmediavault-compose plugin - Failed to fetch - Plugins - openmediavault

It seems that packages are missing from the repos.

Probably some SYNC issue, ATM

First, learn how to post outputs inside CODE boxes, please.
[How-To] Post content in a code box - Guides - openmediavault

After, output of

dpkg -l | grep openm

sudo apt-cache policy containerd.io

You are searching for it on the Debian repos, which it is not where the package is.

Have you installed the omv-extras plugin PRIOR to attempt to install the compose plugin?

What is the output of:
sudo omv-apt clean repos

sudo omv-upgrade

Quote from RUsum1

I get

I don't see the output for

sudo docker start portainer

You can just Skip all this by running the single like (ChatGPT is your friend)

sudo docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

Quote from RUsum1

Then I tried with Run instead of Up and got

My bad, it's sudo docker start portainer

Don't know if it will use the newly pulled portainer-ce image.

What is the output of sudo docker inspect portainer?

Quote from RUsum1

it looks like Portainer was grabbed with your secondary command but it's not running.

It pulled.

You need to start it now.

sudo docker up portainer

Quote from RUsum1

I tried doing these commands and got the following

You need to remove the old container.

Try without guarantee:
sudo docker stop portainer

sudo docker rm portainer

sudo docker pull portainer (if it fails here, sudo docker pull portainer/portainer-ce:latest instead)

See if it shows as running:
sudo docker ps -a

Access the GUI with http://IP_OF_OMV:9443 (IIRC, the GUI is accessed via that port for a long time. NOT 9000)

Last case, ask ChatGPT for instructions.
Good Luck

OR

as chente told, move to the compose plugin and be done with portainer.

Quote from Darky-0

I am experiencing the same problem. I followed all the steps. But I cannot mount the disk. I received this error message:


[FSTAB snippet]

PARTUUID=138ce466-02 / ext4 noatime,nodiratime,defaults 0 1

# >>> [openmediavault]
/dev/disk/by-uuid/87cdb103-2e4b-4d2f-8f40-3434aeb7f8f7 /srv/dev-disk-by-uuid-87cdb103-2e4b-4d2f-8f40-3434aeb7f8f7 btrfs defaults,nofail,ssd 0 2
+/dev/disk/by-uuid/5d54fcce-ea4c-49f5-b6d2-0801cd92bf9d /srv/dev-disk-by-uuid-5d54fcce-ea4c-49f5-b6d2-0801cd92bf9d btrfs defaults,nofail 0 2
# <<< [openmediavault]

[/FSTAB snippet]

[ERROR snippet]

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': raspberrypi:

-----------------

[ERROR ] Command 'mount' failed with return code: 32
[ERROR ] stderr: mount: /srv/dev-disk-by-uuid-5d54fcce-ea4c-49f5-b6d2-0801cd92bf9d: can't read superblock on /dev/sdb.
dmesg(1) may have more information after failed mount system call.
[ERROR ] retcode: 32
[ERROR ] mount: /srv/dev-disk-by-uuid-5d54fcce-ea4c-49f5-b6d2-0801cd92bf9d: can't read superblock on /dev/sdb.
dmesg(1) may have more information after failed mount system call.

[/ERROR snippet]

Display More

What shows here, since the lack of details, is that you are running a Pi with a SSD attached and you tried to connect another HDD.

The error tells you that it can NOT read the superblock on /dev/sdb and that dmesg can provide more info.

sudo lsblk
sudo dmesg | grep err

The most common issue is under voltage.

How are the drives powered? I will speculate that they don't have their own power source and are powered by the USB.

Check it with: sudo vcgencmd get_throttled OR sudo dmesg | grep -i voltage

Nothing much you can do other than have a proper powered external drive.

Some readings:
How to Fix Raspberry Pi "Undervoltage Detected" Warnings

Check If Raspberry Pi is Undervolted Or Throttled

Quote from ulrich.w

OMV7 was mounting the NTFS with option "ro" (latest version a few days ago). Maybe the OS doesn't trust the NTFS Linux driver.

Only time I've seen that happened were on FAT32 USB sticks and SDcards gone bad.
Might happen with SSDs if they reach their write limit.
And this meant they're toast.

Never seen or heard with HDDs.

Quote from ulrich.w

OMV7 mounts NTFS as read-only by default

And where did you read that?

OMV doesn't mount NTFS read-only.

Linux mounts M$ drives with full root ownership meaning you can only write using that USER.

Anyother will only have read-only.