TimeMachine Not Working (OSStatus Error 89)

[euphogeeza]

I have a QNAP TS-559 Pro running the latest version of firmware 3.8.2 Build 20130301
Disks: 5 x 4Tb disks in single Raid 5 array,
Trunking: Boths NICs are bound using "Balance-alb", 1500 MTU on 1000Mbps

It has been running the TimeMachine application for approx 15 mac's for 2-3 months with no issues. Mac's have all been backing up without a hitch.... until about 2 weeks ago when everything just stopped.
When trying to connect to the TMBackup drive from the mac...
Time Machine Preferences -> [Select Disk...]
Select "TMBackup on NASDRIVE(TimeMachine)" and then push the [Use Backup Disk] button.
The "Connecting" progress bar appears...
then the "Enter your name and password for the server" dialog opens.
Enter "TimeMachine" in the Name field
Enter the password in the Password field and press the [Connect] button.
The revolving beach ball appears... time passes... even more time passes... and eventually...

Time Machine can't access the backup disk "TMBackup".
The operation couldn't be completed. (OSStatus error 89.)

I know that I am entering the correct password, because if I deliberately enter an incorrect on the "Enter Password" dialogue IMMEDIATELY shakes and then requests the password.

I can't find any relavant information of the web about "OSStatus Error 89".

We have tried...
* Disabling and Re-enabling the TimeMachine on the TS-559 Pro
* Rebooting the TS-559 Pro
* Changing the password
* The interface will not allow the password to be removed completely (set to nothing).
* Rebooting client macs
* Even deleted the sparse-bundle for one of the mac's to see if it would then reconnect and recreate it's backup

I am seriously scratching my head. Can't think what else to try...

Oh can't "repair" the backups. TimeMachine clients need to be able to connect to the disk before it can see the backup files and attempt a repair.

[thoobs]

Hi there,

Since today I have the same problem. Can't figure out what it is although I have had some TM problems in the past.
I have a Qnap TS 212.
Hopefully someone is able to help us out (-:
Regards,
Thoobs

[PhilXtra]

The same problem here......everything working until first week of april with 3 Macs then I cant get time Machine to work
Have tried all of the above to and using tmutil set destination fix
All my software firmware is latest

Am at a loss here as well

[rBennich]

I have the same problem as from about 1 week back. Could it be the latest software for the qnap messing things up, since we now are several people having the same problem in a short timespan?

[PhilXtra]

just downloaded on QNAP advice latest version of firmware.....3.8.3
this did not help

[PhilXtra]

Problem solved

QNAP support connected to my Mac and the problem was metadata on NAS
Problem sorted within 48 hours of my email to QNAP and would have been 24 hours if I could have been at Mac yesterday

I am not sure if this was original problem cause as I did delete old backups in my own attempts to solve problem

I have a sneaky feeling that was a mistake and might have been at least a part cause of problem if not the original cause

Anyways QNAP support was first rate and I think I am back in business

[thoobs]

Hi PhilXtra,

Good to hear that the problem is solved. You say it is a Meta data problem.
I don't understand what I have to do to solve the problem. Are you able to explain this?
I still have my old backups since March.

Thank you!
Thoobs

[rBennich]

Hi! I'd also be intrested in hearing what solved this problem, as i have the same error.

Thanks!
/Robin

[PhilXtra]

Well I did not solved the problem really I emailed QNAP support and they dialled in and very helpfully solved the problem.
The support guy after checking a few basics opened a terminal window and using unix/linux command
I could not follow all of what he did but essentially I think the sparsebundle or something related to it had become cprrupt on NAS

I really would recommend emailing QNAP support they were first rate and one simple remote session sorted out weeks of hassle

[eirda]

Also curious as to what was/is the solution...

[pwilson]

Also curious as to what was/is the solution...

Have you folks actually read the Firmware v3.8.3 Release Notes?

Notes :
[Version]
3.8.3 build0426

Change log:
- Support Seagate 4TB Backup Plus 4TB USB 3.0 drive for Mac (STCB4000103)
- Updated the time zone of Minsk to GMT+03:00
- Removed Windows Live Messenger notification support due to Microsoft service termination
- Improved RTRR Real-time Mode stability while uploading large amounts of files concurrently
- Improved the compatibility with Citrix Xen Server if CHAP authentication is used
- Improved the stability of VAAI iSCSI
- Fixed the PDF or Adobe-related file, and ChronoSync (*.sync) file visibility issue with AFP connection
- Fixed the color label issue on AFP connection
- Fixed the auto-rescan issue when the NAS restarts if the Media Library is set in Manual Scan mode
- Fixed the login issue of new user accounts from Standalone Application Users in Multimedia/Photo/Music Stations
- Fixed the public album visibility issue in Multimedia Station when a new user account from System Users logs in
- Fixed the Wake-On-LAN (WOL) issue on TS-509/809 Pro
- Fixed inaccurate CPU temperature detection on some models
- Fixed the system error while deleting a new user account via CSV User Import function with Advanced Folder Permission enabled
- Fixed the Microsoft Networking Host Access Control wildcard issue in specific network configuration
- Fixed Amazon S3 backup issue when the file name contains [ or ]
- Fixed the Autorun.sh compatibility issue on ARM-based NAS
- Fixed the issue for truncated local & domain group name and permission settings if the name is over 40 characters long
- Fixed the "Relaunch upsd" issue

Note: TS-112, TS-212, TS-412 firmware cannot be downgraded after upgrading to firmware 3.8.3 or later.


[Version]
3.8.2 build0301

Change log
- VMware VAAI support for the TS-x79, x70U, and x69 series
- VMware vSphere Client Plugin support for the TS-x79, x70U, and x69 series
- Windows Server 2012 Compatibility Certification for the TS-x79, x70U, and x69 series
- Amazon S3 cloud storage now supports objects greater than 2 GB
- AFP upgraded and data transfer performance enhancement on small files
- [x86] Kernel upgrade to 3.4.6 for the TS-x79, x70U, x59, x39, 509, 809, and SS-x39 series
- Updated Gigabit Ethernet drivers for the TS-x79 and x69 series
- PowerWalker USB UPS support (refer to the UPS compatibility list on the website for specific models)
- HDD Health now displays I/O history for the diagnostics
- Wireless LAN IP is displayed on LCD-equipped models
- Auto port-mapping support for multiple NAS setup in the Auto Router Configuration (connected via MyCloudNAS.com)
- Remote Replication UI enhancements
- Improvements to HFS+ compatibility
- UPnP Network Discovery security enhancements
- [ARM] The following kernel patches have been applied to the ARM-based models: CVE-2010-2521, CVE-2010-2248, CVE-2010-1162, CVE-2010-2478
- Fixed upload error in case of destination folder name containing '&' in the Web File Manager
- Fixed non-stop media library scanning if the Music Station is disabled or changed to manual scanning
- For the Music Station, the finish time is added in the media library scanning schedule

Note1: The firmware can’t be downgraded on the TS-x69 series after upgrading to 3.8.2.
Note2: OpenSSL and OpenSSH upgrades are currently under internal development and testing. These updates will be included in the next major firmware version.

[watt4]

Thanks pwilson that was useful , not - We can read the release notes, none of the features say stuff our Time Machine Backup and your response does nothing to help us resolve it

After talking to Tech support

could be that your Timemachine backup file is corrupted. If it's okay for you, it should be fixable by deleting the Timemachine files in the NAS and creating a new backup. The steps are below:

Disable Time Machine backup from the NAS admin page
Access the NAS via SSH in Terminal i.e. ssh admin@<ip of nas>
Delete the Time Machine files with the command:
rm -r /share/MD0_DATA/.timemachine
Enable Time Machine backup again
Run a Time Machine backup from your Mac

This resolved my issue

Thanks

[thoobs]

Hello watt4,

thanks for sharing how to solve the problem. It is not the first time that my NAS and TM have this problem. I used to delete the TM sparebundle form my NAS via the administrator menu. It alwat's helped but unfortunatly not for a long time. I have a backup form my Macbook but if I delete the sparebundle I won't have it anymore. Is there a way to find the sparebundle and to backup it.
Thank you!

[dregina]

Hey Watt4,

Thank you for sharing... that completely solved my issue!!!

Thank You !!

[Behold]

Cheers Watt4 solved all my issues as well.