read and write permission for FAT32 partition in Ubuntu
This is a strange problem. I have the following partition table
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 5737 45978624 7 HPFS/NTFS
/dev/sda3 5738 10600 39062047+ 83 Linux
/dev/sda4 10601 19457 71143852+ 5 Extended
/dev/sda5 10601 11208 4883728+ 82 Linux swap / Solaris
/dev/sda6 11209 15033 30720000 b W95 FAT32
/dev/sda7 15033 19457 35537920 7 HPFS/NTFS
I dual boot Win7 (sda2) and Ubuntu (sda3) and wanted to use the FAT32 partition to share files across two OS's.
I followed some online tutorial and have done these:
sudo mkdir /media/FAT32
sudo chmod 777 /media/FAT32
sudo mount /dev/sda6/ /media/FAT32
after I mounted the file, I can only read but not be able to write to it.
I checked the file permission, it becomes:
drwxr-xr-x
but after I unmounted the it then becomes
drwxrwxrwx
and I can read and write to it.
I don't know where I've down wrong.
ubuntu mount fat32
migrated from stackoverflow.com Dec 7 '09 at 12:46
This question came from our site for professional and enthusiast programmers.
add a comment |
This is a strange problem. I have the following partition table
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 5737 45978624 7 HPFS/NTFS
/dev/sda3 5738 10600 39062047+ 83 Linux
/dev/sda4 10601 19457 71143852+ 5 Extended
/dev/sda5 10601 11208 4883728+ 82 Linux swap / Solaris
/dev/sda6 11209 15033 30720000 b W95 FAT32
/dev/sda7 15033 19457 35537920 7 HPFS/NTFS
I dual boot Win7 (sda2) and Ubuntu (sda3) and wanted to use the FAT32 partition to share files across two OS's.
I followed some online tutorial and have done these:
sudo mkdir /media/FAT32
sudo chmod 777 /media/FAT32
sudo mount /dev/sda6/ /media/FAT32
after I mounted the file, I can only read but not be able to write to it.
I checked the file permission, it becomes:
drwxr-xr-x
but after I unmounted the it then becomes
drwxrwxrwx
and I can read and write to it.
I don't know where I've down wrong.
ubuntu mount fat32
migrated from stackoverflow.com Dec 7 '09 at 12:46
This question came from our site for professional and enthusiast programmers.
add a comment |
This is a strange problem. I have the following partition table
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 5737 45978624 7 HPFS/NTFS
/dev/sda3 5738 10600 39062047+ 83 Linux
/dev/sda4 10601 19457 71143852+ 5 Extended
/dev/sda5 10601 11208 4883728+ 82 Linux swap / Solaris
/dev/sda6 11209 15033 30720000 b W95 FAT32
/dev/sda7 15033 19457 35537920 7 HPFS/NTFS
I dual boot Win7 (sda2) and Ubuntu (sda3) and wanted to use the FAT32 partition to share files across two OS's.
I followed some online tutorial and have done these:
sudo mkdir /media/FAT32
sudo chmod 777 /media/FAT32
sudo mount /dev/sda6/ /media/FAT32
after I mounted the file, I can only read but not be able to write to it.
I checked the file permission, it becomes:
drwxr-xr-x
but after I unmounted the it then becomes
drwxrwxrwx
and I can read and write to it.
I don't know where I've down wrong.
ubuntu mount fat32
This is a strange problem. I have the following partition table
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 5737 45978624 7 HPFS/NTFS
/dev/sda3 5738 10600 39062047+ 83 Linux
/dev/sda4 10601 19457 71143852+ 5 Extended
/dev/sda5 10601 11208 4883728+ 82 Linux swap / Solaris
/dev/sda6 11209 15033 30720000 b W95 FAT32
/dev/sda7 15033 19457 35537920 7 HPFS/NTFS
I dual boot Win7 (sda2) and Ubuntu (sda3) and wanted to use the FAT32 partition to share files across two OS's.
I followed some online tutorial and have done these:
sudo mkdir /media/FAT32
sudo chmod 777 /media/FAT32
sudo mount /dev/sda6/ /media/FAT32
after I mounted the file, I can only read but not be able to write to it.
I checked the file permission, it becomes:
drwxr-xr-x
but after I unmounted the it then becomes
drwxrwxrwx
and I can read and write to it.
I don't know where I've down wrong.
ubuntu mount fat32
ubuntu mount fat32
edited Jan 2 at 15:36
Etherealone
164113
164113
asked Dec 5 '09 at 15:36
DeanDean
200137
200137
migrated from stackoverflow.com Dec 7 '09 at 12:46
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Dec 7 '09 at 12:46
This question came from our site for professional and enthusiast programmers.
add a comment |
add a comment |
9 Answers
9
active
oldest
votes
Try mounting with rw and specify the type:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx
where uid and gid are that of your user account.
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
andauto
are options for thefstab
entry; they aren't very useful on the commandline.
– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
add a comment |
For FAT filesystems, read/write availability is governed by the mount options.
Consult the manpage for mount and read about uid and gid mount options for FAT.
add a comment |
Have you tried writing to the files with a sudo
command? That should work with your current setup.
To get file writes for your normal user working, you need to use the uid
and gid
options to mount
, to set the owner of files on the partition to your current userID. You probably also want either umask
or dmask
and fmask
options.
Your mount
command would look like this:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o uid=1000,gid=1000,umask=022
# assuming your user's UID is 1000, GID is 1000
# umask=022 sets permission mode 755 for all files on the partition
add a comment |
You have the wrong order on the commands you want:
sudo mkdir /media/FAT32
sudo mount /dev/sda6 /media/FAT32
sudo chmod 777 /media/FAT32
What is happening is that /media/FAT32 represents different directories before and after the mount. Before it's the directory you made, and which you chmod'ed 777. After, it's the root directory of the filesystem in /dev/sda6.
add a comment |
If you simply forget about command line and mount with Nautilus, it should set it as you want.
From the terminal, the permissions of the folder before mounting doesn't matter. It's the mount options that count. Try:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx,umask=133,dmask=022
This will set files to rw-r--r--
and folders to rwxr-xr-x
.
If you want other user/group and permissions, for instance to copy files from fat32 to the ext4 partition with the desired attributes, better consult the mount
manpage. Roughly you put on umask
the opposite of what you would put on chmod
.
add a comment |
Sometimes I lost the windows disk from Linux and I solved using mount with "-o force", as this example:
sudo mount -t ntfs-3g /dev/sda1 /media/win -o force
In your case, being FAT32 you should read about, but my be this tip help. Anyway, try at your own risk!
add a comment |
I had exactly the same problem and the only thing that actually worked is:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,umask=0000
See also that answer
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you trychmod 777 /media/FAT32
?
– lauhub
Jan 6 '15 at 14:31
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
add a comment |
Without manually mount, an fstab line do the trick,
UUID=1DD9-0D44 /media/exthd/TERABYTE_G vfat rw,noatime,uid=1000,gid=1000,user 0 0
(uid,gid are of your user, /media/exthd/TERABYTE_G must be pre-created)
but note, mount -a seems not applying properly to test the new fstab line, so a full reboot helps.
add a comment |
Very important repair/check the disk under windows before using it on linux, by default fat/ntfs drivers disable write if they find errors on the disk
chkdsk d: /f
Then
sudo mount -t vfat /dev/sdc1 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
as motioned before
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f79813%2fread-and-write-permission-for-fat32-partition-in-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try mounting with rw and specify the type:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx
where uid and gid are that of your user account.
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
andauto
are options for thefstab
entry; they aren't very useful on the commandline.
– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
add a comment |
Try mounting with rw and specify the type:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx
where uid and gid are that of your user account.
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
andauto
are options for thefstab
entry; they aren't very useful on the commandline.
– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
add a comment |
Try mounting with rw and specify the type:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx
where uid and gid are that of your user account.
Try mounting with rw and specify the type:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx
where uid and gid are that of your user account.
edited Dec 8 '09 at 0:03
answered Dec 7 '09 at 15:32
John TJohn T
142k20293329
142k20293329
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
andauto
are options for thefstab
entry; they aren't very useful on the commandline.
– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
add a comment |
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
andauto
are options for thefstab
entry; they aren't very useful on the commandline.
– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
The umask has effect when creating new files.
– geek
Dec 7 '09 at 17:05
user
and auto
are options for the fstab
entry; they aren't very useful on the commandline.– quack quixote
Dec 7 '09 at 19:03
user
and auto
are options for the fstab
entry; they aren't very useful on the commandline.– quack quixote
Dec 7 '09 at 19:03
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
yeah i just translated one of my fstab entries to a command line. Left in some bits that aren't useful but they aren't exactly harmful either.
– John T
Dec 8 '09 at 0:02
1
1
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
– chefarov
Dec 18 '17 at 8:57
add a comment |
For FAT filesystems, read/write availability is governed by the mount options.
Consult the manpage for mount and read about uid and gid mount options for FAT.
add a comment |
For FAT filesystems, read/write availability is governed by the mount options.
Consult the manpage for mount and read about uid and gid mount options for FAT.
add a comment |
For FAT filesystems, read/write availability is governed by the mount options.
Consult the manpage for mount and read about uid and gid mount options for FAT.
For FAT filesystems, read/write availability is governed by the mount options.
Consult the manpage for mount and read about uid and gid mount options for FAT.
answered Dec 7 '09 at 14:48
geekgeek
6,20231616
6,20231616
add a comment |
add a comment |
Have you tried writing to the files with a sudo
command? That should work with your current setup.
To get file writes for your normal user working, you need to use the uid
and gid
options to mount
, to set the owner of files on the partition to your current userID. You probably also want either umask
or dmask
and fmask
options.
Your mount
command would look like this:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o uid=1000,gid=1000,umask=022
# assuming your user's UID is 1000, GID is 1000
# umask=022 sets permission mode 755 for all files on the partition
add a comment |
Have you tried writing to the files with a sudo
command? That should work with your current setup.
To get file writes for your normal user working, you need to use the uid
and gid
options to mount
, to set the owner of files on the partition to your current userID. You probably also want either umask
or dmask
and fmask
options.
Your mount
command would look like this:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o uid=1000,gid=1000,umask=022
# assuming your user's UID is 1000, GID is 1000
# umask=022 sets permission mode 755 for all files on the partition
add a comment |
Have you tried writing to the files with a sudo
command? That should work with your current setup.
To get file writes for your normal user working, you need to use the uid
and gid
options to mount
, to set the owner of files on the partition to your current userID. You probably also want either umask
or dmask
and fmask
options.
Your mount
command would look like this:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o uid=1000,gid=1000,umask=022
# assuming your user's UID is 1000, GID is 1000
# umask=022 sets permission mode 755 for all files on the partition
Have you tried writing to the files with a sudo
command? That should work with your current setup.
To get file writes for your normal user working, you need to use the uid
and gid
options to mount
, to set the owner of files on the partition to your current userID. You probably also want either umask
or dmask
and fmask
options.
Your mount
command would look like this:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o uid=1000,gid=1000,umask=022
# assuming your user's UID is 1000, GID is 1000
# umask=022 sets permission mode 755 for all files on the partition
answered Dec 7 '09 at 19:00
quack quixotequack quixote
35.2k1087119
35.2k1087119
add a comment |
add a comment |
You have the wrong order on the commands you want:
sudo mkdir /media/FAT32
sudo mount /dev/sda6 /media/FAT32
sudo chmod 777 /media/FAT32
What is happening is that /media/FAT32 represents different directories before and after the mount. Before it's the directory you made, and which you chmod'ed 777. After, it's the root directory of the filesystem in /dev/sda6.
add a comment |
You have the wrong order on the commands you want:
sudo mkdir /media/FAT32
sudo mount /dev/sda6 /media/FAT32
sudo chmod 777 /media/FAT32
What is happening is that /media/FAT32 represents different directories before and after the mount. Before it's the directory you made, and which you chmod'ed 777. After, it's the root directory of the filesystem in /dev/sda6.
add a comment |
You have the wrong order on the commands you want:
sudo mkdir /media/FAT32
sudo mount /dev/sda6 /media/FAT32
sudo chmod 777 /media/FAT32
What is happening is that /media/FAT32 represents different directories before and after the mount. Before it's the directory you made, and which you chmod'ed 777. After, it's the root directory of the filesystem in /dev/sda6.
You have the wrong order on the commands you want:
sudo mkdir /media/FAT32
sudo mount /dev/sda6 /media/FAT32
sudo chmod 777 /media/FAT32
What is happening is that /media/FAT32 represents different directories before and after the mount. Before it's the directory you made, and which you chmod'ed 777. After, it's the root directory of the filesystem in /dev/sda6.
answered May 15 '10 at 20:51
jnevesjneves
31114
31114
add a comment |
add a comment |
If you simply forget about command line and mount with Nautilus, it should set it as you want.
From the terminal, the permissions of the folder before mounting doesn't matter. It's the mount options that count. Try:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx,umask=133,dmask=022
This will set files to rw-r--r--
and folders to rwxr-xr-x
.
If you want other user/group and permissions, for instance to copy files from fat32 to the ext4 partition with the desired attributes, better consult the mount
manpage. Roughly you put on umask
the opposite of what you would put on chmod
.
add a comment |
If you simply forget about command line and mount with Nautilus, it should set it as you want.
From the terminal, the permissions of the folder before mounting doesn't matter. It's the mount options that count. Try:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx,umask=133,dmask=022
This will set files to rw-r--r--
and folders to rwxr-xr-x
.
If you want other user/group and permissions, for instance to copy files from fat32 to the ext4 partition with the desired attributes, better consult the mount
manpage. Roughly you put on umask
the opposite of what you would put on chmod
.
add a comment |
If you simply forget about command line and mount with Nautilus, it should set it as you want.
From the terminal, the permissions of the folder before mounting doesn't matter. It's the mount options that count. Try:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx,umask=133,dmask=022
This will set files to rw-r--r--
and folders to rwxr-xr-x
.
If you want other user/group and permissions, for instance to copy files from fat32 to the ext4 partition with the desired attributes, better consult the mount
manpage. Roughly you put on umask
the opposite of what you would put on chmod
.
If you simply forget about command line and mount with Nautilus, it should set it as you want.
From the terminal, the permissions of the folder before mounting doesn't matter. It's the mount options that count. Try:
mount -t vfat /dev/sda6 /media/FAT32 -o rw,uid=xxx,gid=xxx,umask=133,dmask=022
This will set files to rw-r--r--
and folders to rwxr-xr-x
.
If you want other user/group and permissions, for instance to copy files from fat32 to the ext4 partition with the desired attributes, better consult the mount
manpage. Roughly you put on umask
the opposite of what you would put on chmod
.
edited Aug 20 '10 at 7:42
answered Aug 18 '10 at 12:44
user39559user39559
1,6981415
1,6981415
add a comment |
add a comment |
Sometimes I lost the windows disk from Linux and I solved using mount with "-o force", as this example:
sudo mount -t ntfs-3g /dev/sda1 /media/win -o force
In your case, being FAT32 you should read about, but my be this tip help. Anyway, try at your own risk!
add a comment |
Sometimes I lost the windows disk from Linux and I solved using mount with "-o force", as this example:
sudo mount -t ntfs-3g /dev/sda1 /media/win -o force
In your case, being FAT32 you should read about, but my be this tip help. Anyway, try at your own risk!
add a comment |
Sometimes I lost the windows disk from Linux and I solved using mount with "-o force", as this example:
sudo mount -t ntfs-3g /dev/sda1 /media/win -o force
In your case, being FAT32 you should read about, but my be this tip help. Anyway, try at your own risk!
Sometimes I lost the windows disk from Linux and I solved using mount with "-o force", as this example:
sudo mount -t ntfs-3g /dev/sda1 /media/win -o force
In your case, being FAT32 you should read about, but my be this tip help. Anyway, try at your own risk!
edited Aug 13 '11 at 6:01
Tom Wijsman
50.3k23164247
50.3k23164247
answered Dec 5 '09 at 15:47
Germán Arduino
add a comment |
add a comment |
I had exactly the same problem and the only thing that actually worked is:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,umask=0000
See also that answer
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you trychmod 777 /media/FAT32
?
– lauhub
Jan 6 '15 at 14:31
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
add a comment |
I had exactly the same problem and the only thing that actually worked is:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,umask=0000
See also that answer
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you trychmod 777 /media/FAT32
?
– lauhub
Jan 6 '15 at 14:31
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
add a comment |
I had exactly the same problem and the only thing that actually worked is:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,umask=0000
See also that answer
I had exactly the same problem and the only thing that actually worked is:
sudo mount -t vfat /dev/sda6 /media/FAT32 -o rw,umask=0000
See also that answer
edited Mar 20 '17 at 10:16
Community♦
1
1
answered Dec 17 '14 at 8:19
lauhublauhub
1679
1679
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you trychmod 777 /media/FAT32
?
– lauhub
Jan 6 '15 at 14:31
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
add a comment |
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you trychmod 777 /media/FAT32
?
– lauhub
Jan 6 '15 at 14:31
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
I did this, the usb key is still write protected
– Eildosa
Jan 6 '15 at 12:40
Did you try
chmod 777 /media/FAT32
?– lauhub
Jan 6 '15 at 14:31
Did you try
chmod 777 /media/FAT32
?– lauhub
Jan 6 '15 at 14:31
1
1
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
for some reason removing ",umask=0000" worked
– Eildosa
Jan 6 '15 at 15:32
add a comment |
Without manually mount, an fstab line do the trick,
UUID=1DD9-0D44 /media/exthd/TERABYTE_G vfat rw,noatime,uid=1000,gid=1000,user 0 0
(uid,gid are of your user, /media/exthd/TERABYTE_G must be pre-created)
but note, mount -a seems not applying properly to test the new fstab line, so a full reboot helps.
add a comment |
Without manually mount, an fstab line do the trick,
UUID=1DD9-0D44 /media/exthd/TERABYTE_G vfat rw,noatime,uid=1000,gid=1000,user 0 0
(uid,gid are of your user, /media/exthd/TERABYTE_G must be pre-created)
but note, mount -a seems not applying properly to test the new fstab line, so a full reboot helps.
add a comment |
Without manually mount, an fstab line do the trick,
UUID=1DD9-0D44 /media/exthd/TERABYTE_G vfat rw,noatime,uid=1000,gid=1000,user 0 0
(uid,gid are of your user, /media/exthd/TERABYTE_G must be pre-created)
but note, mount -a seems not applying properly to test the new fstab line, so a full reboot helps.
Without manually mount, an fstab line do the trick,
UUID=1DD9-0D44 /media/exthd/TERABYTE_G vfat rw,noatime,uid=1000,gid=1000,user 0 0
(uid,gid are of your user, /media/exthd/TERABYTE_G must be pre-created)
but note, mount -a seems not applying properly to test the new fstab line, so a full reboot helps.
answered Feb 11 '18 at 13:03
Angelo DureghelloAngelo Dureghello
1
1
add a comment |
add a comment |
Very important repair/check the disk under windows before using it on linux, by default fat/ntfs drivers disable write if they find errors on the disk
chkdsk d: /f
Then
sudo mount -t vfat /dev/sdc1 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
as motioned before
add a comment |
Very important repair/check the disk under windows before using it on linux, by default fat/ntfs drivers disable write if they find errors on the disk
chkdsk d: /f
Then
sudo mount -t vfat /dev/sdc1 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
as motioned before
add a comment |
Very important repair/check the disk under windows before using it on linux, by default fat/ntfs drivers disable write if they find errors on the disk
chkdsk d: /f
Then
sudo mount -t vfat /dev/sdc1 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
as motioned before
Very important repair/check the disk under windows before using it on linux, by default fat/ntfs drivers disable write if they find errors on the disk
chkdsk d: /f
Then
sudo mount -t vfat /dev/sdc1 /media/FAT32 -o rw,uid=$(id -u),gid=$(id -g)
as motioned before
answered Jul 16 '18 at 2:17
intikaintika
744316
744316
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f79813%2fread-and-write-permission-for-fat32-partition-in-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown