drm31078 wrote:Well, I have been transferred to another Synology support representative. Based on his response below, this issue is being caused because my entire file system is corrupted due to unexpected shut downs (like power outage or disk being unplugged). So I have to wipeout my entire disk station and put everything back on; not just my time machine sparse bundle. What the heck?! I dunno where I am going to put 500 gb of data temporarily. This is the whole reason why I bought a disk station! [Please control your language]!
"I will be the point of contact for this ticket moving forward.
I reviewed your logs and see that there have been several unclean shut downs in the past. This will cause a wide range of unexpected behavior including filesystem corruption. Your sparsebundle file sits on top of our filesystem, so, if the underlying filesystem is corrupted, then of course the file containing your sparsebundle 'filesystem' could be corrupted. The fact that Time Machine failed to fsck it helps to indicate this as well.
I recommend to backup your data, verify the backup, remove the volume, create a new volume, and restore from your backups to the new volume. You may then create a new Time Machine backup with the new volume.
If you can show us that this happens with a new volume and with no unclean shut downs in the past, we will investigate it.
Unclean shutdowns of our system is a common issue, hence why you see frequent complaints, because most people think that it can be treated like a Windows PC where you can pull the power and it will most likely be OK. This is not the same for our products as it is the same as a Linux RAID server.
I am sorry if this is not the answer you were looking for.
Synology America Corp | http://www.synology.com |
Users browsing this forum: No registered users and 3 guests