quotaon.service always marked as failed
Hi guys,
I’ve got a lingering issue with the quotaon.service being in a failed state.
I’ve tried to run service quotaon restart but it gave me this error
Job for quotaon.service failed because the control process exited with error code.
See «systemctl status quotaon.service» and «journalctl -xe» for details.
Running systemctl status quotaon.service gives me
● quotaon.service — Enable File System Quotas
Loaded: loaded (/lib/systemd/system/quotaon.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-05-28 23:55:01 EDT; 33s ago
Docs: man:quotaon(8)
Process: 6149 ExecStart=/sbin/quotaon -aug (code=exited, status=4)
Main PID: 6149 (code=exited, status=4)
CPU: 58ms
May 28 23:55:01 Odin systemd[1]: Starting Enable File System Quotas.
May 28 23:55:01 Odin quotaon[6149]: quotaon: cannot find /srv/dev-disk-by-id-ata-Samsung_SSD_850_PRO_512GB_S250NXAGB52683Y-part1/aquota.group on /dev/sdb1 [/srv/dev-disk-by-id-ata-Sams
ung_SSD_850_PRO_512GB_S250NXAGB52683Y-part1]
May 28 23:55:01 Odin quotaon[6149]: quotaon: cannot find /srv/dev-disk-by-id-ata-Samsung_SSD_850_PRO_512GB_S250NXAGB52683Y-part1/aquota.user on /dev/sdb1 [/srv/dev-disk-by-id-ata-Samsu
ng_SSD_850_PRO_512GB_S250NXAGB52683Y-part1]
May 28 23:55:01 Odin quotaon[6149]: quotaon: cannot find /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEJXNSRZ-part1/aquota.group on /dev/sdc1 [/srv/dev-disk-by-id-ata-WDC_WD100EFAX-6
8LHPN0_JEJXNSRZ-part1]
May 28 23:55:01 Odin quotaon[6149]: quotaon: cannot find /srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEJXNSRZ-part1/aquota.user on /dev/sdc1 [/srv/dev-disk-by-id-ata-WDC_WD100EFAX-68
LHPN0_JEJXNSRZ-part1]
May 28 23:55:01 Odin systemd[1]: quotaon.service: Main process exited, code=exited, status=4/NOPERMISSION
May 28 23:55:01 Odin systemd[1]: Failed to start Enable File System Quotas.
May 28 23:55:01 Odin systemd[1]: quotaon.service: Unit entered failed state.
May 28 23:55:01 Odin systemd[1]: quotaon.service: Failed with result ‘exit-code’.
Also, found this thread which seemed to be a similar issue. And followed this suggestion error «Failed start file system quotas» at boot
But when I tried to create a quota for a user on one of the logical drives I got this error in the web gui.
Error #0:
OMV\ExecException: Failed to execute command ‘export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-mkconf quota 2>&1’ with exit code ‘1’: quotacheck: Scanning /dev/sdd1 [/srv/dev-disk-by-id-ata-WDC_WD100EFAX-68LHPN0_JEK5R14N-part1]
quotacheck: Checked 13967 directories and 127932 files
done
setquota: Trying to set quota limits out of range supported by quota format on /dev/sdd1.
setquota: Cannot write quota for 1000 on /dev/sdd1: Numerical result out of range in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/openmediavault/engined/module/quota.inc(37): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(168): OMVModuleQuota->applyConfig()
#2 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod(‘applyChanges’, Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\(‘/tmp/bgstatus38. ‘, ‘/tmp/bgoutputNs. ‘)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg(‘applyChanges’, Array, Array)
#8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod(‘applyChangesBg’, Array, Array)
#11 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call(‘Config’, ‘applyChangesBg’, Array, Array, 1)
#12
[FAILED] Failed to start Enable File System Quotas
After I have installed a new hard disk, the system shows me the following message during the boot process:
«[FAILED] Failed to start Enable File System Quotas».
The NAS still seems to work normally.
It is an external hard disk from Intenso with 2GB. I have shared a folder and set up a Samba share. My NAS based on a raspberry pi 4 two additional hard disks are connected.
What can I do? Do I have to do anything?
Many greetings and thank you very much,
File system quotas are disabled by default, so unless you enabled them and are getting this.. it’l shouldn’t be an issue.. just telling you it did not start.
This is an old, old post.. but it more or less explains this and why it was disabled by default
Air Conditioners are a lot like PC’s. They work great until you open Windows.
Edited once, last by KM0201 ( Sep 19th 2020 ).
Okay, thanks a lot for the fast answer.
I did not enabled it by my self. Is there an option to disable file system quotas? This message appeared only after I connected the third hard-drive. With on lytwo drives the message did not appear. Is there a reason for that behavior?
Okay, thanks a lot for the fast answer.
I did not enabled it by my self. Is there an option to disable file system quotas? This message appeared only after I connected the third hard-drive. With on lytwo drives the message did not appear. Is there a reason for that behavior?
It’s disabled by default (years ago, it was not). All that message is telling you is that it failed to load due to quotas being disabled.
Air Conditioners are a lot like PC’s. They work great until you open Windows.
error «Failed start file system quotas» at boot
Hi guys,
I have OMV installed on a micro SD, since a while I have this error during boot. Is it normal? how can I solve it if it’s not?
Intel G4400 — Asrock H170M Pro4S — 8GB ram — Be Quiet Pure Power 11 400 CM — Nanoxia Deep Silence 4 — 6TB Seagate Ironwolf — RAIDZ1 3x10TB WD — OMV 5 — Proxmox Kernel
It isn’t an error that you need to worry about. If you really want the message to go away, enable quotes (I wouldn’t though).
omv 6.4.9-1 Shaitan | 64 bit | 6.2 proxmox kernel
plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.9.7 | cputemp 6.1.3 | mergerfs 6.3.7
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!
The nas is working fine, so I’m not worryed. But I don’t know what system quotas are
Intel G4400 — Asrock H170M Pro4S — 8GB ram — Be Quiet Pure Power 11 400 CM — Nanoxia Deep Silence 4 — 6TB Seagate Ironwolf — RAIDZ1 3x10TB WD — OMV 5 — Proxmox Kernel
You use system quotas to restrict how much storage a user can use.
omv 6.4.9-1 Shaitan | 64 bit | 6.2 proxmox kernel
plugins :: omvextrasorg 6.3.1 | kvm 6.2.14 | compose 6.9.7 | cputemp 6.1.3 | mergerfs 6.3.7
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!
I also happened to see this error in my log today.
However, today I had pressed the button «Quotas» in the tab filesystems for the first time. Did this make quotaon.service active for the first time, or did I probably have the error before?
I do get an error from time to time as well regarding «Failed to start Enable File System Quotas».
Problem is that the boot will not continue as it stops in emergency mode.
I need to manually hit Control + D to continue which is quite annoying.
Any ideas on how to avoid it? I applied 1 quota for a backup folder.
Maybe there’s a way to completely disable the system, but I didn’t find it at the time.
You may be missing two files at the top level of the filesystem: aquota.group and aquota.user. If that’s the case, you can simply define and save some quotas in the OMV interface under filesystem/quotas and delete them afterwards. The files are then recreated, no quotas are defined and the error should be gone
Failed to start File System Quotas
Hi,
i just installed a fresh OMV (downloaded the latestest Build form the Website) and created a Raid 5 Array (5x3TB).
After copying some files i made a reboot and my OMV isn`t booting correct
i got an Error which says «Failed to start File System Quotas» and i`m completley lost
I am a newbie for OMV and don`t know what to do or how to solve this problem.
I tried to install OMV again — booted via usb and just copied the files.
Then i have acess to the WebGui but after a restart i have the same problem again.
Sorry for my bad English — i hope you understand where my problem is and maybe can provide some informations to solve this.
(it seems there was a user with the same problem but he was not willing to share his solution
new RAID — failed to start enable file system quotas )
i got an Error which says «Failed to start File System Quotas» and i`m completley lost
I didn´t understand, where your problem is? Did you define some quotas and they are not working or what? Or are you just worried about that message? Are there any other error messages?
I remember that in my OMV system I get the same boot message, but I have never defined quotas, so it doesn´t bother me and — more important — I have no problem at all.
And if you are still afraid, then read this:
https://forum.openmediavault.o…le-system-quotas-at-boot/
ASRock Rack C2550D4I C0-stepping — 16GB ECC — 6x WD RED 3TB (ZFS 2×3 Striped RaidZ1) — Fractal Design Node 304 —
3x WD80EMAZ Snapraid / MergerFS-pool via eSATA — 4-Bay ICYCube MB561U3S-4S with fan-mod
Edited 2 times, last by cabrio_leo: Wrong link ( Jul 13th 2017 ).
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!