Beiträge von thk

Solved. The solution for was to clear the HSTS browser settings for my OMV host.

How to Clear HSTS Settings on Chrome, Firefox and IE Browsers (ssl2buy.com)

Thanks again.

Zitat von raulfg3

do you clear Cache? "Crtl+Shift+R"

Nargh, didn't think of that.
The "Ctrl+Shift+R" seems to do nothing, however http:80 works in a incognito browser, so I guess you are on to something... I just need to figure out why it still redirects in a standard browser. Perhaps it's saved in a cookie?
Thank you!

OMV keeps forcing redirect to https, even though the setting "Force SSL/TLS" is disabled.

Any thoughts?

================================================================================

= OS/Debian information

================================================================================

No LSB modules are available.

Distributor ID: Debian

Description: Debian GNU/Linux 11 (bullseye)

Release: 11

Codename: bullseye

================================================================================

= openmediavault information

================================================================================

Release: 6.9.4-1

Codename: Shaitan

Solved - kind of my own fault but... I totally agree with sakulthefirst - The UI error is very misleading. The OMV developers should definitely improve the ui error and do some kind of system readiness before Applying new config.

Running the quota command manually gave me the very simple answer to the issue:

>omv-salt deploy run quota 

ID: quota_check_no_quotas_8221b09f-a0ac-4ae1-b216-47641cebe874

Function: cmd.run

Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/8221b09f-a0ac-4ae1-b216-47641cebe874

Result: False

Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/8221b09f-a0ac-4ae1-b216-47641cebe874" run

Started: 20:15:17.191684

Duration: 40.796 ms

Changes:

----------

pid:

3665407

retcode:

2

stderr:

quotacheck: Scanning /dev/mapper/st2000lm007-backup [/srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874] quotacheck: Cannot sta

t old user quota file /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/aquota.user: No such file or directory. Usage will not be subtracted.

quotacheck: Cannot stat old group quota file /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/aquota.group: No such file or d

irectory. Usage will not be subtracted.

quotacheck: Cannot stat old user quota file /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/aquota.user: No such file or dir

ectory. Usage will not be subtracted.

quotacheck: Cannot stat old group quota file /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/aquota.group: No such file or d

irectory. Usage will not be subtracted.

quotacheck: Checked 952 directories and 13716 files

quotacheck: Old file not found.

quotacheck: Cannot allocate new quota block (out of disk space).

quotacheck: Cannot write quota (id 100): No space left on device

stdout:

done

Would be much nicer to give that output in the error UI instead - could have saved me a lot of hours.

Why it's doing the quota check in the first place... I don't know - I'm not using any quota. Maybe the merger.fs...?

I managed to do all steps, but OMV still fails.

• service quota status = Disabled
• delete the ,usrjquota=aquota.user,grpjquota=aquota.group entries from all mountpoints in /etc/fstab = ok
• reboot = ok
• rm /srv/filessystems/aquota.* = succesfully
• unmount new filesystem, hit Apply = Error
• hit "revert" = OK (new filesystem unmounted though)

OMV just puts ,usrjquota=aquota.user,grpjquota=aquota.group back into /etc/fstab entries, and also creates the aquota files on all filesystems again.

So, I think we can agree that it is OMV that does the "quota thing"?

However, the error is only appearing when I make changes to filesystems. Apparently other changes eg. sharing, is applied without error. But I'm still not happy about the filesystem error.

I'm only trying to add a new disk. I do not touch any of the existing filesystems. If mergerfs is using aquota files it's using it on all filesystems - not only the two merged ones. However I can't find any documention on that.

Also it seems that the issue is not there from the beginning. So it must be building up...

The error is gone when I hit revert, but the situation is NOT comforting. The aquota files are pretty new, so something is using them.

I'm using EXT4 filesystem on all filesystems, and I have one merger.fs. by the Union Filesystem plugin.

Would it help to attach full output of the error, or is is possible to set the omv log to debug so it would be possible to see which module is failing the quota?

Sure, here is the results:

root@openmediavault:~# /etc/init.d/quota stop
[ ok ] Stopping quota (via systemctl): quota.service.

root@openmediavault:~# quotaoff --user --group /srv/e54445c9-9b96-4c15-a4f7-972a48b50959/
quotaoff: Mountpoint (or device) /srv/e54445c9-9b96-4c15-a4f7-972a48b50959 not found or has no quota enabled.
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-042db4b0-0909-4f70-8d19-6692493e4fab/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-07486652-3d63-4830-9658-bc31a880af36/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-2469c19f-4a0a-4890-a049-90c91b0c2b49/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-2c70786e-f2e5-408b-989c-74dcc6c29cd6/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-33155609-8186-4945-9dcb-7859241c1733/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-5b133a5b-4fee-4b7c-ab4c-af5e900ca9e2/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-9820b579-39ab-4913-a07d-34037ab0f174/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-c437e26a-81e7-4be7-9708-2628db1d2f87/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-c5962e99-3e25-450f-b699-07ba87f83ee3/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-uuid-dfcd77f1-ef7f-4e6e-b20a-74c963bd42d0/
root@openmediavault:~# quotaoff --user --group /srv/dev-disk-by-label-basic/
quotaoff: Mountpoint (or device) /srv/dev-disk-by-label-basic not found or has no quota enabled.

Last one (/srv/dev-disk-by-label-basic) is the new filesystem I'm trying to create.

I can create the filesystem, apparently also mount it, but I cannot Apply the configuration - it fails. But If I hit "Revert" it stays mounted

However I think you are right about "some quota going on". There are some strange "quota" files on all filesystems :

root@openmediavault:~# ls -l /srv/dev-disk-by-uuid-8221b09f-a0ac-4ae1-b216-47641cebe874/
total 20
-rw-------  1 root users 6144 Mar 26 07:10 aquota.group
-rw-------  1 root users    0 Mar 25 22:19 aquota.group.new
-rw-------  1 root users 7168 Mar 26 07:10 aquota.user
-rw-------  1 root users    0 Mar 25 22:19 aquota.user.new
drwxrws---+ 7 root users 4096 Mar 28 08:43 backup

No, never - It just suddenly started to fail when adding a new disk. But it's not the new disk fail - it's like all the existing filesystems... I do not use Quota. It's the second time now in OMV5 - Can I active debugging somehow?

Thanks

Some time last year I started getting this crazy error when I was making changes to to file systems. I reinstalled OMV and reconfigured everything from scratch, and everyone was happy. But now.... It's BACK! What is it?

This is the first few lines of the error when I hit Apply. I can't find anything i the logfiles - Only on the screen.

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color quota 2>&1' with exit code '1': omv.privat.lan: ---------- ID: quota_off_no_quotas_07486652-3d63-4830-9658-bc31a880af36 Function: cmd.run Name: quotaoff --group --user /dev/disk/by-uuid/07486652-3d63-4830-9658-bc31a880af36 || true Result: True Comment: Command "quotaoff --group --user /dev/disk/by-uuid/07486652-3d63-4830-9658-bc31a880af36 || true" run Started: 08:09:20.759265 Duration: 89.242 ms Changes: ---------- pid: 2782986 retcode: 0 stderr: stdout: ---------- ID: quota_check_no_quotas_07486652-3d63-4830-9658-bc31a880af36 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/07486652-3d63-4830-9658-bc31a880af36 Result: True Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/07486652-3d63-4830-9658-bc31a880af36" run Started: 08:09:20.849234 Duration: 109.904 ms Changes: ---------- pid: 2782988 retcode: 0 stderr: quotacheck: Scanning /dev/mapper/wd30--raid5-media2 [/srv/dev-disk-by-uuid-07486652-3d63-4830-9658-bc31a880af36] quotacheck: Checked 1877 directories and 18759 files stdout:

Zitat von gderf

Unmount all drives in /srv in the shell and force the unmount if needed.

Then look in each mountpoint directory in /srv and see if anything is there.

Perfect! That was it. There was data in /srv folder behind the mount points.

Tank you!

Thanks, iIt's a good article for cleaning up, but its not resolving the issue with the mismatch between Disk Free and Disk Usage.

df usage says: 14 GB

du usage says : 2.5 GB

Anyone?

I have 16 GB system drive for openmediavault which is reporting 98% full

# df -h /dev/sda2

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 15G 14G 346M 98% /

However disk usage is only 2.5 GB

# du -d1 -x -h / | sort -h

4.0K /export

4.0K /mnt

8.0K /media

8.0K /sharedfolders

16K /lost+found

16K /opt

24K /home

128K /root

1.8M /srv

8.5M /etc

49M /boot

673M /var

1.8G /usr

2.5G /

Where are the rest 11,5 GB that it's reporting used?

Great thanks. Installed perfectly!

Why?

I'm installing on a remote server via KVM Console, and I do not have physical access to the server. The server has twelve disk and one sata-dom for OMV. I can't disable the scsi controller i BIOS as the sata-dom is residing on it.

The disk contains important data, and currently there is no backups available.

Does the installer really delete all the disks or is it just a precaution? Are there any other mitigations i could use?

/T

Same Issue here. Fixed with Boot-Repair-Disk.

Had to detach all disks but the omv systemdisk /dev/sda though. I'm using RAID and LVM

Hi,

Shouldn't the option "Enable port forwarding via NAT-PMP or UPnP" make an entry in the firewall for the Peer Binding IP Address? Apparently it only opens for the host IP Address.

Resolved in openmediavault-route 1.1. Thank you very much

Just upgraded to release: 1.1 Kralizec with plugin now openmediavault-route 1.0

Still same issue.

The Gui gives you the ability to create more than one static route, but it fails with more than one. Anyone having more than one static route?

Can this be done without the plugin directly from the comandline instead?

+1 with same issue and same solution