No dropdown on file system

  • I just installed omv6 and was mounting my old file systems, mount an existing file system selected my hdds with data, and after clicking apply it through an error 500 (Your kernel probably supports ext4 quota feature but you are using external quota files. Please switch your filesystem to use ext4 quota feature as external quota files on ext4 are deprecated) and now no devices show in the dropdown on mount or create a filesystem. If I go to disks all the hdds show.

    The only hdds that appear mounted in file systems are the OS drive and a btrfs drive that I have and was the first I tried to mount, all others were ext4.

    I tried clearing the browser cache and tried another browser, but nothing happens when I press the Select a filesystem dropdown on mount filesystem or in Device in the create and mount option.



    This is the output of fstab and theres some things with quota there, but I dont know if I can just remove them from fstab or theres some other way to do it, I dont think I enabled it or if it came by default when I formated the disks on my old omv4.


    It would be great if I didnt have to wipe the disks as I dont have anywhere to move the data to.

  • I tried removing aquota from one disk, the one with less data in it, from fstab and removed all aquota files inside, but it still isnt appearing in the GUI.

    It appears as mounted and I can access it in /srv/dev/disk-by-uuid really long string/ , but I cant get it to appear in the GUI.

  • If I try mounting the filsesystem I get that its already mounted, but still doesnt appear on the GUI or on the dropdown.

    Code
     mount -t ext4 /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74/
    mount: /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74: /dev/sdf1 already mounted on /srv/dev-disk-by-uuid-beb32fc3-68a4-49da-8c84-54b62e9fab74.
    • Offizieller Beitrag

    If I try mounting the filsesystem I get that its already mounted, but still doesnt appear on the GUI or on the dropdown.

    That is by design. On unmounted filesystems show up in the dropdown. The filesystems tab will only show filesystems mounted by OMV. The disk you are trying to mount is already in /etc/fstab added by OMV. So, that would be why you don't see it in the dropdown. sudo mount -a should be all you need. Have you rebooted?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • Ive rebooted several times since, if they were mounted they should appear with the rest of the filesystems right? But they appear only in disks, but no in filesystems.

    Tried running mount -a -t ext4 , but nothing.

    • Offizieller Beitrag

    Ive rebooted several times since, if they were mounted they should appear with the rest of the filesystems right? But they appear only in disks, but no in filesystems.

    Tried running mount -a -t ext4 , but nothing.

    They should. Did you try ctrl-shift-R?

    You don't need to specify a filesystem type in mount -a. I would reboot one more time and post the output of:

    grep ext4 /proc/mounts

    sudo blkid

    sudo omv-showkey mntent

    sudo omv-salt deploy run fstab

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • Tried ctrl-shift-r, also tried clearing cache and another browser, and no luck.



    Code
    sudo blkid
    
    /dev/sda1: LABEL="2T" UUID="107023e1-5a23-4dc5-a810-0f73fe6c778a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="912281a0-24dd-4f6b-b590-f1ced6a1d772"
    /dev/sdb1: LABEL="HDD2" UUID="c4ea1ab6-6342-42ff-977f-cb7d3c834d4d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6ef735e2-1635-4251-ad42-ef03abe34bd0"
    /dev/sdd1: UUID="753e933d-d692-4250-9e16-89d7bd48f577" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="82fa39d1-01"
    /dev/sdd5: UUID="2a4d268a-2c87-4a29-86f2-6ac30b621a99" TYPE="swap" PARTUUID="82fa39d1-05"
    /dev/sdc1: LABEL="HDD" UUID="beb32fc3-68a4-49da-8c84-54b62e9fab74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="83ca8f0a-bd75-48ba-b4f3-521c871fb989"
    /dev/sdf1: LABEL="Bck" UUID="b280838f-d6e0-4eb6-b13f-af3a5a5e1d8b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2817f573-be0e-4be6-a7a2-c00b6ebfcdf2"
    /dev/sdg1: LABEL="HDD3" UUID="aa3e040c-9f14-4c66-b232-997bab362f74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="510dde00-b291-4b8a-93e7-54aff5087785"
    /dev/sdh1: UUID="0235a908-2725-4c2a-8a95-11de7b7ad68d" UUID_SUB="376c545b-f422-471d-b016-4c13a18445f6" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="922e4f78-c2d6-48c6-af92-720d3dcc8431"




    Thats the output off all the commands, will trying other stuff I did remove aquote from fstab so thats why it doesnt appear on these outputs.


    After that all but 1 disk could be mounted, that one throws the same error 500.


    Another fstab, it added aquota back to all the disks, though now only 1 is giving the rror, all others appear as mounted and in the list.

    • Offizieller Beitrag

    You added a bunch of mounts to /etc/fstab manually. Remove those. Unmount the filesystems. Then mount in the web interface. You can't cheat and just add mounts between the openmediavault tags in /etc/fstab. They need mntent entries in the database. You only get those mounting in the web interface.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • I didnt add them manually, I could add 6 of the 7 hdd through the GUI, the last throughs the aquota error. The ones that worked I just has to go to mount and existing filesystem in the GUI and add them.


    Maybe it seems I added them manually because they came from an old omv4 install and Im trying to mount them with the existing data and filesystem?

    • Offizieller Beitrag

    I can't explain what is happening then. When you add a filesystem, it has to add a mntent entry to the database and you only have one.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • This is the mntent now


    I believe it has more entries now, after doing omv-salt deploy run fstab I think it allowed me to mount most of the disks through the GUI.

    Now theres only 1 that I cant add, its also the hdd thats most full (I believe its completely full).

    • Offizieller Beitrag

    his is the mntent now

    sudo omv-showkey mntent shows the mntent entries

    Now theres only 1 that I cant add, its also the hdd thats most full (I believe its completely full).

    Not sure why a full disk would cause that but I haven't tried. Is the disk that you can't mount the same one with the quota errors from your first post? Can you mount it from the command line?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • Sorry about that grabbed the wrong code, this should be the mntent.


    Read here What is this crazy error? I'm stuck , that someone was running omv-salt deploy run quota and was throwing an error because the disk was full, but it seemed to had to do with that it couldnt write the quota because of lack of space, the command just seemed similar.

    • Offizieller Beitrag

    I guess I could see it failing if every byte was full on the drive. Maybe mount /dev/sdc1 temporarily and free up a little space. Unmount and try again from web interface.


    If all else fails, you could manually add the mntent to the database

    sudo omv-salt deploy run fstab after adding it.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!

  • That did it!!!! I added this entry to the file /etc/openmediavault/config.xml

    run sudo omv-salt deploy run fstab , and now it appears in the filesystems. Rebooted and its still there.

    It had nothing to do with the disk being full most likely as I deleted like 500mb and what I did with the other disks didnt work.


    Thanks a ton ryecoaaron.

    • Offizieller Beitrag

    It had nothing to do with the disk being full

    It still might have. I removed the quota options from the mount to avoid that issue. But glad it is working.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4 | scripts 7.0.1


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


    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!