NTFS Write support on Mavericks

So this is 2014 and mac users aren't able to write on NTFS?

<Edited by Host>

.

Dude, I ran that command (new to the cult of Mac; googled my way to executing a .sh file) - I thought I could use this script on the Bootcamp Windows partition.

When I tried doing that, dunno what happened, I am not able to find the Windows partition when I hit Shift-Command-C in "Finder".

I am, though, able to boot into Windows. However, under Mac boot, I am not able to see the partition under "Start Up Disk" in System Preferences.

Upon executing the sh file in "Terminal", it returned an error saying the process was not a success (unable to recall what it exactly said) - but ever since then, the Windows partition is missing in "Finder".

Please help. ⚠

Hello,

This script cant damage any partition because it just writes the info for the new disk in /etc/fstab (which is used by the OS to know how to mount the device).

You might have been done something else while trying to know how to execute the. sh.

Anyway, you can try to edit /etc/fstab (you will need superuser permissions) and remove the line that the script might have added. After deleting that line (or lines), everything will be as before.

Regards

Thanks a bunch for your reply; no - I did not mean to say that the partition had been deleted. I'd meant to say, while running Mavericks (under Disk Utility), the Bootcamp Windows partition shows up as unmounted. If I try to mount it, it asks me to run First Aid. But I am unable to do so. All options are greyed out.

This is what I did to execute the .sh

cd Downloads (that is where the ntfs.sh had been downloaded to)

sudo ./ntfs.sh (It wouldn't allow me to run it without the sudo)

Could you please tell me how to edit that bit again? Not sure I understand you.

So... This is what I did.

sudo vi /etc/fstab

Prompted for password...

The editor showed my Windows and Elements (WD external HDD) had been configured to blah blah blah.

I deleted those lines and saved using :. x

When I tried to check the fstab again, the terminal pushed a message saying some .swp (swap) exists. I force-closed the terminal and rebooted my machine.

... And just like you said, I can see the Windows and Elements (Western Digital external HDD) listed on Finder again.

Thanks a lot, @neburim. I was very, VERY nervous all this while. Glad I got to learn something too. 🙂

Now... Back on topic - where did I err in the first place? Running the ntfs.sh didn't go as planned. Any insights, please?

It's weird. Perhaps you chose also the Windows partition when executing the script, instead of just your WD HDD (that I guess that it is what you wanted to mount as readwrite).

Try running the script again and when prompted to choose the partition be sure to choose just the one for the WD HDD.

Will try first thing tomorrow and post the result.

Quick q - how do I then ensure my Windows partition also has NTFS write support?

Also... Was I correct in the usage of those commands above? sudo ./ntfs.sh, etc. I'm a novice at this; hence asking. 🙂

Thanks again for taking time to read and reply!

Actually your windows partition would also have write support but may be something is happening behind. This script was created to add support to external drivers (usb and external hdd). dont know what kind of side effects can happen when applied to an embedded partition.

and yes, you were right with the usage of those commands.

The side effects were:

» The embedded NTFS partition became [almost] unmounted (could be mounted ONLY after editing the fstab)

» Which implied, the partition would not be detected while in Mavericks boot

Funny to think that ntfs.sh executed just fine with the external HD - but after ejecting and re-connecting the HD, it wouldn't show up on Finder.

And by deleting the required lines in fstab, the HD - quite obviously - lost the NTFS support.

---

Conclusion: Either I am a SERIOUS noob (ok, make that naïve, ha ha!), or something funny is indeed happening which I can't comprehend.

PS: I've tried Paragon NTFS - it worked for a few days, but soon stopped detecting NTFS partitions. Tuxera never worked for me from Day 1.

Would you be willing to briefly explain how to run the commands successfully in terminal? I've googled it and am still a bit confused and nervous that I'm going to do something catastrophic. 😕 Thank you so much if you're willing!

Have a look at this:

http://osxdaily.com/2013/10/02/enable-ntfs-write-support-mac-os-x/

I just rebuilt my hard drive on my MacBook Pro by reinstalling Mavericks from scratch. I forgot I had a need for NTFS support until a couple of my drives couldn't be written to. I did a quick search and found the software that came with my Seagate Drives. Evidently it is a free version of Paragon's software that supposedly only works with select Seagate drives. I installed it on Mavericks and it worked fine. Your results may vary.

You can find it here:

http://www.seagate.com/support/downloads/item/ntfs-driver-for-mac-os-master-dl/

This 2014 and Windows users aren't able to read/write to HFS+?

I received a copy of Tuxera NTFS as part of an external USB drive purchase. I installed it on my old Mt. Lion Mac and it worked as promised. When I updated to Mavs I reinstalled it and it still works as advertised.

The only issue I have is with the iOmega (now Lenovo) software for the NAS device I'm using. Sometimes my drive shows up, sometimes not. But I can always mount it with the Finder and Tuxera. My version is 2012.3.3.