Can't write to NTFS formatted drives The 2019 Stack Overflow Developer Survey Results Are InCan't Mount NTFS drive “The disk contains an unclean file system”How can I create and delete files in an NTFS partition?How can I resize an external USB NTFS partition?How do i restrict user to make changes to NTFS partition ? (in easy steps)?How can I change permissions on external drives right after formatting with GParted?NTFS Drive write access deniedInstalling Ubuntu and accessing NTFS driveNTFS disk is read-only and I can't change to read & writeUnable to Access NTFS partitionPermission Problems with Newly Formatted DriveCan't write on ntfs partition shared with Windows 10I/O errors when reading & writing downloads and uploads to NTFS drives

If a sorcerer casts the Banishment spell on a PC while in Avernus, does the PC return to their home plane?

Is it safe to harvest rainwater that fell on solar panels?

How did passengers keep warm on sail ships?

How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?

Can you cast a spell on someone in the Ethereal Plane, if you are on the Material Plane and have the True Seeing spell active?

Is Cinnamon a desktop environment or a window manager? (Or both?)

How to notate time signature switching consistently every measure

writing variables above the numbers in tikz picture

What to do when moving next to a bird sanctuary with a loosely-domesticated cat?

Accepted by European university, rejected by all American ones I applied to? Possible reasons?

Is an up-to-date browser secure on an out-of-date OS?

How much of the clove should I use when using big garlic heads?

ODD NUMBER in Cognitive Linguistics of WILLIAM CROFT and D. ALAN CRUSE

What information about me do stores get via my credit card?

Is it correct to say the Neural Networks are an alternative way of performing Maximum Likelihood Estimation? if not, why?

Are there any other methods to apply to solving simultaneous equations?

What is preventing me from simply constructing a hash that's lower than the current target?

How to obtain a position of last non-zero element

Button changing its text & action. Good or terrible?

How to support a colleague who finds meetings extremely tiring?

Deal with toxic manager when you can't quit

The phrase "to the numbers born"?

"as much details as you can remember"

How to charge AirPods to keep battery healthy?



Can't write to NTFS formatted drives



The 2019 Stack Overflow Developer Survey Results Are InCan't Mount NTFS drive “The disk contains an unclean file system”How can I create and delete files in an NTFS partition?How can I resize an external USB NTFS partition?How do i restrict user to make changes to NTFS partition ? (in easy steps)?How can I change permissions on external drives right after formatting with GParted?NTFS Drive write access deniedInstalling Ubuntu and accessing NTFS driveNTFS disk is read-only and I can't change to read & writeUnable to Access NTFS partitionPermission Problems with Newly Formatted DriveCan't write on ntfs partition shared with Windows 10I/O errors when reading & writing downloads and uploads to NTFS drives



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








6















I'm not sure what has happened, but I've all of a sudden lost write access to any of my NTFS external drives.



I installed a few games and apps from the software center, and now I can't make new folders or copy and paste files to anything that is NTFS. Everything is now read only, and I've tried so many things to fix it, but it seems hopeless.



Just to check if it wasn't the drives themselves, I made a little ntfs formatted truecrypt volume, and a fat formatted volume. And yes, it seems that Ubuntu is blocking me from writing anything to NTFS.



What happened here?



Whats a way I can simply get write access to my NTFS drives, so I can just backup all my stuff.



I'll probably reinstall Ubuntu. Please help.




UPDATE (and thanks everyone for their quick replies)



The problem has been solved.



Prior to noticing that I had lost NTFS write permission, I had installed GParted from the software center, and there was an extension called ntfsprogs that came with it.



During my search for a solution to the problem, I uninstalled GParted (as that was one of the apps I installed just before the problem). But that did not solve the problem.



I came across an app called 'NTFS Configuration Tool'. When I installed this, it said that the ntfsprogs extension needed to be removed (so I guess uninstalling GPARTED, didn't remove the ntfsprog extension).



I launched the NTFS Configuration Tool and now I have write access to NTFS drives. Unfortunately, I didn't check if I had write permission prior to launching the NTFS Configuration Tool, so I'm not sure whether the NTFS Configuration Tool, or the un-installation of ntfsprog gave me back NTFS write permission.



Hopefully if another newbee encounters this problem, they'll come across this page and know what to do.










share|improve this question
























  • Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

    – James T Snell
    Jan 5 '12 at 19:28












  • if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

    – Thomas Ward
    Oct 26 '12 at 14:38











  • ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

    – dearN
    Oct 26 '12 at 14:39

















6















I'm not sure what has happened, but I've all of a sudden lost write access to any of my NTFS external drives.



I installed a few games and apps from the software center, and now I can't make new folders or copy and paste files to anything that is NTFS. Everything is now read only, and I've tried so many things to fix it, but it seems hopeless.



Just to check if it wasn't the drives themselves, I made a little ntfs formatted truecrypt volume, and a fat formatted volume. And yes, it seems that Ubuntu is blocking me from writing anything to NTFS.



What happened here?



Whats a way I can simply get write access to my NTFS drives, so I can just backup all my stuff.



I'll probably reinstall Ubuntu. Please help.




UPDATE (and thanks everyone for their quick replies)



The problem has been solved.



Prior to noticing that I had lost NTFS write permission, I had installed GParted from the software center, and there was an extension called ntfsprogs that came with it.



During my search for a solution to the problem, I uninstalled GParted (as that was one of the apps I installed just before the problem). But that did not solve the problem.



I came across an app called 'NTFS Configuration Tool'. When I installed this, it said that the ntfsprogs extension needed to be removed (so I guess uninstalling GPARTED, didn't remove the ntfsprog extension).



I launched the NTFS Configuration Tool and now I have write access to NTFS drives. Unfortunately, I didn't check if I had write permission prior to launching the NTFS Configuration Tool, so I'm not sure whether the NTFS Configuration Tool, or the un-installation of ntfsprog gave me back NTFS write permission.



Hopefully if another newbee encounters this problem, they'll come across this page and know what to do.










share|improve this question
























  • Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

    – James T Snell
    Jan 5 '12 at 19:28












  • if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

    – Thomas Ward
    Oct 26 '12 at 14:38











  • ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

    – dearN
    Oct 26 '12 at 14:39













6












6








6


2






I'm not sure what has happened, but I've all of a sudden lost write access to any of my NTFS external drives.



I installed a few games and apps from the software center, and now I can't make new folders or copy and paste files to anything that is NTFS. Everything is now read only, and I've tried so many things to fix it, but it seems hopeless.



Just to check if it wasn't the drives themselves, I made a little ntfs formatted truecrypt volume, and a fat formatted volume. And yes, it seems that Ubuntu is blocking me from writing anything to NTFS.



What happened here?



Whats a way I can simply get write access to my NTFS drives, so I can just backup all my stuff.



I'll probably reinstall Ubuntu. Please help.




UPDATE (and thanks everyone for their quick replies)



The problem has been solved.



Prior to noticing that I had lost NTFS write permission, I had installed GParted from the software center, and there was an extension called ntfsprogs that came with it.



During my search for a solution to the problem, I uninstalled GParted (as that was one of the apps I installed just before the problem). But that did not solve the problem.



I came across an app called 'NTFS Configuration Tool'. When I installed this, it said that the ntfsprogs extension needed to be removed (so I guess uninstalling GPARTED, didn't remove the ntfsprog extension).



I launched the NTFS Configuration Tool and now I have write access to NTFS drives. Unfortunately, I didn't check if I had write permission prior to launching the NTFS Configuration Tool, so I'm not sure whether the NTFS Configuration Tool, or the un-installation of ntfsprog gave me back NTFS write permission.



Hopefully if another newbee encounters this problem, they'll come across this page and know what to do.










share|improve this question
















I'm not sure what has happened, but I've all of a sudden lost write access to any of my NTFS external drives.



I installed a few games and apps from the software center, and now I can't make new folders or copy and paste files to anything that is NTFS. Everything is now read only, and I've tried so many things to fix it, but it seems hopeless.



Just to check if it wasn't the drives themselves, I made a little ntfs formatted truecrypt volume, and a fat formatted volume. And yes, it seems that Ubuntu is blocking me from writing anything to NTFS.



What happened here?



Whats a way I can simply get write access to my NTFS drives, so I can just backup all my stuff.



I'll probably reinstall Ubuntu. Please help.




UPDATE (and thanks everyone for their quick replies)



The problem has been solved.



Prior to noticing that I had lost NTFS write permission, I had installed GParted from the software center, and there was an extension called ntfsprogs that came with it.



During my search for a solution to the problem, I uninstalled GParted (as that was one of the apps I installed just before the problem). But that did not solve the problem.



I came across an app called 'NTFS Configuration Tool'. When I installed this, it said that the ntfsprogs extension needed to be removed (so I guess uninstalling GPARTED, didn't remove the ntfsprog extension).



I launched the NTFS Configuration Tool and now I have write access to NTFS drives. Unfortunately, I didn't check if I had write permission prior to launching the NTFS Configuration Tool, so I'm not sure whether the NTFS Configuration Tool, or the un-installation of ntfsprog gave me back NTFS write permission.



Hopefully if another newbee encounters this problem, they'll come across this page and know what to do.







permissions ntfs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 5 '12 at 19:51







mloman

















asked Jan 5 '12 at 19:22









mlomanmloman

3472923




3472923












  • Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

    – James T Snell
    Jan 5 '12 at 19:28












  • if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

    – Thomas Ward
    Oct 26 '12 at 14:38











  • ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

    – dearN
    Oct 26 '12 at 14:39

















  • Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

    – James T Snell
    Jan 5 '12 at 19:28












  • if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

    – Thomas Ward
    Oct 26 '12 at 14:38











  • ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

    – dearN
    Oct 26 '12 at 14:39
















Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

– James T Snell
Jan 5 '12 at 19:28






Reinstalling may well just lead to the same end. Perhaps a recent update changed the default behavior for NTFS writes? Do you have NTFS-3G installed? What does your /etc/mtab say regarding your NTFS volumes?

– James T Snell
Jan 5 '12 at 19:28














if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

– Thomas Ward
Oct 26 '12 at 14:38





if you have an answer that you came upon answer your own post with your update, rather than just editing your question.

– Thomas Ward
Oct 26 '12 at 14:38













ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

– dearN
Oct 26 '12 at 14:39





ntfsfix and chown may be your friends, read my answer below. I had the same issue a couple of time already.

– dearN
Oct 26 '12 at 14:39










8 Answers
8






active

oldest

votes


















4














You need to mount the NTFS drive with the UTF-8 options. If you look up on Google how to mount the ntfs-3g filesystem , you'll see that you need these options:



defaults,locale=en_US.UTF-8


The symptom that you will get if your missing the UTF-8 option is that you can read to the drive but you cannot write. For, example, you would lose the ability to move a file off of the drive.



Note: a link to more info is here . The UTF-8 option is mentioned here .






share|improve this answer
































    3














    Running



    sudo apt-get purge ntfs-3g


    and then



    sudo apt-get install ntfs-3g


    worked for me.



    I guess it's because initrd.img was not generated with the ntfs-3g module while kernel update took place. Just a guess because I didn't have ntfsprogs Install ntfsprogs installed. I had only ntfs-3g Install ntfs-3g which didn't work.






    share|improve this answer
































      2














      For ntfs you should use the permissions option.



      Using /dev/sda1 as an example (you can use UUID in fstab as well), mounted at /media/ntfs (adjust your partition / mountpoint / fstab entry to your needs).



      Edit /etc/fstab



      # graphical
      gksu gedit /etc/fstab

      # command line
      sudo -e /etc/fstab


      Add/Edit your entry to look similar this line



      /dev/sda1 /media/ntfs ntfs-3g locale=en_US.UTF-8,permissions 0 0


      Make a mount point (if needed)



      [[ -d /media/ntfs ]] || sudo mkdir /media/ntfs


      Unmount and re-mount the ntfs partition



      sudo umount /dev/sda1
      sudo mount /media/ntfs


      Now you can manage the ownership and permissions with chown and chmod



      sudo chown -R your_user:your_user /media/ntfs
      chmod -R ug+rw /media/ntfs


      If, after all that, the partition is not working as expected, check it from windows.






      share|improve this answer























      • I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

        – djangofan
        Jan 30 '12 at 23:28











      • Works fine for me

        – Mazhar Ahmed
        Oct 18 '17 at 9:10











      • See this if the mount commands get overruled as read-only still due to Windows hibernation...

        – Nae
        Dec 29 '18 at 13:22



















      1














      I installed GParted with ntsfprog as add-on a month back and I lost the write permission (I just find out).



      So, I un-installed ntfsprogs only, and then installed ntfs-3g and that solved the problem.






      share|improve this answer
































        1














        If you're dual-booting, try



        sudo ntfsfix /dev/sda1


        and replace /dev/sda1 with the partition name (e.g. /dev/sda4 [for the fourth partition on the primary hard drive] or /dev/sdb [for a single partitioned secondary drive]).






        share|improve this answer
































          0














          Thank goodness I found this post. I was having a similar problem where i could make a folder or file, but I could not change the file or folder except delete it. It gets really annoying when you must do chmod on every new file or folder.



          All I did was:



          sudo apt-get purge ntfsprogs
          sudo apt-get purge ntfs-3g
          sudo apt-get install ntfs-3g


          The purge option is a full uninstall. After that, I just grabbed a fresh install. Simple, and it works.






          share|improve this answer
































            0














            Same thing happened to me after I installed GParted few days ago. So I did some research in the Internet and found that its because an add-on called "ntfsprogs"(older ntfs utility) overwritten the add-on "ntfs-3g"(latest ntfs version).



            I can't understand the whole thing, but those two add-ons are in a conflict.
            So all you need to do is remove "ntfsprogs" by using Software Center.



            1. Type GParted and unmark "Tools for doing neat things in NTFS partitions from linux(ntfsprogs)" or remove GParted completely.


            2. Type "ntfs" in Ubuntu Software center. First option you get is "NTFS Configuration Tools".


            3. Install it and bingo. Now you got your permissions back.






            share|improve this answer
































              0














              I had this recurring problem for months. I was under the impression that this was specifi to Toshiba drive.



              Anyway, this is how I dealt with it successfully:



              1. If your drive is not mounting and giving you an exit 13 error, since you have ntfsfix now, run ntfsfix -b /dev/sdbx where you replace sdbx with your hard drive/NTFS drive. You can get your drive name from sudo fdisk -l. You'd be able to identiy your drive from there.

              For instance, for me, sudo fdisk -l returns:



              Disk /dev/sda: 500.1 GB, 500107862016 bytes
              255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
              Units = sectors of 1 * 512 = 512 bytes
              Sector size (logical/physical): 512 bytes / 512 bytes
              I/O size (minimum/optimal): 512 bytes / 512 bytes
              Disk identifier: 0x000586fb

              Device Boot Start End Blocks Id System
              /dev/sda1 * 2148 961320312 480659082+ 83 Linux
              /dev/sda2 961320313 976773167 7726427+ 5 Extended
              /dev/sda5 961320314 976773167 7726427 83 Linux

              WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


              Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
              255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
              Units = sectors of 1 * 512 = 512 bytes
              Sector size (logical/physical): 512 bytes / 512 bytes
              I/O size (minimum/optimal): 512 bytes / 512 bytes
              Disk identifier: 0xcfd88605

              Device Boot Start End Blocks Id System
              /dev/sdb1 1 1953525167 976762583+ ee GPT


              Here, /dev/sdb1 is my external hard drive.



              1. After this you might need to run chown -R username:username /media/path/to/hardrive to give yourself read+write rights (recursively to all folders and subfolder).

              I've had to do this twice which probably suggests that my hard drive is dying! Have you backed your data up?






              share|improve this answer





















                protected by Community 2 days ago



                Thank you for your interest in this question.
                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                Would you like to answer one of these unanswered questions instead?














                8 Answers
                8






                active

                oldest

                votes








                8 Answers
                8






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                4














                You need to mount the NTFS drive with the UTF-8 options. If you look up on Google how to mount the ntfs-3g filesystem , you'll see that you need these options:



                defaults,locale=en_US.UTF-8


                The symptom that you will get if your missing the UTF-8 option is that you can read to the drive but you cannot write. For, example, you would lose the ability to move a file off of the drive.



                Note: a link to more info is here . The UTF-8 option is mentioned here .






                share|improve this answer





























                  4














                  You need to mount the NTFS drive with the UTF-8 options. If you look up on Google how to mount the ntfs-3g filesystem , you'll see that you need these options:



                  defaults,locale=en_US.UTF-8


                  The symptom that you will get if your missing the UTF-8 option is that you can read to the drive but you cannot write. For, example, you would lose the ability to move a file off of the drive.



                  Note: a link to more info is here . The UTF-8 option is mentioned here .






                  share|improve this answer



























                    4












                    4








                    4







                    You need to mount the NTFS drive with the UTF-8 options. If you look up on Google how to mount the ntfs-3g filesystem , you'll see that you need these options:



                    defaults,locale=en_US.UTF-8


                    The symptom that you will get if your missing the UTF-8 option is that you can read to the drive but you cannot write. For, example, you would lose the ability to move a file off of the drive.



                    Note: a link to more info is here . The UTF-8 option is mentioned here .






                    share|improve this answer















                    You need to mount the NTFS drive with the UTF-8 options. If you look up on Google how to mount the ntfs-3g filesystem , you'll see that you need these options:



                    defaults,locale=en_US.UTF-8


                    The symptom that you will get if your missing the UTF-8 option is that you can read to the drive but you cannot write. For, example, you would lose the ability to move a file off of the drive.



                    Note: a link to more info is here . The UTF-8 option is mentioned here .







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Jan 30 '12 at 23:25

























                    answered Jan 5 '12 at 19:28









                    djangofandjangofan

                    1,61121827




                    1,61121827























                        3














                        Running



                        sudo apt-get purge ntfs-3g


                        and then



                        sudo apt-get install ntfs-3g


                        worked for me.



                        I guess it's because initrd.img was not generated with the ntfs-3g module while kernel update took place. Just a guess because I didn't have ntfsprogs Install ntfsprogs installed. I had only ntfs-3g Install ntfs-3g which didn't work.






                        share|improve this answer





























                          3














                          Running



                          sudo apt-get purge ntfs-3g


                          and then



                          sudo apt-get install ntfs-3g


                          worked for me.



                          I guess it's because initrd.img was not generated with the ntfs-3g module while kernel update took place. Just a guess because I didn't have ntfsprogs Install ntfsprogs installed. I had only ntfs-3g Install ntfs-3g which didn't work.






                          share|improve this answer



























                            3












                            3








                            3







                            Running



                            sudo apt-get purge ntfs-3g


                            and then



                            sudo apt-get install ntfs-3g


                            worked for me.



                            I guess it's because initrd.img was not generated with the ntfs-3g module while kernel update took place. Just a guess because I didn't have ntfsprogs Install ntfsprogs installed. I had only ntfs-3g Install ntfs-3g which didn't work.






                            share|improve this answer















                            Running



                            sudo apt-get purge ntfs-3g


                            and then



                            sudo apt-get install ntfs-3g


                            worked for me.



                            I guess it's because initrd.img was not generated with the ntfs-3g module while kernel update took place. Just a guess because I didn't have ntfsprogs Install ntfsprogs installed. I had only ntfs-3g Install ntfs-3g which didn't work.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Mar 11 '17 at 19:03









                            Community

                            1




                            1










                            answered Jul 6 '13 at 7:58









                            user171297user171297

                            412




                            412





















                                2














                                For ntfs you should use the permissions option.



                                Using /dev/sda1 as an example (you can use UUID in fstab as well), mounted at /media/ntfs (adjust your partition / mountpoint / fstab entry to your needs).



                                Edit /etc/fstab



                                # graphical
                                gksu gedit /etc/fstab

                                # command line
                                sudo -e /etc/fstab


                                Add/Edit your entry to look similar this line



                                /dev/sda1 /media/ntfs ntfs-3g locale=en_US.UTF-8,permissions 0 0


                                Make a mount point (if needed)



                                [[ -d /media/ntfs ]] || sudo mkdir /media/ntfs


                                Unmount and re-mount the ntfs partition



                                sudo umount /dev/sda1
                                sudo mount /media/ntfs


                                Now you can manage the ownership and permissions with chown and chmod



                                sudo chown -R your_user:your_user /media/ntfs
                                chmod -R ug+rw /media/ntfs


                                If, after all that, the partition is not working as expected, check it from windows.






                                share|improve this answer























                                • I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                  – djangofan
                                  Jan 30 '12 at 23:28











                                • Works fine for me

                                  – Mazhar Ahmed
                                  Oct 18 '17 at 9:10











                                • See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                  – Nae
                                  Dec 29 '18 at 13:22
















                                2














                                For ntfs you should use the permissions option.



                                Using /dev/sda1 as an example (you can use UUID in fstab as well), mounted at /media/ntfs (adjust your partition / mountpoint / fstab entry to your needs).



                                Edit /etc/fstab



                                # graphical
                                gksu gedit /etc/fstab

                                # command line
                                sudo -e /etc/fstab


                                Add/Edit your entry to look similar this line



                                /dev/sda1 /media/ntfs ntfs-3g locale=en_US.UTF-8,permissions 0 0


                                Make a mount point (if needed)



                                [[ -d /media/ntfs ]] || sudo mkdir /media/ntfs


                                Unmount and re-mount the ntfs partition



                                sudo umount /dev/sda1
                                sudo mount /media/ntfs


                                Now you can manage the ownership and permissions with chown and chmod



                                sudo chown -R your_user:your_user /media/ntfs
                                chmod -R ug+rw /media/ntfs


                                If, after all that, the partition is not working as expected, check it from windows.






                                share|improve this answer























                                • I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                  – djangofan
                                  Jan 30 '12 at 23:28











                                • Works fine for me

                                  – Mazhar Ahmed
                                  Oct 18 '17 at 9:10











                                • See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                  – Nae
                                  Dec 29 '18 at 13:22














                                2












                                2








                                2







                                For ntfs you should use the permissions option.



                                Using /dev/sda1 as an example (you can use UUID in fstab as well), mounted at /media/ntfs (adjust your partition / mountpoint / fstab entry to your needs).



                                Edit /etc/fstab



                                # graphical
                                gksu gedit /etc/fstab

                                # command line
                                sudo -e /etc/fstab


                                Add/Edit your entry to look similar this line



                                /dev/sda1 /media/ntfs ntfs-3g locale=en_US.UTF-8,permissions 0 0


                                Make a mount point (if needed)



                                [[ -d /media/ntfs ]] || sudo mkdir /media/ntfs


                                Unmount and re-mount the ntfs partition



                                sudo umount /dev/sda1
                                sudo mount /media/ntfs


                                Now you can manage the ownership and permissions with chown and chmod



                                sudo chown -R your_user:your_user /media/ntfs
                                chmod -R ug+rw /media/ntfs


                                If, after all that, the partition is not working as expected, check it from windows.






                                share|improve this answer













                                For ntfs you should use the permissions option.



                                Using /dev/sda1 as an example (you can use UUID in fstab as well), mounted at /media/ntfs (adjust your partition / mountpoint / fstab entry to your needs).



                                Edit /etc/fstab



                                # graphical
                                gksu gedit /etc/fstab

                                # command line
                                sudo -e /etc/fstab


                                Add/Edit your entry to look similar this line



                                /dev/sda1 /media/ntfs ntfs-3g locale=en_US.UTF-8,permissions 0 0


                                Make a mount point (if needed)



                                [[ -d /media/ntfs ]] || sudo mkdir /media/ntfs


                                Unmount and re-mount the ntfs partition



                                sudo umount /dev/sda1
                                sudo mount /media/ntfs


                                Now you can manage the ownership and permissions with chown and chmod



                                sudo chown -R your_user:your_user /media/ntfs
                                chmod -R ug+rw /media/ntfs


                                If, after all that, the partition is not working as expected, check it from windows.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Jan 5 '12 at 19:51









                                PantherPanther

                                80.2k14159259




                                80.2k14159259












                                • I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                  – djangofan
                                  Jan 30 '12 at 23:28











                                • Works fine for me

                                  – Mazhar Ahmed
                                  Oct 18 '17 at 9:10











                                • See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                  – Nae
                                  Dec 29 '18 at 13:22


















                                • I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                  – djangofan
                                  Jan 30 '12 at 23:28











                                • Works fine for me

                                  – Mazhar Ahmed
                                  Oct 18 '17 at 9:10











                                • See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                  – Nae
                                  Dec 29 '18 at 13:22

















                                I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                – djangofan
                                Jan 30 '12 at 23:28





                                I didn't know about the permission option and/or the inherit option. Very useful for the future also. ;-)

                                – djangofan
                                Jan 30 '12 at 23:28













                                Works fine for me

                                – Mazhar Ahmed
                                Oct 18 '17 at 9:10





                                Works fine for me

                                – Mazhar Ahmed
                                Oct 18 '17 at 9:10













                                See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                – Nae
                                Dec 29 '18 at 13:22






                                See this if the mount commands get overruled as read-only still due to Windows hibernation...

                                – Nae
                                Dec 29 '18 at 13:22












                                1














                                I installed GParted with ntsfprog as add-on a month back and I lost the write permission (I just find out).



                                So, I un-installed ntfsprogs only, and then installed ntfs-3g and that solved the problem.






                                share|improve this answer





























                                  1














                                  I installed GParted with ntsfprog as add-on a month back and I lost the write permission (I just find out).



                                  So, I un-installed ntfsprogs only, and then installed ntfs-3g and that solved the problem.






                                  share|improve this answer



























                                    1












                                    1








                                    1







                                    I installed GParted with ntsfprog as add-on a month back and I lost the write permission (I just find out).



                                    So, I un-installed ntfsprogs only, and then installed ntfs-3g and that solved the problem.






                                    share|improve this answer















                                    I installed GParted with ntsfprog as add-on a month back and I lost the write permission (I just find out).



                                    So, I un-installed ntfsprogs only, and then installed ntfs-3g and that solved the problem.







                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Sep 19 '12 at 12:36









                                    Peachy

                                    5,08672843




                                    5,08672843










                                    answered Feb 3 '12 at 16:32









                                    Francisco IbáñezFrancisco Ibáñez

                                    611




                                    611





















                                        1














                                        If you're dual-booting, try



                                        sudo ntfsfix /dev/sda1


                                        and replace /dev/sda1 with the partition name (e.g. /dev/sda4 [for the fourth partition on the primary hard drive] or /dev/sdb [for a single partitioned secondary drive]).






                                        share|improve this answer





























                                          1














                                          If you're dual-booting, try



                                          sudo ntfsfix /dev/sda1


                                          and replace /dev/sda1 with the partition name (e.g. /dev/sda4 [for the fourth partition on the primary hard drive] or /dev/sdb [for a single partitioned secondary drive]).






                                          share|improve this answer



























                                            1












                                            1








                                            1







                                            If you're dual-booting, try



                                            sudo ntfsfix /dev/sda1


                                            and replace /dev/sda1 with the partition name (e.g. /dev/sda4 [for the fourth partition on the primary hard drive] or /dev/sdb [for a single partitioned secondary drive]).






                                            share|improve this answer















                                            If you're dual-booting, try



                                            sudo ntfsfix /dev/sda1


                                            and replace /dev/sda1 with the partition name (e.g. /dev/sda4 [for the fourth partition on the primary hard drive] or /dev/sdb [for a single partitioned secondary drive]).







                                            share|improve this answer














                                            share|improve this answer



                                            share|improve this answer








                                            edited Mar 18 at 5:29









                                            zx485

                                            1,47131315




                                            1,47131315










                                            answered Mar 17 at 16:53









                                            Harry SHarry S

                                            111




                                            111





















                                                0














                                                Thank goodness I found this post. I was having a similar problem where i could make a folder or file, but I could not change the file or folder except delete it. It gets really annoying when you must do chmod on every new file or folder.



                                                All I did was:



                                                sudo apt-get purge ntfsprogs
                                                sudo apt-get purge ntfs-3g
                                                sudo apt-get install ntfs-3g


                                                The purge option is a full uninstall. After that, I just grabbed a fresh install. Simple, and it works.






                                                share|improve this answer





























                                                  0














                                                  Thank goodness I found this post. I was having a similar problem where i could make a folder or file, but I could not change the file or folder except delete it. It gets really annoying when you must do chmod on every new file or folder.



                                                  All I did was:



                                                  sudo apt-get purge ntfsprogs
                                                  sudo apt-get purge ntfs-3g
                                                  sudo apt-get install ntfs-3g


                                                  The purge option is a full uninstall. After that, I just grabbed a fresh install. Simple, and it works.






                                                  share|improve this answer



























                                                    0












                                                    0








                                                    0







                                                    Thank goodness I found this post. I was having a similar problem where i could make a folder or file, but I could not change the file or folder except delete it. It gets really annoying when you must do chmod on every new file or folder.



                                                    All I did was:



                                                    sudo apt-get purge ntfsprogs
                                                    sudo apt-get purge ntfs-3g
                                                    sudo apt-get install ntfs-3g


                                                    The purge option is a full uninstall. After that, I just grabbed a fresh install. Simple, and it works.






                                                    share|improve this answer















                                                    Thank goodness I found this post. I was having a similar problem where i could make a folder or file, but I could not change the file or folder except delete it. It gets really annoying when you must do chmod on every new file or folder.



                                                    All I did was:



                                                    sudo apt-get purge ntfsprogs
                                                    sudo apt-get purge ntfs-3g
                                                    sudo apt-get install ntfs-3g


                                                    The purge option is a full uninstall. After that, I just grabbed a fresh install. Simple, and it works.







                                                    share|improve this answer














                                                    share|improve this answer



                                                    share|improve this answer








                                                    edited Jul 8 '12 at 14:08









                                                    Eliah Kagan

                                                    83.3k22229369




                                                    83.3k22229369










                                                    answered Jul 8 '12 at 4:53









                                                    alex harperalex harper

                                                    11




                                                    11





















                                                        0














                                                        Same thing happened to me after I installed GParted few days ago. So I did some research in the Internet and found that its because an add-on called "ntfsprogs"(older ntfs utility) overwritten the add-on "ntfs-3g"(latest ntfs version).



                                                        I can't understand the whole thing, but those two add-ons are in a conflict.
                                                        So all you need to do is remove "ntfsprogs" by using Software Center.



                                                        1. Type GParted and unmark "Tools for doing neat things in NTFS partitions from linux(ntfsprogs)" or remove GParted completely.


                                                        2. Type "ntfs" in Ubuntu Software center. First option you get is "NTFS Configuration Tools".


                                                        3. Install it and bingo. Now you got your permissions back.






                                                        share|improve this answer





























                                                          0














                                                          Same thing happened to me after I installed GParted few days ago. So I did some research in the Internet and found that its because an add-on called "ntfsprogs"(older ntfs utility) overwritten the add-on "ntfs-3g"(latest ntfs version).



                                                          I can't understand the whole thing, but those two add-ons are in a conflict.
                                                          So all you need to do is remove "ntfsprogs" by using Software Center.



                                                          1. Type GParted and unmark "Tools for doing neat things in NTFS partitions from linux(ntfsprogs)" or remove GParted completely.


                                                          2. Type "ntfs" in Ubuntu Software center. First option you get is "NTFS Configuration Tools".


                                                          3. Install it and bingo. Now you got your permissions back.






                                                          share|improve this answer



























                                                            0












                                                            0








                                                            0







                                                            Same thing happened to me after I installed GParted few days ago. So I did some research in the Internet and found that its because an add-on called "ntfsprogs"(older ntfs utility) overwritten the add-on "ntfs-3g"(latest ntfs version).



                                                            I can't understand the whole thing, but those two add-ons are in a conflict.
                                                            So all you need to do is remove "ntfsprogs" by using Software Center.



                                                            1. Type GParted and unmark "Tools for doing neat things in NTFS partitions from linux(ntfsprogs)" or remove GParted completely.


                                                            2. Type "ntfs" in Ubuntu Software center. First option you get is "NTFS Configuration Tools".


                                                            3. Install it and bingo. Now you got your permissions back.






                                                            share|improve this answer















                                                            Same thing happened to me after I installed GParted few days ago. So I did some research in the Internet and found that its because an add-on called "ntfsprogs"(older ntfs utility) overwritten the add-on "ntfs-3g"(latest ntfs version).



                                                            I can't understand the whole thing, but those two add-ons are in a conflict.
                                                            So all you need to do is remove "ntfsprogs" by using Software Center.



                                                            1. Type GParted and unmark "Tools for doing neat things in NTFS partitions from linux(ntfsprogs)" or remove GParted completely.


                                                            2. Type "ntfs" in Ubuntu Software center. First option you get is "NTFS Configuration Tools".


                                                            3. Install it and bingo. Now you got your permissions back.







                                                            share|improve this answer














                                                            share|improve this answer



                                                            share|improve this answer








                                                            edited Oct 26 '12 at 14:18









                                                            Peachy

                                                            5,08672843




                                                            5,08672843










                                                            answered May 2 '12 at 5:45









                                                            NadeeraNadeera

                                                            1




                                                            1





















                                                                0














                                                                I had this recurring problem for months. I was under the impression that this was specifi to Toshiba drive.



                                                                Anyway, this is how I dealt with it successfully:



                                                                1. If your drive is not mounting and giving you an exit 13 error, since you have ntfsfix now, run ntfsfix -b /dev/sdbx where you replace sdbx with your hard drive/NTFS drive. You can get your drive name from sudo fdisk -l. You'd be able to identiy your drive from there.

                                                                For instance, for me, sudo fdisk -l returns:



                                                                Disk /dev/sda: 500.1 GB, 500107862016 bytes
                                                                255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
                                                                Units = sectors of 1 * 512 = 512 bytes
                                                                Sector size (logical/physical): 512 bytes / 512 bytes
                                                                I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                Disk identifier: 0x000586fb

                                                                Device Boot Start End Blocks Id System
                                                                /dev/sda1 * 2148 961320312 480659082+ 83 Linux
                                                                /dev/sda2 961320313 976773167 7726427+ 5 Extended
                                                                /dev/sda5 961320314 976773167 7726427 83 Linux

                                                                WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


                                                                Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
                                                                255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
                                                                Units = sectors of 1 * 512 = 512 bytes
                                                                Sector size (logical/physical): 512 bytes / 512 bytes
                                                                I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                Disk identifier: 0xcfd88605

                                                                Device Boot Start End Blocks Id System
                                                                /dev/sdb1 1 1953525167 976762583+ ee GPT


                                                                Here, /dev/sdb1 is my external hard drive.



                                                                1. After this you might need to run chown -R username:username /media/path/to/hardrive to give yourself read+write rights (recursively to all folders and subfolder).

                                                                I've had to do this twice which probably suggests that my hard drive is dying! Have you backed your data up?






                                                                share|improve this answer



























                                                                  0














                                                                  I had this recurring problem for months. I was under the impression that this was specifi to Toshiba drive.



                                                                  Anyway, this is how I dealt with it successfully:



                                                                  1. If your drive is not mounting and giving you an exit 13 error, since you have ntfsfix now, run ntfsfix -b /dev/sdbx where you replace sdbx with your hard drive/NTFS drive. You can get your drive name from sudo fdisk -l. You'd be able to identiy your drive from there.

                                                                  For instance, for me, sudo fdisk -l returns:



                                                                  Disk /dev/sda: 500.1 GB, 500107862016 bytes
                                                                  255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
                                                                  Units = sectors of 1 * 512 = 512 bytes
                                                                  Sector size (logical/physical): 512 bytes / 512 bytes
                                                                  I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                  Disk identifier: 0x000586fb

                                                                  Device Boot Start End Blocks Id System
                                                                  /dev/sda1 * 2148 961320312 480659082+ 83 Linux
                                                                  /dev/sda2 961320313 976773167 7726427+ 5 Extended
                                                                  /dev/sda5 961320314 976773167 7726427 83 Linux

                                                                  WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


                                                                  Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
                                                                  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
                                                                  Units = sectors of 1 * 512 = 512 bytes
                                                                  Sector size (logical/physical): 512 bytes / 512 bytes
                                                                  I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                  Disk identifier: 0xcfd88605

                                                                  Device Boot Start End Blocks Id System
                                                                  /dev/sdb1 1 1953525167 976762583+ ee GPT


                                                                  Here, /dev/sdb1 is my external hard drive.



                                                                  1. After this you might need to run chown -R username:username /media/path/to/hardrive to give yourself read+write rights (recursively to all folders and subfolder).

                                                                  I've had to do this twice which probably suggests that my hard drive is dying! Have you backed your data up?






                                                                  share|improve this answer

























                                                                    0












                                                                    0








                                                                    0







                                                                    I had this recurring problem for months. I was under the impression that this was specifi to Toshiba drive.



                                                                    Anyway, this is how I dealt with it successfully:



                                                                    1. If your drive is not mounting and giving you an exit 13 error, since you have ntfsfix now, run ntfsfix -b /dev/sdbx where you replace sdbx with your hard drive/NTFS drive. You can get your drive name from sudo fdisk -l. You'd be able to identiy your drive from there.

                                                                    For instance, for me, sudo fdisk -l returns:



                                                                    Disk /dev/sda: 500.1 GB, 500107862016 bytes
                                                                    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
                                                                    Units = sectors of 1 * 512 = 512 bytes
                                                                    Sector size (logical/physical): 512 bytes / 512 bytes
                                                                    I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                    Disk identifier: 0x000586fb

                                                                    Device Boot Start End Blocks Id System
                                                                    /dev/sda1 * 2148 961320312 480659082+ 83 Linux
                                                                    /dev/sda2 961320313 976773167 7726427+ 5 Extended
                                                                    /dev/sda5 961320314 976773167 7726427 83 Linux

                                                                    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


                                                                    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
                                                                    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
                                                                    Units = sectors of 1 * 512 = 512 bytes
                                                                    Sector size (logical/physical): 512 bytes / 512 bytes
                                                                    I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                    Disk identifier: 0xcfd88605

                                                                    Device Boot Start End Blocks Id System
                                                                    /dev/sdb1 1 1953525167 976762583+ ee GPT


                                                                    Here, /dev/sdb1 is my external hard drive.



                                                                    1. After this you might need to run chown -R username:username /media/path/to/hardrive to give yourself read+write rights (recursively to all folders and subfolder).

                                                                    I've had to do this twice which probably suggests that my hard drive is dying! Have you backed your data up?






                                                                    share|improve this answer













                                                                    I had this recurring problem for months. I was under the impression that this was specifi to Toshiba drive.



                                                                    Anyway, this is how I dealt with it successfully:



                                                                    1. If your drive is not mounting and giving you an exit 13 error, since you have ntfsfix now, run ntfsfix -b /dev/sdbx where you replace sdbx with your hard drive/NTFS drive. You can get your drive name from sudo fdisk -l. You'd be able to identiy your drive from there.

                                                                    For instance, for me, sudo fdisk -l returns:



                                                                    Disk /dev/sda: 500.1 GB, 500107862016 bytes
                                                                    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
                                                                    Units = sectors of 1 * 512 = 512 bytes
                                                                    Sector size (logical/physical): 512 bytes / 512 bytes
                                                                    I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                    Disk identifier: 0x000586fb

                                                                    Device Boot Start End Blocks Id System
                                                                    /dev/sda1 * 2148 961320312 480659082+ 83 Linux
                                                                    /dev/sda2 961320313 976773167 7726427+ 5 Extended
                                                                    /dev/sda5 961320314 976773167 7726427 83 Linux

                                                                    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


                                                                    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
                                                                    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
                                                                    Units = sectors of 1 * 512 = 512 bytes
                                                                    Sector size (logical/physical): 512 bytes / 512 bytes
                                                                    I/O size (minimum/optimal): 512 bytes / 512 bytes
                                                                    Disk identifier: 0xcfd88605

                                                                    Device Boot Start End Blocks Id System
                                                                    /dev/sdb1 1 1953525167 976762583+ ee GPT


                                                                    Here, /dev/sdb1 is my external hard drive.



                                                                    1. After this you might need to run chown -R username:username /media/path/to/hardrive to give yourself read+write rights (recursively to all folders and subfolder).

                                                                    I've had to do this twice which probably suggests that my hard drive is dying! Have you backed your data up?







                                                                    share|improve this answer












                                                                    share|improve this answer



                                                                    share|improve this answer










                                                                    answered Oct 26 '12 at 14:35









                                                                    dearNdearN

                                                                    1,02661528




                                                                    1,02661528















                                                                        protected by Community 2 days ago



                                                                        Thank you for your interest in this question.
                                                                        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                                        Would you like to answer one of these unanswered questions instead?



                                                                        Popular posts from this blog

                                                                        Tamil (spriik) Luke uk diar | Nawigatjuun

                                                                        Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                                                                        Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?