I have been going back and forth with Synology support since they said that the wireless connection is the problem. This happened to me a few times, but I have Time Machine logs for two of them. One on 12/27/11 and then it happened again on 3/22/12 (almost 4 months apart). Both times I have the following Time Machine log entries on the day it happened:
QUICKCHECK ONLY; FILESYSTEM DIRTY
Runtime corruption detected on /Volumes/dans time machine/Daniel McDonaldÕs MacBook Pro.sparsebundle (fsck_hfs -q termination status: 3)
The support guy (Michael) is still not sure why the file is getting corrupted, he is thinking that it could be because I have the "hibernation" option enabled or could be the wireless connection:
"This means the backup was corrupted, hfs is the mac file system and Time Machine is running fsck (a linux/unix command) to fix it. Still no mention why the sparsebundle is getting corrupted, just that it is. I’m leaning on the hibernation as a possible factor and maybe running wireless. Prolonged testing would suggest a possible solution."
Now Synology is asking me to give them admin access to my diskstation?! I told them no, but offered to give them all of my macbook/DSM settings or do a remote assist where I can watch what they are doing. I also told them they should do their own testing with their own MBP since it seems this is a wide spread problem. Still awaiting a response. It sounds from the following statement from them, if I don't give them access there is nothing else that will be done.
"With all due respect, I’m still not convinced that it’s a DiskStation issue at this point. All I have seen based on the research that I have done in addition to what I have given you in links is that while there are some Synology units affected it is the environment (their computer, the connection, etc) that is the likely cause of the issue. I have seen this myself and it was just a change in habits of how they handle their backups.
If you want us to resolve the issue in a timely fashion which I would prefer then we require remote access for escalation to one of our engineers to check out. If you don’t want this, along with not being able to perform backups wired then our hands are tied because we don’t have a baseline for testing to prove that it’s a DiskStation issue which you think it is.
Please let me know how you would like to proceed.
Synology America Corphttp://www.Synology.com
This is so frustrating. This needs to get bumped up to their engineering department. It's clear that the customer support people do not have the expertise to resolve this.