Closed GoogleCodeExporter closed 9 years ago
No... it still does not support HFS+ with journalling, an it is required by
time machine to work.
Original comment by egcarr...@gmail.com
on 20 Nov 2012 at 7:39
HFS+ with journalling is not supported on linux, hence it is not supported here
either. Probably will never be supported either.
Then again: you don't need it. It is a NAS, so a network sharing system will be
used (afp in this case). As long as the NAS can write to the drive it can use
any filesystem on the drive. It will then expose it using afp to the network
(hence NAS: Network Attached Storage).
The only problem is that you will need to format your drive to use it with the
router. I chose ext4 as my filesystem, but you can use others as well. I would
recommend a linux filesystem since they tend to be more stable.
Setting up everything the right way is described in some other posts.
Original comment by jord.sw...@gmail.com
on 20 Nov 2012 at 8:30
This is not true and I have it working at home. I'll update this post as soon
as I get home.
All you need is a firmware that supports HFS+, no journaling required at all.
Original comment by ferreira...@gmail.com
on 30 Nov 2012 at 11:20
Yes. Please post how you managed to get Time Machine supported using external
hdd on RT-N56U. Thanks!
Original comment by dzei...@gmail.com
on 5 Dec 2012 at 12:21
Was this solved?? I have this issue now with the ASUS standard firmware and
want to know if installing this firmware will solve the issue. Thanks
Original comment by tpoy...@gmail.com
on 28 Dec 2014 at 12:00
There is no need to use HFS+ for OS X Time Machine. I use EXT4 to create
backup. I'm on OS X Mavericks. The same configuration was used for previous OS
X versions.
Original comment by d...@soulblader.com
on 30 Dec 2014 at 6:38
[deleted comment]
Can anyone post the settings required for this? I'm on Yosemite
Original comment by winarto
on 16 Feb 2015 at 2:45
I'd love an answer to this question too.
Original comment by gingermo...@gmail.com
on 20 May 2015 at 3:21
Original issue reported on code.google.com by
zachraven@gmail.com
on 20 Nov 2012 at 6:29