omv6: problems with attached USB memory

1st Official Post

    Hello community!

    I'm a newbie to omv as well as my knowledge/skills with linux are low so far.. :)


    Bought a raspiPi4B with 2GB RAM (as the other ones with more RAM are still not available unf. :( ).

    Installed Pi OS lite --> Debian 11 (bullseye).

    Installed openmediavault6. As I not yet work with productive data and hence it is ok when it is still a not stable version. (actual running 6.0.10-1 (Shaitan))



    I have severe problems when attaching a USB memory (USB3.2Gen1 64GB). Procedure goes like this after stick is attached:

    Storage/Disks/Wipe --> ok

    Storage/File Systems/Create (as ext4) + select the device --> ok (writing inode tables etc. --> ok)

    As a direct next step: Storage/File Systems/Mount --> delay of some seconds followed by "Software Failure. Press left mouse button to continue. The server is unavailable to handle this request right now."


    Clicking on screen as the message prompt it --> loading symbol appears for some seconds..

    If(!) coming back to login mask and try to login --> still the same message occurs "Software....."

    When waiting for e.g. 5 minutes or more --> login mask --> coming to Dashboard --> System trying to update the Dashboard which take some seconds until the same message "Software....." shows up again.


    Only to detach the USB stick will help. Then I can login as usual and performance is back on normal.



    My first thoughts/questions:

    1. Is 2GB of RAM to small for OMV6? (tried it once with OMV5 as well --> same results)

    2. As swappiness is per default set to 1, I put it permanently to 70 to see if it helps, as well as using another USB (32GB; USB2.0; and no problems with that) for SWAP to preserve the SDcard. But I see no difference.


    Do you have any hints or ideas why it always crashes as soon as I attach a 'bigger' USB memory?

    Does anyone has an idea why it succeeds to wipe and format the stick but when it comes to mount it, it is failing?

    Maybe it's due to USB version "3.2 Gen1" ?

    Quote from holyowly

    using another USB (32GB; USB2.0; and no problems with that)
    when attaching a USB memory (USB3.2Gen1 64GB), when it comes to mount it, it is failing?

    Did you consider a defective (or even faked) 64GB stick?

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

    Quote from mi-hol

    Did you consider a defective (or even faked) 64GB stick?

    By formatting the 64GB with GParted it showed a plausible available size (something around 57,30GB). So I don't think it is a fake memory size. But I have no idea why 6,7GB are reserved resp. not available.

    All used USB sticks used are new. Assuming they are in new/good condition.

    Thank you for the hint. I will try it with a different USD stick.



    Meanwhile I have different problem. I tried several updates. On Raspberry-Pi-OS-Lite as well as on omv6, but I am not sure as they were sucessfully. In the end omv permanently crashed and even the OS updates in the menu threw errors. So I reinstalled everything, but facing problems I did not have before. Problems as desribed below:


    Installing Raspberry-Pi-OS-Lite following the instructions here:

    https://wiki.omv-extras.org/do…ing_omv6_armbian_bullseye

    with its update and upgrade is working fine.

    Code
    sudo reboot

    most often does not work as it should. Instead kind of shuts down the raspi (green and red LED are off). Then I have to re-attach the USB power supply. Then it works again. So far so good.



    Next step is running the script:

    wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash


    Formerly this ran through without any issue. Now it stops at some point with the message:


    ...

    Code
    setting up Salt environment ...
Setting up system ...
[WARNING ] /usr/lib/python3/dist-packages/salt/utils/files.py:396: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
f_handle = open(*args, **kwargs)  # pylint: disable=resource-leakage


client_loop: send disconnect: Broken pipe
name@name-ThinkCentre-M93p:~$




    I can reconnect to raspberry and trigger the script again:

    wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash



    Then it stope next at:


    ...



    Reconnect again and trigger the script:

    wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash


    ...




    OMV6 is not yet working. If I do 'sudo reboot' then the following will prompted:

    ssh: connect to host 192.168.178.38 port 22: No route to host


    If I re-attach the USB power supply. Still the same:

    ssh: connect to host 192.168.178.38 port 22: No route to host



    Having a look into the folder 'boot' of the micro sd-card, I saw that the empty 'ssh' file was removed and hence the ssh connection no longer worked.

    Adding the empty 'ssh' file again into the 'boot' folder will not help, as it will be removed again immediately.




    Conclusion so far:

    Installing raspi OS is working. Something under installation of omv6 is not working I guess.

    I have no clue what I did different to the previous installations.


    Any ideas?

    Shall I share the whole prompted information of the terminal during installion?

    • Official Post

    Seems the connection from your computer to the RPi is not very stable. Try to run the script in a screen session.


    https://linuxize.com/post/how-to-use-linux-screen/


    That way the script will continue to run even if you loose the connection from your computer.

    Quote from macom

    Seems the connection from your computer to the RPi is not very stable. Try to run the script in a screen session.


    https://linuxize.com/post/how-to-use-linux-screen/


    That way the script will continue to run even if you loose the connection from your computer.

    Thank you for the hint. I tried it, unf. with same result.

    It terminates at the same line. Due to that I would guess it is not an issue due to an unstable connection between raspi and the host.


    Btw. Had this problem few days ago with another computer, where it before worked fine.


    I am baffled..

    Raspberry PI 4 only have 2 USB 3.0 and 2 USB 2.0 ports. I used one USB 3.0 ports for storage (hardware raid enclosure), one USB 3.0 for ethernet connection (bond with build in NIC), one USB 2.0 for monthly auto backup, one USB 2.0 for keyboard. So I install OMV on a microSD card.

    Quote from czgu4422

    Raspberry PI 4 only have 2 USB 3.0 and 2 USB 2.0 ports. I used one USB 3.0 ports for storage (hardware raid enclosure), one USB 3.0 for ethernet connection (bond with build in NIC), one USB 2.0 for monthly auto backup, one USB 2.0 for keyboard. So I install OMV on a microSD card.

    Maybe the USB3.2 is causing the problems. Strange only that wiping the memory and formatting is working (also here communication is needed), but then when it comes to mount the device it gets massive problems and the system crashes.

    Hello community,


    I found the root cause to the 2 problems I had (1. USB-stick problems with crashing of system; 2. problem to reinstall OMV6).

    It is embarrassing to admit it as I read about that issuesbefore and should have known it better, but nevertheless I will inform you about the root cause.


    To make it short: the power supply was to weak!

    By reinstalling I used a different USB power supply as before. Kind of strange that I did not have problems when updating the raspi OS lite, but then when installing OMV - which here and there obviously needs more current/power or installing is done faster or whatever - it crashed/interrupted.


    Also the initial problem with handling of the USB-stick has gone. So I assume everything was related to the power supply.

    Now I am running with quad-SATA-HAT that is powered by a 12V/5A DC jack power supply, and the HAT in turn is powering the raspi. No more problems so far :)


    The symptoms I could see were:

    -> the LEDs were sometimes not blinking that bright as normal, but more flickering only slightly. (lack of power)

    -> crash or reboot occured when this slightly flickering of LEDs were to observe.

    -> the command "sudo reboot" often stopped the system, but LEDs stayed off, resp. the system could not reboot (to less power..!?) and I had to reattach the USB-C manually.


    Thank all of you for the support and hints to solve the problem! :thumbup:

  • macom

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login