RomeoApps

Evidence guide · Synology Drive on Mac

“Preparing” is a symptom, not a diagnosis.

A Mac sync failure can sit at several layers: an integrity mismatch, a queued server event, a connection channel that did not establish, or a local visibility problem. Start with the exported evidence and keep the source package private.

Independent RomeoApps software. It reads supported customer-owned exports locally; it does not connect to a NAS, bypass access controls, or upload support packages.

NAS Diagnostic Export Inspector showing evidence-linked problems and a privacy inventory
Example local report using a standard-container support fixture; findings remain linked to evidence and privacy context.

Start with the words in the export

What to look for before sharing anything.

These signals are useful starting points for review. Keep every conclusion tied to its source evidence.

01

Downloaded file hash mismatch with server response hash

Compare the integrity warning with its surrounding time, path, and session evidence instead of treating it as a generic “sync failed” message.

02

Session still has server events

Separate queued server work from a Finder or local file-visibility symptom before you decide what a support team needs.

03

Failed to establish a new channel (-2)

Keep connection and secure-channel lines visible while avoiding a claim of live NAS diagnosis or automatic remediation.

A safer handoff

Turn a noisy export into a reviewable report.

The paid inspector stays inside the published support boundary and makes a human review easier.

  1. Choose a supported standard-container export or readable diagnostic text you own or are authorized to process.
  2. Trace recurring signals, categories, uncertain timestamps, and exact source lines locally.
  3. Review the privacy inventory before creating a self-contained report or text-only safe-share ZIP.
  4. Share only the derivative you have authority to disclose; the tool cannot guarantee that every custom secret is found.

Scope boundary

Evidence stays local and reviewable.

  • The workflow uses no NAS connection, authentication, decryption, remediation, or automatic support upload.
  • Opaque or encrypted debug.dat, ZIP64, multipart/encrypted ZIP, RAR, 7z, and unsupported methods are rejected visibly.
  • Release fixtures are independently created and synthetic; this is not Synology software or a DSM/SRM compatibility claim.

Next step

Have an export? Check the support boundary first.

The product page lists accepted containers, budgets, the exact frozen release, and the recovery route before checkout.

Read the full release page