Posts by Ghazzawi

thank you dear ,, it was just a weekend project , was curious on how much i can push the Pi 4 , i want to install other OS beside OMV now and see what happens

thank you for all the support you extend to the community

Followup ...

I am happy to let you know that I managed to get the OMV running in a VM in PiMox also attached 5 external disks , 4TB each , configured mergerfs and everything is working fine ...

• i installed Debian image debian-12-nocloud-arm64.qcow2 on the machine configured below

• i installed OMV from this guide (remember to install wget and openssh-server) before you start with the guide

Installation on Debian — openmediavault 6.x.y documentation

• I installed OMV-extras

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | sudo bash 

• Added mergerfs plugin and customised OMV and enabled services like cifs etc etc
• I added disk to the VM

ls -l /dev/disk/by-id 

• then one by one add the disks using this IDs with the command

  qm set <VM_ID>
 -virtio1 /dev/disk/by-id/<disk-ID>

• Created a giant mergerfs pool
• Created a shared folder on the root of the mergerfs pool ç I could not write to this folder from windows machine but I created folders inside the main folder and reading and writing was fine
• I copy from windows machine large files like 3GB to the cifs share and it starts at speed of 40-45 MBps

• Note : the NIC on this setup is a USB 2.5Gbps NIC connected to the Pi 4 through a USB hub and on the same hub I connect USB cable to the enclosure hosting 5 disks each are 4TB

Here is the final VM

and here is OMV7

Quote from Soma

OMV doesn't run proper on lxc.

Why complicated?

complicated because the disks I have are in a DAS device connected to the Pi over USB ,, and its giving me all kinds of trouble mapping the disks once by one inside the LXC , but anyways i don’t find the LXC idea worth the effort ,,, i will proceed with ryecoaaron suggestion ,,,

thank you both for your usual support

Hi All ,

I Installed PiMox ( Proxmox VE for Raspberry Pi) on my RPi4 and it working fine .. I managed to install OMV as a LXC but its difficult to attach external disks to it

i Need help installing OMV as a VM instead of LXC ,, i tried many VM config variations but it wont boot from the OMV iso nor the debin iso

anyone successful doing that ?

Quote from Barney

Update to this issue: A very recent update removed the need to apply Chente's workaround (as described in post #9 in this thread.)

When this came up last spring, I apply Chente's workaround to one RPI NAS but left another one alone (no workaround.) I would do the dongle dance on this system as needed. My plan was to see if a subsequent update either fixed or reversed the change that led to this issue with USB-ethernet dongles. However I was not always disciplined to reboot after each update (especially when I wind up performing multiple updates in a short period.) Therefore I cannot identify the exact update where the issue behavior changed, but only know it was likely within the last 4-6 weeks.

Knowing the exact update is all academic anyway. I am simply reporting that I observed the boot behavior changed and we may no longer need the workaround.

confirmed by me too ,,, no longer need the workaround on fresh installation of 7.7.7-1

Quote from jata1

Yep. I don't use node-red so can't help too much. This is what I would do.

1. remove the user info from the compose file so that nodered is using the standard 1000:1000 user/group

2. ssh to console and chown the data folder (sudo chown -R 1000:1000 path/to/your/node-red/data)

3. start container

post any error after doing this and I will see if I can help further.

if you are a windows person, I suggest you install winSCP on your PC as it's quite helpful for checking/updating permissions etc.

Display More

This worked for me ,,, thank you

Quote from Ghazzawi

try from the console

Code

omv-firstaid

Quote from Arelius

I try to “configure network interface” it exits and give error (see attached)..

you need to be logged in as root , or try sudo before you run the command

Quote from Arelius

Got a HDMI adapter and thought I could gain access to the Pi5 and reconfigure the network and what not, but no, it’s reboots like 2 times when system fails to lunch OMV and then idles like this (see attached).

Everything passes beside the starting up of “systemd-networkd-wait-online-service” this is the only service that has failed status.

Is there any chance there is something to be done at this point?

try from the console

omv-firstaid

Quote from Arelius

Interesting read, I did add a NIC to my Pi5 just the other day and I was worried cause of this and then I was not NIC is visible in OMV.

the NIC visibility is not the biggest issue in our case

the real thing do you still see the USB NIC after reboots ? or do you have to unplug and re-plug the USB NIC ? ( which Barney calls "dongle dance"))

Quote from ryecoaaron

I just ordered the Asus version. I will get it tomorrow and can try to figure out how to fix this.

I would still be interested to see your view once your ASUS NC arrives tomorrow ")

Quote from chente

That scheduled task should reboot the USB NIC a minute after starting the server, that should avoid the manual disconnect and reconnect dance.

ok after testing i could not get the PI 5 to unbind the device because it could not see it ,, although i am connected to the ssh through that USB NIC and it shows in the command below ...

long story short i targeted the whole port 4 ( in my case usb4) and it worked , now in the GUI scheduler i have the command below .. and i managed to reboot multiple times with no problem ( decreased the sleep time to 10 seconds )

sleep 10;  echo 'usb4' | tee /sys/bus/usb/drivers/usb/unbind; echo 'usb4' | tee /sys/bus/usb/drivers/usb/bind

root@OMV7:~# lsusb
Bus 004 Device 004: ID 0b05:1976 ASUSTek Computer, Inc. USB 10/100/1G/2.5G LAN
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@OMV7:~#
root@OMV7:~#
root@OMV7:~# lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
root@OMV7:~#
root@OMV7:~#
root@OMV7:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP    MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
                                             2500baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol
        Link detected: yes
root@OMV7:~#

Quote from ryecoaaron

I just ordered the Asus version. I will get it tomorrow and can try to figure out how to fix this.

thank you for stepping in too ,, cant wait to hear from you

thank you for your help

i tried the commands in the GUI schedule tasks with no luck so i thought i would run them in the terminal and see the output ..

root@OMV7:~# sudo lsusb -t

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
root@OMV7:~# sleep 60; echo '4-1' | tee /sys/bus/usb/drivers/usb/unbind; echo '4-1' | tee /sys/bus/usb/drivers/usb/bind
4-1
tee: /sys/bus/usb/drivers/usb/unbind: No such device
4-1
tee: /sys/bus/usb/drivers/usb/bind: No such device
root@OMV7:~#

ok after few tests ,, and verifying the procedure in https://forums.raspberrypi.com/viewtopic.php?t=362358

i had to also bind the ip to the mac address of the 2.5Gbe NIC in the router ,,,

now i don't have to run omv-firstaid every time ,, but certainly unplug and re-plug the NIC after each reboot

Hi Barney ,

so tried the dongle dance and it seems to work for me ,,, the challenge is that after every reboot o have to log in to the console and run omv-firstaid

finally i tested with two dongles ( UGREEN and ASUS ) and both have the same problem in OMV while both run smoothly in raspberry OS ( GUI)

I agree with you , i also saw few reports about intermittent behaviour of those USB NICs ..

but the interesting part is that the NIC works perfectly in raspberry OS ( GUI) even after reboots

Hi ,

I got OMV 7 running on raspberry pi 5 with , USB 2.5g NIC .. but i had to run omv-firstaid from the console to configure the USB NIC

after i reboot it seems that the system losses all the USB NIC configuration and no matter how many times i configure it from the console the behaviour is the same

can you let me know what might be the problem ?

I tried casaos on RPI 4 and i must say that he GUI is impressive , and the way you can download containers is also very graphical in a nice way

that said , they had a challenge presenting something to fuse multiple usb disks into a large drive ( something like mergerfs) , i don't know if they solved this issue now

same issue and clearing the browser cache did not help

Dear ,

I ping normally but i think this image is corrupt , i will delete it and recreate it again and let you know how it goes

thank you for your interest