Posts by jfromeo

  • [OMV 6.X to 7.X upgrade with errors] Update packages search does not work, plugin list refers to 6.X build

    Quote from ryecoaaron

    Try:


    head /usr/sbin/omv-mkaptidx

    sudo rm /usr/sbin/omv-mkaptidx

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

    Wow, you are the man.


    Plugin list is corrected, and although no updates are shown due to the script having been launched just a moment before, the search progress is quite longer as it was before on 6.X build, so I guess when updates are pendant, they will be shown.


    I leave the log in case someone faces the same issue.


    Thanks again.

  • [OMV 6.X to 7.X upgrade with errors] Update packages search does not work, plugin list refers to 6.X build

    Quote from ryecoaaron

    Searcht the forum for info about the fix6to7upgrade script and run it.

    Thank you.


    Copied the script to ./tmp and executed it via PuTTy


    bash fix6to7upgrade.sh


    Rebooted and cleared web cache, but still plugins list is at 6.X, I will check if the update button works in some days because I see the script launches apt-get update && apt-get upgrade.


    Here it is the log in case it helps. It is a pity I cannot locate the omv-upgrade log to check what failed exactly during the 6.X to 7.X upgrade (I was at the latest 6.X ver):

  • [OMV 6.X to 7.X upgrade with errors] Update packages search does not work, plugin list refers to 6.X build

    I recently pulled the trigger and upgraded all my machines from 6.X to 7.X via omv-upgrade.


    2 of 3 went perfectly through the process but 1 of them, the most important one as it is the machine where 90% all my workload is, finished the upgrade with errors, and I am experimenting some odd behaviours from then on.

    1. Raspberry Pi4B arm64 8GB LPDDR4 --> perfect
    2. Xeon dual core x86-64 16GB DDR4 ECC --> perfect
    3. Xeon octo core x86-64 64GB DDR5 ECC --> completed with errors

    In this last machine I face 2 errors:


    1. If I click on "Check for new updates" nothing happens after the search, but if I SSH and launch:

    apt-get update

    apt-get upgrade


    Packages get correctly updated (docker-ce docker-ce-cli docker-compose-plugin as of today, from bookworm source)


    cat /etc/apt/sources.list

    Code
    deb http://deb.debian.org/debian bookworm main contrib non-free
deb http://deb.debian.org/debian bookworm-updates main contrib non-free
# Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
# deb-src http://deb.debian.org/debian bookworm main contrib non-free
# deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free


    2. If I click on "Check for new plugins" nothing happens, plus the plugin list show 6.X plugins:



    But If I SSH and launch:


    dpkg -l | grep openmediavault


    OMV 7-X plugins are shown.


    I have tried to reboot, clear browser cache and omv-salt stage run deploy, with no luck. This machine seems to live "in the past".


    Is this a common problem after an incorrect upgrade? How to check for "consistency" after the omv-upgrade command?


    Thanks in advance.

  • 4 identical external drives, 2 idle at <30ºC, other 2 idle at >40ºC

    Quote from Soma

    On what hardware are the drives settled? Links please.

    Do they have ventilation or just passive dissipation?


    To rule out temp sensors not giving correct reading, just blow a fan to them and see if values drop on the GUI.

    On this StarTech powered hub:


    4-Port Self-Powered USB-C Hub, 4x BC 1.2 - USB-A Hubs | USB Hubs | StarTech.com Europe
    4-Port Self-Powered USB-C Hub with Individual On/Off Switch, Desktop/Laptop USB-C to USB-A Hub, USB Type C Hub w/Power Supply | Europe
    www.startech.com


    I need the extra power (>1A@5v from each USB port) to run the drives, as the Pi4B could only provide around 1A@5v USB-Ports in total. The drives take around 6.5W max at the boot up process and 4.5W max under working conditions.


    Yeah, the fan reduces around 8-10ºC to all the drives, so sensors are working.

  • 4 identical external drives, 2 idle at <30ºC, other 2 idle at >40ºC

    Quote from mi-hol

    Is the temperature measurement confirmed via an external sensor measurement (Infrared laser thermometer)?

    Anyway you might get better answers in a disc hardware or vendor related forum

    Thank you.


    Only with smart sensors (the ones built in OMV/Debian).


    Although touching by hand I can confirm the two drives sitting at 50ºC when accesed (not burning but somewhat warm), the other ones which sit at 33-35ºC when accesed are almost unnoticeable. I have tried different positions (center/side) and usb ports connected at the hub (0/1/2/3).


    Without the fan they all go up around 8-10ºC.


    It is like 2 of them cannot go into idle.

  • 4 identical external drives, 2 idle at <30ºC, other 2 idle at >40ºC

    Hello all.


    I have 4 external WD 2.5" disks connected via a powered hub to my Raspberry Pi 4B 8GB running OMV 6.9.6-1.












    I have all of them set with the following APM paremeters.













    They are all idling for hours, but 2 of them idle at <30ºC and the other 2 at >40ºC. They are all on a vertical mount, espaced 5cm each other, with a 14cm fan blowing directly to them.


    I see that the model of the 2 colder ones is identical while the 2 hottest ones is different.


    Is there anyway to check what is happening? Why the >10ºC difference on the same conditions among 4 identical drives?


    I suspect the hottest ones are not idling. When accesed (jellyfin media server) they all get 6-8ºC hotter, which is normal, but the hottest ones almost reach 50ºC which I want to avoid. They are all read-only, no random writes are generated (jellyfin docker running on another flashdrive).


    Thanks in advance.

  • OMV does not recognise external USB HDD on fdisk and got dmesg errors (DOA?)

    Hello all.


    I recently purchased 4 HC560 20TB data center hard drives. I have 4 SilverStone TS07 external USB cases 12v powered which have the Asmedia ASM1051E SATA to USB chip, connected to a Raspberry Pi4B running OMV6.


    3 of the HDD gets recognised correctly on OMV while 1 of them do not. Unforntunately I do not have access to a SATA interface for further testing.


    I have tried to swap the external cases and cables from 1 of the working HDD to the 1 of the unrecognised one. I have tried to run the unrecognised HDD as the only drive connected. None of them works.


    The output of dmesg whenever I connect a working drive is as follows:



    The output of dmesg whenever I connect the unrecognised drive is as follows:



    As you see, at half the spinning disk operation, it gest halted and removed. The HDD "sounds" as it is working and gets somewhat warm as the working drives, but it does not show on fdisk or OMV disk GUI. The other 3 HDD works perfectly, they got all ext4 formatted and have them running. I assume the controller is ok but some mechanical component is not.


    Do I have something left to test or should I already RMA it?


    Thanks in advance.

  • [Q] NUT plugin - Communication with Back-UPS and RJ45/USB cable

    Wow, that is a super interesting method.


    Geeky as hell :D


    I keep it for the future.


    Thank you!

  • [Q] NUT plugin - Communication with Back-UPS and RJ45/USB cable

    Hello all.


    I have a Pi4B with OMV6 and the NUT plugin.


    I am thinking of buying the following UPS "APC Back-UPS BE850G2" (https://www.apc.com/es/es/prod…de-recarga-usb-tipoc-y-a/) for protecting the IT equipment (ONT, router, switch), along with the Pi4B and some external HDDs.


    I have checked the UPS has a Data port with a RJ-45/USB type cable, like this one:


    Cable-de-comunicaci-n-APC-UPS-USB-AP9827-Cable-NAS-de-se-alizaci-n-Simple-USB.jpg


    I would like to connect it to the Pi4B in order to set the nut plugin to autoshutdown when UPS goes on battery for more than 5 minutes.


    Is this possible? I have it but on another more advanced UPS (APC Smart-UPS SMT1500i) and I do not know if this interface is also "smart" and it can communicate with the nut plugin to get the sequence done.


    Thanks in advance

  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote from raulfg3

    only need to select portainer in files, use button pull ( to pull latest image), and once done, use button UP ( to restart container with recent downloaded image)


    https://wiki.omv-extras.org/do…v6_plugins:docker_compose

    Thank you.


    But it seems I have to set a "shared folder" first, I got an error in webui once I access the folder section. I will look for some tutorial.

    Quote from chente

    Portainer is just another container, nothing differentiates it from the others. So the procedure is the same as for any other container.

    Thank you.


    But I cannot stop and recreate it by pulling latest image from portainer menu itself (the options are greyed out), which is the way I update all the other containers. I guess it it because if I stop it, the webui will be lost and I could not recreate it from the webui, so it makes sense. Before the change to omv-extras it was pretty straightforward to update it by clicking on install portainer from OMV menu.


    Maybe I could do via cli, and the previous image and options are maintained?:

    Code
    $ docker stop portainer
$ docker rm portainer
$ docker pull portainer/portainer-ce

  • Fastest way to rsync large files between two local machines?

    Quote from chente

    That is. That job should work locally without a doubt.

    However, it is always preferable if it is possible for the job to be executed as a pull rather than a push. Then I would create the share on the PI. I would do a remote mount on the xeon with openmediavault-remotemount. And I would create the job in pull mode from the xeon.

    Thank you so much for all the help.


    I will try it as soon as I hit home.

  • Fastest way to rsync large files between two local machines?

    Hello all.


    I need to rsync a big chunk of large files (around 5TB, mostly 10GB files) between 2 machines connected to my local network. I have done some tests and the maximum speed size I get is 5MBps, which is damn slow.


    The command I run on a remote Putty session over Wireguard on the machine with the source folders is:


    rsync -v -r /source_folder/ root@IP_destination_machine:/destination_folder/


    The speed output was:


    sent 11,020,343,517 bytes received 35 bytes 4,849,436.11 bytes/sec


    Not even 5 MBps. Given the drives and interfaces I was expecting >60 MBps


    I do not know where the bottleneck is here.


    The source machine is a SBC Pi4B 8GB running OMV 6.4.0 and the destination one is a NAS based on Xeon E3-1230v5 32GB running OMV 6.4.0.


    Source HDD is WD Black 5TB connected to USB3.0 port of the Pi4B and destination HDD is WD HC560 20TB connected to SATA3 port of the NAS. Both Pi4B and NAS are connected to the same 10/100/1000GB switch (Linksys WRT-SE4008EJ) on Cat6 cables (<25m).


    What could be the problem? I cannot detach the WD Black from the Pi4B and attach it to the NAS as both are at a remote location far from where I live.


    Thanks in advance.

  • Docker volumes shared with several containers?

    Hello all.


    I have several docker containers (15+) and I would like to ask if it is possible to create common volumes paths to all containers so I do not need to write down the full mount point of the volume in each stack compose.


    For example I would like to create a volume called "docker" which points to "/srv/dev-disk-by-uuid-d3343dca-5136-40ff-b1be-e3eb786c56ce/docker" so in the transmission stack compose instead of:


    volumes

    - /srv/dev-disk-by-uuid-d3343dca-5136-40ff-b1be-e3eb786c56ce/docker/transmission/config:/config

    - /srv/dev-disk-by-uuid-d3343dca-5136-40ff-b1be-e3eb786c56ce/docker/transmission/downloads:/downloads

    - /srv/dev-disk-by-uuid-d3343dca-5136-40ff-b1be-e3eb786c56ce/docker/transmission/watch:/watch


    I could reference them as:


    volumes

    - /transmission/config:/config

    - /transmission/downloads:/downloads

    - /transmission/watch:/watch


    Thanks in advance.

  • [HELP] OMV OS disk got almost full in one day

    I did some


    sudo umount -a /dev/sda1

    sudo umount -a /dev/sdb1

    sudo umount -a /dev/sdc1

    sudo umount -a /dev/sdd1

    sudo umount -a /dev/sde1


    But I realised after some seconds they all got automounted again (I was watching file folders on OMV).


    Is there any way to prevent automounting?

  • [HELP] OMV OS disk got almost full in one day

    Hello all.


    I have a Pi4B running OMV 6.3.12.


    My OS drive (/dev/root) is at 90% while yesterday it was at 25%, and has been at 25% for months.


    I suspect transmission or rsync have failed to reach a mounted drive while in some operation and left the big file or files in /dev/root, but I cannot find the file/s causing the space shrink and I fear I run out of space and cannot access the gui.


    I have followed the guide: how-to-fix-full-os-filesystem-gui-login-loop and pruned logs and unused docker images. In /srv I have no suspicious big file.


    I am not physically at home, so I cannot detach usb drives (I have 4+cache drive), reboot and inspect the OS drive. And I prefer not to unmount all of them as I would have to unreference all the services I have running on each of them (smb, sftp, rsync jobs, shared folders...).


    Is there any command to reboot without mounting any external usb drive? Or to unmount all external drives despite being referenced? I was thinking about installing systemrescuecd and reboot to it once.


    There is an inconsistency between the outputs of df and du


    du -xhd1



    df -h



    Thanks in advance.