- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Time Machine not working
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to setup Time Machine on my Ultra 2 plus. I go to the backup->time machine section of frontview. I enter a password and a size of 50gb (there are 111gb free space remaining. Check the box to enable time machine. I hit apply and the ready nas changes the size back to zero and does not enable time machine.
What is going on and how can I correct it? I know I had this working before a few years ago, but I havent used it in a long time. somewhere in the past I deleted /c/.timemachine also using SSH.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just for kicks I upgraded to 4.2.28-T6. still got the same reaction in frontview, enter password and a size, hit apply, th enumber changes to zero. but then when I went to time machine prefs, the ReadyNAS share shows up and seems to be working now and when I go back to the time machine page in frontview, it shows the size I had entered. Dunno, maybe it was always working and its a javascript glitch. Anyway, seems to be working On mavericks even.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Time Machine not working
By the way, NAS is running the 4.2.27
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just for kicks I upgraded to 4.2.28-T6. still got the same reaction in frontview, enter password and a size, hit apply, th enumber changes to zero. but then when I went to time machine prefs, the ReadyNAS share shows up and seems to be working now and when I go back to the time machine page in frontview, it shows the size I had entered. Dunno, maybe it was always working and its a javascript glitch. Anyway, seems to be working On mavericks even.