Bridging The NTFS Gap Between Windows and OS X – If you’ve ever tried shifting documents between a laptop running windows and one running Mac OS X, chances are you’ve faced the issues arising due to NTFS and FAT formats. Windows, by default prefers the usage of NTFS formats on it is drives, and when you have formatted external hard disks and pen drives on windows, you maximum probably have used NTFS to format those.
That’s all well and exact in the windows universe, but switch over to a Mac and you’ll notice how OS X can read those NTFS formatted disks however not write anything to them. That’s one among the largest problems in cross platform compatibility for external information garage between windows and OS X.
What We Can Do
- The most common solution you will hear to this is to format drives in FAT. While this works, we will give you two explanations why you might not want to do this:
- Your disk might already contain valuable data that will be lost if you format it into FAT.
- You might need to transfer files larger than 4GB into your disk, and FAT doesn’t allow this.
So, how to bridge this glaring gap between Windows and OS X?
We discover the feasible solutions to this trouble nowadays. But, earlier than you can understand what to do, you want to understand what it’s far that you are trying to restore. A little heritage is so as:
NTFS and FAT are two of the most commonly used file systems to format drives. These are abbreviations for New Technology File System and File Allocation Table, respectively. These formats govern how disks arrange data.
The usage of FAT can actually fix most of your troubles with the use of the same external storage between windows and Mac, but, there’s the caveat that files large than 4GB can’t be saved inside disks formatted the usage of FAT.
How to Enable NTFS Write Capabilities on OS X
OS X natively helps reading capabilities for disks in the NTFS format. This means you can use your NTFS formatted disks with OS X to read documents from. However, you cannot switch documents from your Mac to the disk in question.
So, you’re flummoxed? Don’t worry, we’ve the fix, and we are going to provide an explanation to you. As it turns out, there are possible solutions to this hassle.
1.Third Party Applications
Observably you were not the first to stumble upon those boundaries, so problem solvers have pop out with answers in the form of third party applications. Those are available each paid and free variations, but before you bounce ahead to the free section, be warned, the free one takes a lot more hard work and is commonly not as dependable as the paid ones.
- The great human beings at Paragon software organization and Tuxera have created utilities that bridge the NTFS gap between windows and OS X.
- All you want to do with these applications is download them (and deploy, glaringly.) and also you’re prepared. Well, almost. You do need to restart your laptop for the adjustments to take effect, and now you can freely read/write on NTFS drives with none problem.
- “Paragon NTFS for Mac” is priced at $19.95 and has a ten day trial in case you want to make sure that it really works out for you.
- “Tuxera NTFS for Mac” is priced at $31 and has a 15 day trial.
Each of those applications come with the added functionally that allows you to layout a drive the use of NTFS or create partitions. We have attempted Paragon’s presenting and it is well worth the price.
Additionally, note that if you’re using a Seagate drive, Seagate gives a free license for “Paragon NTFS for Mac”, with the limitation that it only works with Seagate drives, or with drives which are synthetic by Seagate. I could use it with a Samsung external HD that was synthetic by Seagate.
osxfuse” is an open source app hosted on GitHub that also permit users to write to NTFS drives on Mac. The method is tediously long, and not suggested if you’re not comfy with the usage of the Terminal, or rebooting your Mac into recovery mode.
Although, we’ve got outlined the steps here.
- Download and install osxfuse.
- Download Homebrew(a command line package manager for Mac), if you don’t have it already.
- Open Terminal, and type the following command:
brew install homebrew/fuse/ntfs-3g
- Now, you will have to disable System Integrity Protection(SIP, or “rootless”). To do this, you need to reboot into recovery mode.
Turn your Mac off and press Command + R while starting it up again. This will boot up your Mac in a recovery environment.
- Launch Terminal and type the following command:
This will disable System Integrity Protection on your Mac.
Reboot your Mac normally.
- Open Terminal and type the following commands:
sudo mv /sbin/mount_ntfs /sbin/mount_ntfs.original
sudo ln -s /usr/local/sbin/mount_ntfs /sbin/mount_ntfs
- Next, you to re-enable System Integrity Protection.
Reboot your Mac into recovery.
- Launch Terminal and type the following command:
This will enable System Integrity Protection on your Mac.
- Reboot your Mac.
- NTFS should now be working on your Mac.
Good enough, that was a number of works to do. Specially, considering how there are much simpler and easier methods accessible. Also, deactivating system Integrity protection isn’t something that need to be completed lightly as it permits root programs to access protected files on your Mac and can make your Mac an easy target for malware, or lead to corruption in your startup disk.
2.Apple’s Experimental Feature
As it turns out, Apple themselves have an experimental characteristic that may be enabled to permit NTFS writing functionality at the Mac. This technique also needs the use of command line, but it does not require you to disable system Integrity protection.
Observe: Being an experimental function, this could not work nicely, it would corrupt your data, your disk, or cause data loss. Continue with caution, and at your own risk.
The steps you want to take, in order to permit this feature are given under:
- Fire up Terminal on your Mac.
- Type the following command:
sudo nano /etc/fstab
You need to add the following line to the file:
LABEL=DRIVE_NAME none ntfs rw,auto,nobrowse
Replace the DRIVE_NAME with the name of your disk.
Make sure the DRIVE_NAME you are using does not contain any spaces as this might cause issues.
- This will enable write support for your drive.
If your drive has a complex name with spaces and the like, you can use the device UUID to enable write support for that drive as well. To find the UUID for your disk, you need to run the following command on the Terminal:
Ediskutil info /Volumes/DRIVENAME | grep UUID
Replace the “DRIVENAME” with the name of your disk.
Once you have the UUID for your disk, you need to follow these steps:
- Open Terminal on your Mac
Type the following command:
sudo nano /etc/fstab
Add the following line to the file:
UUID=DEVICEUUID none ntfs rw,auto,nobrowse
Replace “DEVICEUUID” with the UUID for your disk.
The limitation with this experimental technique, is exactly that; it’s experimental. There is no assurance that it will work properly. It might corrupt your data, or even corrupt your entire disk. Also, this method needs you to include one line “per disk” for it to work. So if you have more than one disk that you need to write to using this technique, it’ll be needlessly tedious.
The reality that Apple has an experimental feature to allow writing skills for NTFS disks hints a little bit at a probable native support for NTFS writing. That is ideal information, but it’s also unconfirmed. For all we know, Apple might completely eliminate NTFS writing support from the OS, leaving users without a desire but to use third party apps.
If you have the choice, we recommend that you layout your disks using exFAT. exFAT is a layout that is supported by way of both windows and OS X and it does not have the 4GB document size restrict that FAT does.
However, like almost the entirety in technology, exFAT too has a caveat in that it might not be supported by the way of older variations of OS X and by windows machines running windows XP and older. Which means that you continuously find yourself sitting in front of a computer running windows XP or older, then exFAT is not the first-class preference for you as it might not even get detected by the older operating systems.