New Install - Cannot see "volumes"

  • Hi,


    i just installed OMV on a new 3TB (only 1 disk for OMV and for Data). This is the "Filesystem" snapshot:



    /dev/mapper/bubba ext3 Mounted Yes
    /dev/sda1 ext3 Mounted yes


    When i try to create a new shares, there is no way to select a volume.


    I check in the config.xml and <mntent> does not contain any reference to my device.


    I tried to unmount it but i get an error:


    Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/d6c252e9-4f37-449e-96cf-b607dc1571a7'])



    I also tried to run omv-mkconf fstab but no luck.



    Any hint?


    Thank you and kind regards,


    Fabio

    • Offizieller Beitrag

    You will have to repartition. You can't use the OS partition for data.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    You never posted your partition structure. So, I couldn't say. If data is on /dev/sda2, then mount it in the filesystems tab and you should be able to create a shared folder and use it throughout the OMV web interface.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yes, i confirm data is on sda2 and it is visible on the filesystem tab....but there is no way to select when creating a new share.


    Anyway, i will quit. I am trying to run OMV in a headless device (with no serial port) and i had to re-install it so many times due to hangs during boot process (as i was playing with the interface).


    I will retry when i will get a new device.


    Thanks for your assistance....maybe tomorrow i will change opinion and try again :)


    Fabio

    • Offizieller Beitrag

    It is visible on the filesystem tab but did you mount it using the mount button on that tab? You can't mount it manually or by fstab. Once you do that, you should be able to create a new share.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Find here the snapshot of the filesystems:



    and this is the dump of fdisk -l (i cut out sdb1)


    Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
    255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00000000


    Device Boot Start End Blocks Id System
    /dev/sda1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.


    Disk /dev/mapper/bubba-storage: 2988.8 GB, 2988777144320 bytes
    255 heads, 63 sectors/track, 363364 cylinders, total 5837455360 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00000000


    Disk /dev/mapper/bubba-storage doesn't contain a valid partition table


    And this shows that no volume is available:


    • Offizieller Beitrag

    Did you mount the drive using the web interface? If not, you have to for OMV. What is the output of: omv-showkey mntent

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • According to his screenshot, he hasn't mounted it yet.


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • Good morning (and thanks for your support),


    i cannot find the command names omv-showkey. Anyway, in the config.xml, under the entries <mntent> there are only xxx..xxx, no reference to a concrete device. So, as you say, probably OMV has not mounted it.


    As you can see from the above picture, the Web Interface shows the device as "Mounted". I tried click "unmount" but i get the following error:


    Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/45d3b493-b741-45a6-a6b6-9e26d150e814'])


    (as, I guess, the device is not listed in config.xml).

  • And this is the fstab entry:



    /dev/sda1 / ext3 noatime,defaults 0 1
    /dev/mapper/bubba-storage /home ext3 defaults 0 2
    /dev/sda3 none swap sw 0 0
    none /proc/bus/usb usbfs defaults 0 0
    tmpfs /tmp tmpfs defaults 0 0

  • Solved!


    in the terminal I first unmounted the disk (umont /dev/mapper/xxx)


    Back to the guy I remounted it


    and then, in the terminal, omv-mkconf fstab


    Let me do some tests to see if it as all ok :)

    • Offizieller Beitrag

    Did you mount the drive using the web interface? If not, you have to for OMV.


    I think I posted that...

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yes, I mounted via GUI.


    Regardig unmounting, the GUI did not allow to unmount it (i guess, as there was no entry in <mntent> the GUI doesn't know how to unmount).


    I unmounted via CLI and then remounted via GUI, this finally allowed for the creation of the <mntent> in config.xml.


    I then run omv-mkconf fstab to create the entry in fstab.



    Anyway, to summarize, for some strange reason, upon installing (with LVM) no mntent is created in config.xml.


    Hope this helps.


    Next challenge: resize the LVM with the plugin...something is not working there....

    • Offizieller Beitrag

    When you do a fresh install, OMV does not automatically add existing data drives (lvm or raid or partitions). You have to manually mount/add them which will then create the mntent entries.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • thanks, the thing is that, after a fresh install, the GUI was showing it as "MOUNTED" see my picture above.


    And it cannot be unmounted via the GUI itself as no entry exists in config.xml


    It must be unmounted via CLI and then mounted via GUI, at least in my case...this allows for the creation of the right mntent entry in config.xml

    • Offizieller Beitrag

    Must be an LVM thing then because partitions and raid arrays don't automount. Might be worth a bug report.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!