Mailcow change volume (please help me)

Rex

ood day,
i really need help regarding changing volume for mailcow, beacuse i have only limited hardrive on my ubuntu 18.04.
i followed this instruction https://mailcow.github.io/mailcow-dockerized-docs/u_e-dovecot-vmail-volume/ and the error came with this Starting mailcowdockerized_dovecot-mailcow_1 … error ERROR: for mailcowdockerized_dovecot-mailcow_1 Cannot start service dovecot-mailcow: error while mounting volume ‘/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data’: failed to mount local volume:

ERROR: for dovecot-mailcow Cannot start service dovecot-mailcow: error while mounting volume ‘/var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data’: failed to mount local volume:

in my fstab
192.168.1.4:/volume1/MailServer /home/mail nfs nouser,rsize=8192,wsize=8192,atime,auto,rw,dev,exec,suid 0 0

Please help me

diekuh

Iirc you use Synology as NFS provider. As I told you, they rewrite UIDs and GIDd to a user on the NAS. That will not work. We need the IDs 5000.

Use iSCSI and mount it as block device.

Rex

@diekuh Thank you so much.
ill just used another hardrive,
Thanks again.. Stay safe

diekuh

You too, thanks. 🙂

p0wer

https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/file_share_privilege_nfs

-> 8. Squash
Map all users to admin: Assigns access privileges to all users of NFS client equivalent to the admin user access privileges on your system.

should work if changing nfs permissions is an option.

ISCSI with synology is kinda wierd since you have to shrink a volume and setup iscsi within a dedicated volume.
Or am i missing a point. just got familiar with this stuff some time ago configuring XCP-ng. Since then plain NFS with IP restrictions : ))

diekuh

The user in the Synology that you map to needs the same UID and GUID. Plus it must not enforce a umask.

Rex

Good day, moving vmail to other disk is ok but moving mysql redis and others will get error..

why is that?

please help