Issue creating file system in OpenMediaVault

  • Hi,


    I'm relatively new to NAS operating systems, so please forgive me if this is a beginner's question. I'm currently working on a small tinkering project using an Acer Aspire E5-576 laptop from 2017 with the following specs:


    Intel Core i3-8130U


    6GB DDR4 2400MHz RAM


    500GB WDC WDS500G2B0A-00SM50 SSD


    The first time I installed OpenMediaVault (OMV), I was able to set up an EXT4 file system and successfully mounted it. I then created shared folders (data, compose, and backup) and used them with Docker containers — everything worked as expected.


    However, I wasn’t fully satisfied with the way I initially configured everything, so I decided to reinstall OMV from scratch.


    Now, after the reinstallation, I'm trying to recreate the file system and mount it, but the WDC WDS500G2B0A-00SM50 SSD no longer appears in the dropdown menu when I attempt to select a device to mount. It’s like OMV doesn’t see it anymore.


    Did I miss a step during the setup? Could it be that the disk is already in use, or maybe it wasn't properly wiped during the reinstall? Any tips or guidance would be greatly appreciated!


    Thanks in advance!


    I see the disk under storage and disks, see the following picture:


    And when I go to Storage ⇾ File systems, click on the + select EXT4 I can't select the disk, see the following picture:


    Also, I can't mount the file system.



    What do I have to do?

    this is the output of fstab

    # /etc/fstab: static file system information.

    #

    # Use 'blkid' to print the universally unique identifier for a

    # device; this may be used with UUID= as a more robust way to name devices

    # that works even if disks are added and removed. See fstab(5).

    #

    # systemd generates mount units based on this file, see systemd.mount(5).

    # Please run 'systemctl daemon-reload' after making changes here.

    #

    # <file system> <mount point> <type> <options> <dump> <pass>

    # / was on /dev/sda1 during installation

    UUID=8a8d7f4c-ead1-4ae3-8e1d-cf808718730e / ext4 errors=remount-ro 0 1

    # swap was on /dev/sda5 during installation

    UUID=7381fa8d-20f4-4548-813f-59b8a0e93738 none swap sw 0 0

    /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0


    and also the output of config.xml


    <mntent>

    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>

    <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>

    <dir>/xxx/yyy/zzz</dir>

    <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>

    <opts></opts>

    <freq>0</freq>

    <passno>0|1|2</passno>

    <hidden>0|1</hidden>

    <usagewarnthreshold>xxx</usagewarnthreshold>

    <comment>xxx</comment>

    </mntent>


    Can someone help me?

  • You only have one hard drive and OMV is installed on it. By default OMV does not allow the creation of filesystems on the system drive or to create shares there either.


    If you want share access to the system drive, install the openmediavault-sharerootfs plugin.


    You would probably be better off installing OMV to a smaller drive like a 16 or 32GB SSD or USB stick and using the 500GB drive for data.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


    • Official Post

    is it also possible to partion the disk beforehand with gparted?

    To install OMV on a partition on that hard drive, you can install Debian by creating the necessary partitions and then installing OMV. However, it's better to follow the advice you were given and use a separate drive for the operating system.

Participate now!

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