tomer@hc4-11:~$ which bash
/bin/bash
You should install the usrmerge package to fix this.
tomer@hc4-11:~$ which bash
/bin/bash
You should install the usrmerge package to fix this.
Both my OMV installs are doing this too for the last few days. cron jobs shouldn't produce any output unless there are errors. Can this be fixed please?
Isn't it dangerous to disable apparmor?
If you're having this problem after upgrading, then you didn't have AppArmor running anyway. Docker just thinks you did, mistakenly.
The output of those commands doesn’t give meaningful details to me, I’m afraid…
They might be meaningful to other readers though.
Also check /var/log/syslog, /var/log/messages.
I maybe that I am on OMV5, so the fix doesn't actually work for me.
The grub apparmor fix is not nothing to do with OMV. It's a workaround for a Docker bug. No reason why it wouldn't work on OMV 5.
See "systemctl status docker.service" and "journalctl -xe" for details.
What does it tell you if you run those commands as instructed?
Still getting this error after doing the fix on the first page
You did reboot, right?
added "xextraargs=apparmor=0" and after a reboot I still get
It's extraargs=, not xextraargs=
Worked for me. I edited /boot/armbianEnv.txt directly.
Add extraargs=apparmor=0 to ArmbianEnv.txt
It's /boot/armbianEnv.txt, not ArmbianEnv.txt
How about Odroid HC4? It works well.
Even better use the tool chronic (from package moreutils). It will suppress the output unless the program returns an error.
Did you create an override file? Otherwise your changes might be lost after the next update.
Thanks for the reminder, I have now.
If you are already running OMV6, and on the omv-extras->docker GUI page, and you have the proper docker root path setted, just click install again and it will create the needed file.
Thanks! That created the file, and now my containers starts on boot.
I had to add another dependency also to fix this. I have /home encrypted with fscrypt, and needed docker to wait until my unlock service ran before starting docker else the containers that need /home still fail.
I'm having this problem too. I've moved my Docker data off the root and to a disk (/srv/dev-disk-by-by-uuid-....) and my containers never come up on boot, even though they are set to restart: unless-stopped.
My OMV started at v5. I would guess the problem is that Docker is starting before the disk is mounted.
Post the output of:
cat /etc/fstabomv-showkey mntent
cat /etc/systemd/system/docker.service.d/waitAllMounts.conf
I have no /etc/systemd/system/docker.service.d.
fstab says
UUID=9865a0b7-94e4-469a-8102-02611e455672 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/acc49cfe-4343-414f-8583-5575550dfac6 /srv/dev-disk-by-uuid-acc49cfe-4343-414f-8583-5575550dfac6 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]
and omv-showkey says
$ sudo omv-showkey mntent
<mntent>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
<dir>/xxx/yyy/zzz</dir>
<type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
<opts></opts>
<freq>0</freq>
<passno>0|1|2</passno>
<hidden>0|1</hidden>
</mntent>
<mntent>
<uuid>c5f393d7-e253-49c7-8290-7f7b82c2dd3b</uuid>
<fsname>/dev/disk/by-uuid/acc49cfe-4343-414f-8583-5575550dfac6</fsname>
<dir>/srv/dev-disk-by-uuid-acc49cfe-4343-414f-8583-5575550dfac6</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<comment></comment>
<usagewarnthreshold>85</usagewarnthreshold>
</mntent>
Alles anzeigen
You can try fatrace
https://manpages.debian.org/bu…fatrace/fatrace.8.en.html
And make sure it is not SMART that is waking up your drives.
My disks are waking up, usually in under 10 minutes (default hd-idle timeout), sometimes slightly longer. SMART is disabled in the OMV configuration.
I have /home on disk (not on SD card). fatrace shows that the php session cleaner is accessing /home, but I think that is a false alarm because of the systemd unit using ProtectHome=yes, and not a real access to the disk.
It's a bit more complicated because I'm using ZFS so something else might be happening before the scenes that doesn't show in fatrace.
fatrace looks good for this. https://www.piware.de/2012/02/…-wide-file-access-events/
Take it out of its case then. You could run cables from the sata ports and put the board in another case with some creativity.
Good suggestion. I got some disk stands (https://sedna-shop.com/index.p…ct/product&product_id=126) and some SATA 22-pin extensions cables and now I can stack the disks and the HC4 more securely.
Depending on how hot it gets over summer I might need a bigger fan for the HC4. The CPU seems to sit around 52 degrees at idle.
Without beeing that knowledgeable, it seems there's some discussion on using NetworkManager over systemd-networkd.
Use NetworkManager (#187) · Issues · Arch Linux / archiso · GitLab
systemd-networkd is fine (and IMHO preferable) for a headless wired server. NetworkManager shines when you have a desktop environment and perhaps WiFi.
Failed to preset unit: Unit file /etc/systemd/system/systemd-networkd.service is masked.
This is weird. Which armbian bullseye image did you use? Does it happen to include a desktop environment?
The 'CLI' download would appear to be the one you want.
Ah the problem is my zfs-load-keys.service, which depends on network-online. Tricky.