Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Time Machine Maverick Problem Space with raidator 4.1.13
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-16
02:55 AM
2014-01-16
02:55 AM
Time Machine Maverick Problem Space with raidator 4.1.13
Hi Guys,
I updated my readynas Duo Sparc to the lastest build. (1tb of storage)
It work great but something strange appen.
On the web interface i setuped 60gb for Time Machine Partition.
The finder when i mount it show "you have 148 gb avaible" (correct avaible space but not correct for Time machine space)
Is it correct ?
Because i remeberd that it worked differently.
I want to limit the space. but i can't.
I updated my readynas Duo Sparc to the lastest build. (1tb of storage)
It work great but something strange appen.
On the web interface i setuped 60gb for Time Machine Partition.
The finder when i mount it show "you have 148 gb avaible" (correct avaible space but not correct for Time machine space)
Is it correct ?
Because i remeberd that it worked differently.
I want to limit the space. but i can't.
Message 1 of 9
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-16
03:04 AM
2014-01-16
03:04 AM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
Known issue.
Message 2 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-16
03:23 AM
2014-01-16
03:23 AM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
Uhm.. i can use TimeMachine ?
is there the possibility that something goes wrong ? .. can i damage my data in others partitions ?
is there the possibility that something goes wrong ? .. can i damage my data in others partitions ?
Message 3 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-16
03:40 AM
2014-01-16
03:40 AM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
Make sure you don't 100% fill your data volume.
Message 4 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-08-26
01:37 AM
2014-08-26
01:37 AM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
I continue to have this issue on my NV+. I understand there has been a fix in the firmware for newer models (like NV+ v2). But is there also a newer firmware than 4.1.13 available that fixes the issue for my NV+?
Message 5 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-08-26
05:21 PM
2014-08-26
05:21 PM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
Can you try this?: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222
Message 6 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-08-27
08:41 AM
2014-08-27
08:41 AM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
Hi mgdm
Thanks for that. I'm a bit hesitant to upload a Beta release. Is the official release planned for anytime soon?
Raymond
Thanks for that. I'm a bit hesitant to upload a Beta release. Is the official release planned for anytime soon?
Raymond
Message 7 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-08-27
02:27 PM
2014-08-27
02:27 PM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
This build has been around a while and should work fine. Having said that it would be a good idea to make sure your backup is up to date before trying any beta release.
I don't think so as it has long been EOL.
I don't think so as it has long been EOL.
Message 8 of 9
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-08-27
03:23 PM
2014-08-27
03:23 PM
Re: Time Machine Maverick Problem Space with raidator 4.1.13
I'd hope differently, since the beta contains at least one security fix (added yesterday).
mdgm wrote: ...I don't think so as it has long been EOL.
Message 9 of 9