OMV: failed to start quotaon@srv-dev error. Why? How to fix?

    I'm running OMV 8 on a Proxmox 9 VM. It's running with root/os drive, 1x 2.5" SSD (sda) - primary NAS storage, and 1x USB external 2TB SSD (sdb) for rsync daily backups. QEMU is enabled.

    During boot, I hit quotaon failed on my sda drive. It's not like it affects my OMV NAS by any means, I suppose, but it is bothering me due to the slower boot time.


    Can someone explain where this came from and how to solve it?


    I found a way to fix it by installing OMV-Extras - https://github.com/OpenMediaVa…Script?tab=readme-ov-file, but I really don't need to be doing this because it adds some cache things and other bloat, which is some extra complexity and overkill for my simple NAS needs.

    Another approach would be to directly edit the /etc/fstab mounting point and remove both quota directives to the sda mounting point, but the chat does not recommend this approach.


    CDN media

  • macom

    Approved the thread.

    Installing OMV-Extras really doesn't add any complexity or overkill to your system - it just provides Docker functionality (completely optional and must be explicitly enabled before it's available) and a host of plugins you can install one by one as needed.


    One of these plugins is the mount editor, which allows you to remove the quota options from your /etc/fstab entries. It sounds like you're saying that you already went that route...?


    If you really wanted to do it the manual way, editing /etc/fstab directly wouldn't do it because OMV would just overwrite it at some point. You'd have to edit /etc/openmediavault/config.xml instead and look for an entry that looks like this:

    There's one block like this for each storage device known to OMV. You can tell that the <opts>defaults,nofail,user_xattr,acl</opts> is the one to edit. After that, you'd have to either run an omv-salt command - I'm not sure exactly how - or just reboot the server for the change to become active.


    I do not recommend this approach unless you're absolutely comfortable editing what could be called OMV's "registry" (like the Windows registry). If you inadvertently change something else by accident, the whole system can crash and burn.

    @cubemin, thanks for your detailed response. Afterall, I'll go the 'clean way' and just install the omv-extras.

    Yes, I did go this way once, and then I restored the VM. I didn't like that it asked me to apply changes when I logged back to the OMV GUI (that yellow box), and that it added that cache functionality, I think it was 'openmediavault-flashmemory' without asking. But I suppose this is part of the installation script.


    Thanks once again. Would appreciate it if you could share your thoughts about that additional cache option that is being added automatically.

    That flashmemory plugin is meant for OMV systems that run off a USB stick or SD card, or similar flash-based storage (other than SSD drives) that doesn't have wear leveling. The plugin helps to prevent premature failure of such storage.

    You can simply uninstall that plugin with no adverse effects if you wish; your SSD should be fine without it. Or you can configure it to your needs.

Participate now!

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

Register Yourself Login