Synology Administration Guide#

1 Syncthing Deployment#

1.1 Synology DSM Implementation (Docker)#

1. Inotify Limit:

   echo "fs.inotify.max_user_watches=204800" | sudo tee -a /etc/sysctl.d/90-override.conf
   sudo sysctl -p /etc/sysctl.d/90-override.conf

2. User IDs: Use Task Scheduler to run id > /volume1/docker/id.txt to find UID/GID (e.g., 1027/100).
3. Docker Compose Highlights:

   environment:
     - PUID=1027
     - PGID=100
     - TZ=America/New_York
   volumes:
     - ./config:/config
     - /volume2/HP3Storage:/volume2/HP3Storage

1.2 Standard .stignore Patterns#

Create a .stignore file in the root of the sync folder:

(?i)#recycle
@eaDir
.DS_Store
.stfolder
.stignore
$RECYCLE.BIN
Thumbs.db
Desktop.ini
.SynologyWorkingDirectory

2 Storage & Maintenance Commands#

2.1 iPerf3#

sudo -i
synogear install
iperf3 -s -p 11111

2.2 Locked Folder Cleanup#

Remove Synology metadata directories when cleaning up a locked folder:

Immich & Photo Management Guide#

1. Synology Photo Workflow#

Album Creation#

1. In Synology Photo:
   • Move images from Personal space to Shared Space.
   • Create an album with the moved images.

2. Immich Management#

Update Attempt — 2026-10-02#

• Host: HP1GPU (10.1.2.231), compose directory /home/marc/docker-compose/immich.
• Attempted stable upgrade from v3.1.0 to v3.2.4, including CUDA machine learning; PostgreSQL and Valkey images were unchanged.
• Pre-upgrade database dump: /mnt/Immich/Immich-Uploads/upgrade-backups/2026-10-02-v3.2.4/database.sql.gz. Gzip integrity check passed and the SQL dump completion marker was verified.
• Original compose file preserved as docker-compose.yaml.pre-v3.2.4; stable image override saved as docker-compose.stable-v3.2.4.yaml.
• Server failed to start with PostgreSQL password authentication failure. Restored the original compose file and recreated both application containers with local v3.1.0 images using docker-compose.recovery-v3.1.0.yaml.
• The same database authentication error persisted after rollback to v3.1.0, indicating an authentication/configuration issue upon container recreation. Following the user’s restart through their 1Password workflow, the API responded successfully with v3.1.0 and pong, with zero application container restarts. The stable upgrade remains pending. Credential inspection requires explicit authorization under the vault agent instructions.
• Root filesystem has approximately 3.2 GB free (95% used); old and new images retained. No database restore or credential changes performed.

External Libraries & Albums#

1. Scan Libraries: Settings > Administration > External Library > Scan All Libraries.
2. Monitor Progress: Jobs > Check when the job is finished.
3. Create Album: Main page > Albums > Create Album > Select Photos.
4. Sharing: Share with Nadine.

Backup Strategy#

• Photo ingress: The HP1Photos share on the Synology VM is the source of truth and is pushed one-way to the UNAS-Pro Photos share by the Linux sync hosts.
• Immich: Immich reads the photo library from the UNAS-Pro Photos share.
• UNAS-Pro protection: TrueNAS nodes pull the Photos and Immich data from UNAS-Pro according to the schedules documented in Unifi UNAS-Pro Backup Strategy.
• Manual sync: Run pushphotos on HP1GPU (10.1.2.231) or HP1Docker (10.1.2.202) when a sync is required.

See Unifi UNAS-Pro Backup Strategy#3.2 Synology Photos to UNAS-Pro Push for the mounts, script, exclusions, and deletion policy.

Syncthing Installation & Configuration Guide#

1. #truenas TrueNAS Scale Installation#

Increase Inotify Limit#

For real-time file watching on large datasets, increase the inotify limit in the TrueNAS backend.

1. Go to System Settings > Advanced > Sysctl.
2. Add New Sysctl:
   • Variable: fs.inotify.max_user_watches
   • Value: 524288
   • Description: Increase inotify limit for Syncthing.
3. Verify persistence via Shell:

cat /proc/sys/fs/inotify/max_user_watches

App Deployment#

1. Apps > Settings > Advanced: Disable “Host Path Safety Check” (if using existing datasets).
2. Catalog: Search for and install the Syncthing Enterprise version.
3. Storage Configuration:
   • Type: Host Path
   • Host Path: /mnt/HP1-4TBSSD-Raid0/HP1Storage (or your specific data path).
   • Mount Path: HP1Storage
4. Access: Open the Web UI at http://[IP]:31000. Set an Admin password immediately.

2. Synology DSM Installation (via Docker)#

Increase Inotify Limit#

1. Connect via SSH and run:

echo "fs.inotify.max_user_watches=204800" | sudo tee -a /etc/sysctl.d/90-override.conf
echo 204800 | sudo tee /proc/sys/fs/inotify/max_user_watches

Identify User IDs (PUID/PGID)#

To avoid permission issues, run the container as your specific user.