The open network attached storage solution

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.


  • New

    This is not the OS hard drive, but rather a 2nd HDD.

    It shows up as /dev/sdb1 in the "File Systems" page, but when I go to the "Shared Folders" page and attempt to "+ Add" folders on it as shared folders it doesn't appear in the drop down list next to "Device".

    If I plug in a USB External HDD and mount it, that external HDD does show up in the drop down list.

    I should note that /dev/sdb1 is formatted with an ext4 file system and was formerly used on an OMV 2.x installation.

    I'm trying to upgrade to OMV 3.x and I have hit this stumbling block. Before I resort to making a new logical volume on my OS HDD, copying the contents of /dev/sdb1 onto it, and deleting then recreating the filesystem on /dev/sdb1 via the OMV GUI, I wanted to ask here and see what wisdom I could gather.

    My fear is that after doing all that repartitioning and moving files around and recreating the file system in the OMV admin GUI I'd find it STILL wouldn't work.... ?(
  • New

    After getting some DRDY error messages on my physical testbench:

    Source Code

    1. janv. 18 20:01:00 omv kernel: ata5.00: failed command: SMART
    2. janv. 18 20:01:00 omv kernel: ata5.00: cmd b0/d5:01:e1:4f:c2/00:00:00:00:00/00 tag 30 pio 512 in
    3. res 40/00:01:03:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    4. janv. 18 20:01:00 omv kernel: ata5.00: status: { DRDY }
    i fix them by deseabling the PCI IDE ONBOARD CHIP from my bios motherboard.

    It may help people ...
  • New

    Hello, ( again )...

    On my physical testbench ( accessing from another computer with ssh on local 192.168.x.x and ), i am experiencing multiples times a "broken pipe" error when trying to:
    - accessing drive with smart command from GUI
    - applying saved configuration changes.
    - installing plugins from GUI.

    Most of the time, re-applying what i was doing fix the error message.

    GUI is simply stating communications error, and journalctl -f state message like:
    - omv-engined[12967]: Failed to write to socket: Broken pipe

    I know that broken pipe error is thrown when the socket on the peer side is closed. But i wonder were it come from ??

Unread Threads

Topic Replies Last Reply

Announcement Solutions to common problems



headphones (docker) "cannot find directory"



Deleted /var/cache or How do I reinstall the web-gui?



phpVirtualBox (5.0-5) is incompatible with VirtualBox 5.1.8_Debian



General discussion moved from another thread!!



Recent Activities