Time machine to Readynas NV+ stopped working.

Question

Level 1

6 points

Time machine to Readynas NV+ stopped working.

I've been using a ReadyNAS NV+ for time machine back up and it has been working fine.

Recently I tried to change the backup interval/ frequency and modified some plist files as commonly instructed. Then the time machine seem to stopped working. I've restored the plist files from the time machine, but the time machine still didn't work.

It's always stuck at "waiting to back up".

I've tried to use an external USB drive to do the backup and it's the same.

Here's what I found in console:

11-04-25 7:53:07 PM kernel AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 450

11-04-25 7:53:08 PM kernel AFP_VFS afpfs_unmount: /Volumes/ReadyNAS, flags 0, pid 453

11-04-25 7:53:08 PM kernel ASP_TCP do_thread_read: no reqInfo found for reqID 1

11-04-25 7:53:08 PM kernel ASP_TCP CancelOneRequest: cancelling slot 26 error 89 reqID 27 flags 0x9 afpCmd 0x14 so 0x5b62ce0

11-04-25 7:53:56 PM com.apple.launchd[1] (com.apple.backupd-attach[452]) Exited with exit code: 1

Could somebody help me solve this??

Thanks.

MacBook, Mac OS X (10.6.7)

Posted on Apr 25, 2011 7:57 PM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Apr 25, 2011 9:09 PM in response to Roadie-Z

First of all, Time Machine backups to a network volume are not supported unless the volume is hosted on a Time Capsule or on a Mac running 10.5 or later. It may seem to work for a while, but it will eventually fail and result in data loss.

Next, are you saying that you have a separate, independent TM backup to a USB drive that has stopped working? If so, please launch the Console application, select "system.log" from the list on the left, and enter "backupd" (without the quotes) in the filtering text box. Then run a TM backup. Post any error messages that appear.

Reply

Answer 2

Roadie-Z Author

Level 1

6 points

Apr 26, 2011 9:15 PM in response to Linc Davis

As you can see, I'm using OSX 10.6.7.

Try running the backup to the USB shows this:

Apr 26 20:57:32 new-host-2 /Applications/System Preferences.app/Contents/MacOS/System Preferences[1016]: TMShowUnsupportedNetworkVolumes is set to TRUE which allows selection of unsupported Time Machine network destination volumes. Use of an unsupported network destination can result in silent data corruption and complete loss of backup data under certain circumstances!

Reply

Answer 3

Linc Davis

Level 10

209,739 points

Apr 26, 2011 9:31 PM in response to Roadie-Z

As you can see, I'm using OSX 10.6.7.

Not on the NAS, you aren't. And the NAS is hosting the backup volume.

Use of an unsupported network destination can result in silent data corruption and complete loss of backup data under certain circumstances!

That's my point. Your configuration will eventually result in the loss of backup data. You won't know it's happened until it's too late.

Reply

Answer 4

Roadie-Z Author

Level 1

6 points

Apr 26, 2011 9:44 PM in response to Linc Davis

so, what's your point? That's the USB.

Reply

Answer 5

Linc Davis

Level 10

209,739 points

Apr 27, 2011 3:13 AM in response to Roadie-Z

Yes, I see that. You haven't reversed the hack that allows you to select the NAS as a backup destination. Until you do, you'll continue to get that warning.

Reply

Answer 6

Roadie-Z Author

Level 1

6 points

Apr 28, 2011 4:08 AM in response to Linc Davis

Just an update to the future readers of this thread, in case you come across the same problem. I've solved the problem by doing the following. Do a safe boot; initiate the time machine back up to a USB. Once it's started, you can stop it. Boot back to normal mode. Time machine worked again, it was able to back up to the NAS and the entire database is intact from day 1 of the history.

Linc, FYI, no hack was required to back up to the ReadyNAS. It is officially compatible, and tons of people are doing it. Also, I wasn't able to do back up doesn't mean the data was corrupted. I was able to see the backup files in my NAS all along. The time machine just stopped doing backup.

Reply