One-drive install - how to?

    • OMV 4.x

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

    • One-drive install - how to?

      New

      Hello,

      I have a small OMV setup on a machine that has a single drive. Please note that I cannot use the OMV ISO so I made a Debian 9 minimal and installed OMV.

      Source Code

      1. Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
      2. Units: sectors of 1 * 512 = 512 bytes
      3. Sector size (logical/physical): 512 bytes / 512 bytes
      4. I/O size (minimum/optimal): 512 bytes / 512 bytes
      5. Disklabel type: dos
      6. Disk identifier: 0x88e3bbf9
      Because I've read that partitions should be created exclusively via OMV's WebUI, I've created only these partitions:

      Source Code

      1. Device Boot Start End Sectors Size Id Type
      2. /dev/sda1 * 4096 40962047 40957952 19.5G 83 Linux
      3. /dev/sda2 40962048 42008575 1046528 511M 82 Linux swap / Solaris
      Next, what should I do? If I create a partition via fdisk it will not be "usable" in OMV. So ... what's next?

      Thank you!
    • New

      Razva wrote:

      Because I've read that partitions should be created exclusively via OMV's WebUI
      That is the case if OS drive and data drive are separated.

      Mounting must be done from WebGUI of OMV, only. Otherwise OMV is not aware of the filesystem.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • New

      macom wrote:

      Create a partition and filesystem outside of OMV (e.g. from CLI). Then you should be able to mount the filesystem in OMV.
      OK, so I'm safe to fdisk a new partition, but create a mount point exclusively via WebUI?

      Also, does OMV 32bit (arm) have any partition size limit?

      The post was edited 1 time, last by Razva ().

    • New

      macom wrote:

      Razva wrote:

      Because I've read that partitions should be created exclusively via OMV's WebUI
      That is the case if OS drive and data drive are separated.
      Mounting must be done from WebGUI of OMV, only. Otherwise OMV is not aware of the filesystem.
      I've tried everything I could think at. So here it goes.

      Here's FSTAB

      Source Code

      1. # <file system> <mount point> <type> <options> <dump> <pass>
      2. /dev/sda2 / ext4 errors=remount-ro,relatime 0 1
      3. /dev/sda3 /shared ext4 defaults,relatime 1 2
      4. /dev/sda4 swap swap defaults 0 0
      5. tmpfs /tmp tmpfs defaults 0 0

      Now.

      1. If I comment SDA3, the partition will obviously not be mounted. In this case I cannot even find it on the WebUI.
      2. If I don't commend SDA3, the partition will be mounted but it'll have Referenced = No and not be usable as a share (or anywhere else).
      3. If I don't commend SDA3 and unmount it via CLI, then mount it via WebUI, I either got an error OR it works until the first reboot. Here's the error:

      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/disk/by-id/ata-HGST_HUS726040ALA610_K7JHDMWL-part3' 2>&1' with exit code '32': mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.
      So at this point I've tried every possible combination and I'm really out of ideas.


      Any hints?