Automounted USB devices are read onlyHow do I change the default permissions for automounted USB media?Ubuntu 15.10: restoring USB storage accessWhy does lsusb show devices connected to a USB 3 port as connected to USB2 root hub?USB Media stopped working from one day to the next on 2 PCs (Ubuntu 14.04)Moving and deleting files in setguid foldersProblem finding USB pathStart application (GUI) upon mount of any USB devicesUbuntu stopped recognizing USB drivesUSB sticks and video devices not recognizedInternal HDD doesn't get recognized in “My Book” Enclosure on usb. How to format the drive?
How To Make Earth's Oceans as Brackish as Lyr's
In what sequence should an advanced civilization teach technology to medieval society to maximize rate of adoption?
Why is it called a stateful and a stateless firewall?
What is this gigantic dish at Ben Gurion airport?
What does "boys rule, girls drool" mean?
Permutations in Disguise
What's the benefit of prohibiting the use of techniques/language constructs that have not been taught?
Is it appropriate to CC a lot of people on an email
How to publish superseding results without creating enemies
Impossible Scrabble Words
If I want an interpretable model, are there methods other than Linear Regression?
Asked to Not Use Transactions and to Use A Workaround to Simulate One
Test to know when to use GLM over Linear Regression?
2000s space film where an alien species has almost wiped out the human race in a war
Why any infinite sequence of real functions can be generated from a finite set through composition?
Why is the year in this ISO timestamp not 2019?
Amortized Loans seem to benefit the bank more than the customer
Is my sink P-trap too low?
Difference between system uptime and last boot time in windows
How to give my students a straightedge instead of a ruler
Make 2019 with single digits
Is "you will become a subject matter expert" code for "you'll be working on your own 100% of the time"?
What is the source of "You can achieve a lot with hate, but even more with love" (Shakespeare?)
Examples of proofs by making reduction to a finite set
Automounted USB devices are read only
How do I change the default permissions for automounted USB media?Ubuntu 15.10: restoring USB storage accessWhy does lsusb show devices connected to a USB 3 port as connected to USB2 root hub?USB Media stopped working from one day to the next on 2 PCs (Ubuntu 14.04)Moving and deleting files in setguid foldersProblem finding USB pathStart application (GUI) upon mount of any USB devicesUbuntu stopped recognizing USB drivesUSB sticks and video devices not recognizedInternal HDD doesn't get recognized in “My Book” Enclosure on usb. How to format the drive?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Since I upgraded to Ubuntu 12.10 the automout of USB devices does not work as expected. When I plug in a storage device it is recognized correctly but I do not have write privileges on it. I thought, that maybe the permissions of /media are not correctly set, but I don't know, how they have to be. They are like this:
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media
I also checked whether my user is a member of the group plugdev and he definitely is.
What else could be the cause of that problem?
Update: Here is the dmesg output after plugging in an USB storage device: http://pastebin.com/pJ7qebQR
usb mount permissions
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
|
show 2 more comments
Since I upgraded to Ubuntu 12.10 the automout of USB devices does not work as expected. When I plug in a storage device it is recognized correctly but I do not have write privileges on it. I thought, that maybe the permissions of /media are not correctly set, but I don't know, how they have to be. They are like this:
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media
I also checked whether my user is a member of the group plugdev and he definitely is.
What else could be the cause of that problem?
Update: Here is the dmesg output after plugging in an USB storage device: http://pastebin.com/pJ7qebQR
usb mount permissions
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
Could you paste/link the relevant part ofdmesgoutput from when you plug in or mount the drive?
– onik
Jan 25 '13 at 14:02
How do I do this?
– user5950
Jan 25 '13 at 14:03
Open a terminal and typedmesgright after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.
– onik
Jan 25 '13 at 14:06
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
2
Could you paste/ link the output ofcat /etc/fstabandmount(pls ignore the above commend as i can't edit or delete from my phone)
– totti
Feb 3 '13 at 6:39
|
show 2 more comments
Since I upgraded to Ubuntu 12.10 the automout of USB devices does not work as expected. When I plug in a storage device it is recognized correctly but I do not have write privileges on it. I thought, that maybe the permissions of /media are not correctly set, but I don't know, how they have to be. They are like this:
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media
I also checked whether my user is a member of the group plugdev and he definitely is.
What else could be the cause of that problem?
Update: Here is the dmesg output after plugging in an USB storage device: http://pastebin.com/pJ7qebQR
usb mount permissions
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
Since I upgraded to Ubuntu 12.10 the automout of USB devices does not work as expected. When I plug in a storage device it is recognized correctly but I do not have write privileges on it. I thought, that maybe the permissions of /media are not correctly set, but I don't know, how they have to be. They are like this:
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media
I also checked whether my user is a member of the group plugdev and he definitely is.
What else could be the cause of that problem?
Update: Here is the dmesg output after plugging in an USB storage device: http://pastebin.com/pJ7qebQR
usb mount permissions
usb mount permissions
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
edited Jan 25 '13 at 14:32
user5950
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
asked Jan 25 '13 at 13:53
user5950user5950
2,4006 gold badges33 silver badges65 bronze badges
2,4006 gold badges33 silver badges65 bronze badges
Could you paste/link the relevant part ofdmesgoutput from when you plug in or mount the drive?
– onik
Jan 25 '13 at 14:02
How do I do this?
– user5950
Jan 25 '13 at 14:03
Open a terminal and typedmesgright after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.
– onik
Jan 25 '13 at 14:06
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
2
Could you paste/ link the output ofcat /etc/fstabandmount(pls ignore the above commend as i can't edit or delete from my phone)
– totti
Feb 3 '13 at 6:39
|
show 2 more comments
Could you paste/link the relevant part ofdmesgoutput from when you plug in or mount the drive?
– onik
Jan 25 '13 at 14:02
How do I do this?
– user5950
Jan 25 '13 at 14:03
Open a terminal and typedmesgright after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.
– onik
Jan 25 '13 at 14:06
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
2
Could you paste/ link the output ofcat /etc/fstabandmount(pls ignore the above commend as i can't edit or delete from my phone)
– totti
Feb 3 '13 at 6:39
Could you paste/link the relevant part of
dmesg output from when you plug in or mount the drive?– onik
Jan 25 '13 at 14:02
Could you paste/link the relevant part of
dmesg output from when you plug in or mount the drive?– onik
Jan 25 '13 at 14:02
How do I do this?
– user5950
Jan 25 '13 at 14:03
How do I do this?
– user5950
Jan 25 '13 at 14:03
Open a terminal and type
dmesg right after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.– onik
Jan 25 '13 at 14:06
Open a terminal and type
dmesg right after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.– onik
Jan 25 '13 at 14:06
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
2
2
Could you paste/ link the output of
cat /etc/fstab and mount (pls ignore the above commend as i can't edit or delete from my phone)– totti
Feb 3 '13 at 6:39
Could you paste/ link the output of
cat /etc/fstab and mount (pls ignore the above commend as i can't edit or delete from my phone)– totti
Feb 3 '13 at 6:39
|
show 2 more comments
6 Answers
6
active
oldest
votes
I think you are suffering the bug #1021375
You can workaround it by renaming the folder ~/.config/nautilus and then logout and log back in.
mv ~/.config/nautilus ~/.config/nautilus-bak- Logout.
- Login.
edited Jun 28 '16 at 1:07
muru
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
killall nautilusdid the trick as @isset suggested. Thanks.
– Lekhnath
Jan 21 '17 at 15:18
|
show 1 more comment
sudo mount -o remount,rw /media/MonterFolderName
This shall solve the issue. I am not sure how to make it permanent. I am not sure if chmod would work if in case the USB is not mounted in readwrite mode in the first place.
Tested on Ubuntu 12.10 and 13.
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
3
may I suggestsudo mount -o remount,rw /media/$USER/*
– mchid
Nov 28 '14 at 7:03
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
mount: cannot remount /dev/sda1 read-write, is write-protected
– Pithikos
May 20 '17 at 9:53
|
show 2 more comments
When the USB is inserted it's mounted on /media/<username> that you should have permissions through an access control list.
You can check what the permissions are e.g.
bcbc@23:34:50:~$ getfacl /media/bcbc
# file: media/bcbc
# owner: root
# group: root
user::rwx
user:bcbc:r-x
group::---
mask::r-x
other::---
If there is no access control list, just delete the directory and it will recreate it with the correct permissions.
sudo rmdir /media/<username>
Or add the ACL:
sudo setfacl -m u:<username>:rx /media/<username>
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
add a comment
|
Problem appears to have gone away
This is a 5 y/o question on short term release Ubuntu 12.10. The dmesg link is no longer available in the OP's question. But if I plug in a Ubuntu 18.04 Live USB with persistent storage dmesg reveals:
$ dmesg | tail -n18
[115528.249547] usb-storage 1-9:1.0: USB Mass Storage device detected
[115528.250152] scsi host2: usb-storage 1-9:1.0
[115528.250474] usbcore: registered new interface driver usb-storage
[115528.255685] usbcore: registered new interface driver uas
[115529.281407] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[115529.282090] sd 2:0:0:0: Attached scsi generic sg1 type 0
[115529.992200] sd 2:0:0:0: [sdb] 30261248 512-byte logical blocks: (15.5 GB/14.4 GiB)
[115529.992998] sd 2:0:0:0: [sdb] Write Protect is off
[115529.993006] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[115529.993787] sd 2:0:0:0: [sdb] No Caching mode page found
[115529.993797] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[115530.592616] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[115530.596279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[115531.018019] EXT4-fs (sdb5): warning: mounting unchecked fs, running e2fsck is recommended
[115531.470201] EXT4-fs (sdb5): mounted filesystem without journal. Opts: (null)
[115531.480738] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.483397] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.512219] ISO 9660 Extensions: RRIP_1991A
Unlike OP implies, there is no warning for read-only. Notice the line:
sd 2:0:0:0: [sdb] Write Protect is off
Apparently whatever the problem was 5 years ago, it no longer exists today under Ubuntu 16.04 LTS. Also for the only other LTS version today, 14.04 I can't remember this being a problem either. Only SD RAM cards come to mind as being read only, which is a different problem altogether.
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
add a comment
|
Nothing is wrong with the mounting options and fstab file, as far as my knowledge, you just have to use below command to get the Required right permissions on the media folder. and I will explain you why.
1) your current permissions on the folder as you mentioned are as below. (Apologize if you know this and I'm bothering you with it.)
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media in this d stands for directory, first group of rwx stands for the rights of the user who owns that object, which is in your case root.
second group of rwx stands for the rights of the group who owns that object & here you have only r-x which means even if you are in the sudoers file or in the admin group you do not have rights to write in it.
Third group of rwx is or other users, who are not owner of that object nor in the group who has ownership rights of that object. if your case it is again r-x only. so that is why you do not have write permissions on it.
2) So you need to change permissions of the media folder. (I am going to consider that you are in admin group or sudoers file, because this will work only in that case). so this is what you need to do.
$ sudo chmod -R 775 /media
3) This will give you required write permissions on the all auto mounted drives.
Please check and let me know if this does not work will tell you what else can be done to fix this issue.
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the-Rflag tochmod. For one thing, the permissions of/media/$USERshould (now) be 750 with an ACL for$USER. (Ubuntu versions later than 15.04 must have theaclpackage sincesystemddepends on it.)
– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,chmod 775 /media/user/deviceis good enough.
– erm3nda
Jan 30 '17 at 18:19
add a comment
|
I hit this problem too, in my case it was a fat32 corruption problem allowing to read it but not to write.
Then if your usb key is a fat32, it might be that your filesyste is corrupted.
To verify do a sudo dmesg
[17183.485565] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[17205.406905] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
then unmout it, sudo fsck.vfat your_device_partition it then mount it again.
in my specific case :
sudo fsck.vfat /dev/sdc1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/T90bis
Start does point to root directory. Deleting dir.
Reclaimed 93 unused clusters (1523712 bytes).
Free cluster summary wrong (1248506 vs. really 1248599)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/sdc1: 916 files, 704527/1953126 clusters
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
add a comment
|
protected by Community♦ Jun 28 '16 at 1:29
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?
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you are suffering the bug #1021375
You can workaround it by renaming the folder ~/.config/nautilus and then logout and log back in.
mv ~/.config/nautilus ~/.config/nautilus-bak- Logout.
- Login.
edited Jun 28 '16 at 1:07
muru
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
killall nautilusdid the trick as @isset suggested. Thanks.
– Lekhnath
Jan 21 '17 at 15:18
|
show 1 more comment
I think you are suffering the bug #1021375
You can workaround it by renaming the folder ~/.config/nautilus and then logout and log back in.
mv ~/.config/nautilus ~/.config/nautilus-bak- Logout.
- Login.
edited Jun 28 '16 at 1:07
muru
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
killall nautilusdid the trick as @isset suggested. Thanks.
– Lekhnath
Jan 21 '17 at 15:18
|
show 1 more comment
I think you are suffering the bug #1021375
You can workaround it by renaming the folder ~/.config/nautilus and then logout and log back in.
mv ~/.config/nautilus ~/.config/nautilus-bak- Logout.
- Login.
edited Jun 28 '16 at 1:07
muru
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
I think you are suffering the bug #1021375
You can workaround it by renaming the folder ~/.config/nautilus and then logout and log back in.
mv ~/.config/nautilus ~/.config/nautilus-bak- Logout.
- Login.
edited Jun 28 '16 at 1:07
muru
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
edited Jun 28 '16 at 1:07
muru
1
edited Jun 28 '16 at 1:07
muru
1
edited Jun 28 '16 at 1:07
muru
1
1
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
answered Jan 29 '14 at 19:43
desguadesgua
28.5k8 gold badges83 silver badges115 bronze badges
28.5k8 gold badges83 silver badges115 bronze badges
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
killall nautilusdid the trick as @isset suggested. Thanks.
– Lekhnath
Jan 21 '17 at 15:18
|
show 1 more comment
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
killall nautilusdid the trick as @isset suggested. Thanks.
– Lekhnath
Jan 21 '17 at 15:18
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
I don't know if there are multiple possible causes of this problem, but I don't know why this answer hasn't gotten more upvotes. This was exactly my problem, with the exception of the fact that I was using the nemo file manager rather than nautilus. But I confirmed that I could create/edit/delete files using an alternative file manager (PCManFM), the terminal, and the application Save File dialog of gedit and LibreOffice, so the problem only affects nautilus/nemo. Your proposed workaround also seems to have done the trick.
– Lee Hachadoorian
Jan 28 '15 at 17:47
2
2
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
This answer is what solved my problem. Thanks !
– David V.
Jun 24 '15 at 5:39
11
11
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
killall nautilus is enough, no need for logging out. :)
– isset
Jul 19 '15 at 16:33
8
8
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
I am using Ubuntu 16.04 and the problem appeared out of thin air. The solution still solves the problem.
– sebers
Nov 17 '16 at 8:19
5
5
killall nautilus did the trick as @isset suggested. Thanks.– Lekhnath
Jan 21 '17 at 15:18
killall nautilus did the trick as @isset suggested. Thanks.– Lekhnath
Jan 21 '17 at 15:18
|
show 1 more comment
sudo mount -o remount,rw /media/MonterFolderName
This shall solve the issue. I am not sure how to make it permanent. I am not sure if chmod would work if in case the USB is not mounted in readwrite mode in the first place.
Tested on Ubuntu 12.10 and 13.
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
3
may I suggestsudo mount -o remount,rw /media/$USER/*
– mchid
Nov 28 '14 at 7:03
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
mount: cannot remount /dev/sda1 read-write, is write-protected
– Pithikos
May 20 '17 at 9:53
|
show 2 more comments
sudo mount -o remount,rw /media/MonterFolderName
This shall solve the issue. I am not sure how to make it permanent. I am not sure if chmod would work if in case the USB is not mounted in readwrite mode in the first place.
Tested on Ubuntu 12.10 and 13.
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
3
may I suggestsudo mount -o remount,rw /media/$USER/*
– mchid
Nov 28 '14 at 7:03
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
mount: cannot remount /dev/sda1 read-write, is write-protected
– Pithikos
May 20 '17 at 9:53
|
show 2 more comments
sudo mount -o remount,rw /media/MonterFolderName
This shall solve the issue. I am not sure how to make it permanent. I am not sure if chmod would work if in case the USB is not mounted in readwrite mode in the first place.
Tested on Ubuntu 12.10 and 13.
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
sudo mount -o remount,rw /media/MonterFolderName
This shall solve the issue. I am not sure how to make it permanent. I am not sure if chmod would work if in case the USB is not mounted in readwrite mode in the first place.
Tested on Ubuntu 12.10 and 13.
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
edited Jun 1 '16 at 11:46
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
answered Jul 30 '13 at 10:28
JalpeshJalpesh
3254 silver badges7 bronze badges
3254 silver badges7 bronze badges
3
may I suggestsudo mount -o remount,rw /media/$USER/*
– mchid
Nov 28 '14 at 7:03
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
mount: cannot remount /dev/sda1 read-write, is write-protected
– Pithikos
May 20 '17 at 9:53
|
show 2 more comments
3
may I suggestsudo mount -o remount,rw /media/$USER/*
– mchid
Nov 28 '14 at 7:03
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
mount: cannot remount /dev/sda1 read-write, is write-protected
– Pithikos
May 20 '17 at 9:53
3
3
may I suggest
sudo mount -o remount,rw /media/$USER/*– mchid
Nov 28 '14 at 7:03
may I suggest
sudo mount -o remount,rw /media/$USER/*– mchid
Nov 28 '14 at 7:03
4
4
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
did not work in ubuntu 16.04 :(
– knocte
May 29 '16 at 17:34
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Sorry, It was in older versions of android, I had tested it on ubuntu 13 max I think.
– Jalpesh
May 30 '16 at 4:15
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
Ubuntu I meant...
– Jalpesh
Jul 10 '16 at 15:35
1
1
mount: cannot remount /dev/sda1 read-write, is write-protected– Pithikos
May 20 '17 at 9:53
mount: cannot remount /dev/sda1 read-write, is write-protected– Pithikos
May 20 '17 at 9:53
|
show 2 more comments
When the USB is inserted it's mounted on /media/<username> that you should have permissions through an access control list.
You can check what the permissions are e.g.
bcbc@23:34:50:~$ getfacl /media/bcbc
# file: media/bcbc
# owner: root
# group: root
user::rwx
user:bcbc:r-x
group::---
mask::r-x
other::---
If there is no access control list, just delete the directory and it will recreate it with the correct permissions.
sudo rmdir /media/<username>
Or add the ACL:
sudo setfacl -m u:<username>:rx /media/<username>
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
add a comment
|
When the USB is inserted it's mounted on /media/<username> that you should have permissions through an access control list.
You can check what the permissions are e.g.
bcbc@23:34:50:~$ getfacl /media/bcbc
# file: media/bcbc
# owner: root
# group: root
user::rwx
user:bcbc:r-x
group::---
mask::r-x
other::---
If there is no access control list, just delete the directory and it will recreate it with the correct permissions.
sudo rmdir /media/<username>
Or add the ACL:
sudo setfacl -m u:<username>:rx /media/<username>
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
add a comment
|
When the USB is inserted it's mounted on /media/<username> that you should have permissions through an access control list.
You can check what the permissions are e.g.
bcbc@23:34:50:~$ getfacl /media/bcbc
# file: media/bcbc
# owner: root
# group: root
user::rwx
user:bcbc:r-x
group::---
mask::r-x
other::---
If there is no access control list, just delete the directory and it will recreate it with the correct permissions.
sudo rmdir /media/<username>
Or add the ACL:
sudo setfacl -m u:<username>:rx /media/<username>
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
When the USB is inserted it's mounted on /media/<username> that you should have permissions through an access control list.
You can check what the permissions are e.g.
bcbc@23:34:50:~$ getfacl /media/bcbc
# file: media/bcbc
# owner: root
# group: root
user::rwx
user:bcbc:r-x
group::---
mask::r-x
other::---
If there is no access control list, just delete the directory and it will recreate it with the correct permissions.
sudo rmdir /media/<username>
Or add the ACL:
sudo setfacl -m u:<username>:rx /media/<username>
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
answered Feb 3 '13 at 4:34
bcbcbcbc
5,8694 gold badges30 silver badges67 bronze badges
5,8694 gold badges30 silver badges67 bronze badges
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
add a comment
|
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
THIS - this is the solution that finally works for me. On Mint, Kubuntu, Debian and Ubuntu. Nautilus was never the real issue at all (and was not even used in a couple of the distros listed). Thank you!
– growlf
May 13 '17 at 18:32
add a comment
|
Problem appears to have gone away
This is a 5 y/o question on short term release Ubuntu 12.10. The dmesg link is no longer available in the OP's question. But if I plug in a Ubuntu 18.04 Live USB with persistent storage dmesg reveals:
$ dmesg | tail -n18
[115528.249547] usb-storage 1-9:1.0: USB Mass Storage device detected
[115528.250152] scsi host2: usb-storage 1-9:1.0
[115528.250474] usbcore: registered new interface driver usb-storage
[115528.255685] usbcore: registered new interface driver uas
[115529.281407] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[115529.282090] sd 2:0:0:0: Attached scsi generic sg1 type 0
[115529.992200] sd 2:0:0:0: [sdb] 30261248 512-byte logical blocks: (15.5 GB/14.4 GiB)
[115529.992998] sd 2:0:0:0: [sdb] Write Protect is off
[115529.993006] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[115529.993787] sd 2:0:0:0: [sdb] No Caching mode page found
[115529.993797] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[115530.592616] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[115530.596279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[115531.018019] EXT4-fs (sdb5): warning: mounting unchecked fs, running e2fsck is recommended
[115531.470201] EXT4-fs (sdb5): mounted filesystem without journal. Opts: (null)
[115531.480738] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.483397] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.512219] ISO 9660 Extensions: RRIP_1991A
Unlike OP implies, there is no warning for read-only. Notice the line:
sd 2:0:0:0: [sdb] Write Protect is off
Apparently whatever the problem was 5 years ago, it no longer exists today under Ubuntu 16.04 LTS. Also for the only other LTS version today, 14.04 I can't remember this being a problem either. Only SD RAM cards come to mind as being read only, which is a different problem altogether.
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
add a comment
|
Problem appears to have gone away
This is a 5 y/o question on short term release Ubuntu 12.10. The dmesg link is no longer available in the OP's question. But if I plug in a Ubuntu 18.04 Live USB with persistent storage dmesg reveals:
$ dmesg | tail -n18
[115528.249547] usb-storage 1-9:1.0: USB Mass Storage device detected
[115528.250152] scsi host2: usb-storage 1-9:1.0
[115528.250474] usbcore: registered new interface driver usb-storage
[115528.255685] usbcore: registered new interface driver uas
[115529.281407] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[115529.282090] sd 2:0:0:0: Attached scsi generic sg1 type 0
[115529.992200] sd 2:0:0:0: [sdb] 30261248 512-byte logical blocks: (15.5 GB/14.4 GiB)
[115529.992998] sd 2:0:0:0: [sdb] Write Protect is off
[115529.993006] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[115529.993787] sd 2:0:0:0: [sdb] No Caching mode page found
[115529.993797] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[115530.592616] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[115530.596279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[115531.018019] EXT4-fs (sdb5): warning: mounting unchecked fs, running e2fsck is recommended
[115531.470201] EXT4-fs (sdb5): mounted filesystem without journal. Opts: (null)
[115531.480738] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.483397] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.512219] ISO 9660 Extensions: RRIP_1991A
Unlike OP implies, there is no warning for read-only. Notice the line:
sd 2:0:0:0: [sdb] Write Protect is off
Apparently whatever the problem was 5 years ago, it no longer exists today under Ubuntu 16.04 LTS. Also for the only other LTS version today, 14.04 I can't remember this being a problem either. Only SD RAM cards come to mind as being read only, which is a different problem altogether.
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
add a comment
|
Problem appears to have gone away
This is a 5 y/o question on short term release Ubuntu 12.10. The dmesg link is no longer available in the OP's question. But if I plug in a Ubuntu 18.04 Live USB with persistent storage dmesg reveals:
$ dmesg | tail -n18
[115528.249547] usb-storage 1-9:1.0: USB Mass Storage device detected
[115528.250152] scsi host2: usb-storage 1-9:1.0
[115528.250474] usbcore: registered new interface driver usb-storage
[115528.255685] usbcore: registered new interface driver uas
[115529.281407] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[115529.282090] sd 2:0:0:0: Attached scsi generic sg1 type 0
[115529.992200] sd 2:0:0:0: [sdb] 30261248 512-byte logical blocks: (15.5 GB/14.4 GiB)
[115529.992998] sd 2:0:0:0: [sdb] Write Protect is off
[115529.993006] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[115529.993787] sd 2:0:0:0: [sdb] No Caching mode page found
[115529.993797] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[115530.592616] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[115530.596279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[115531.018019] EXT4-fs (sdb5): warning: mounting unchecked fs, running e2fsck is recommended
[115531.470201] EXT4-fs (sdb5): mounted filesystem without journal. Opts: (null)
[115531.480738] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.483397] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.512219] ISO 9660 Extensions: RRIP_1991A
Unlike OP implies, there is no warning for read-only. Notice the line:
sd 2:0:0:0: [sdb] Write Protect is off
Apparently whatever the problem was 5 years ago, it no longer exists today under Ubuntu 16.04 LTS. Also for the only other LTS version today, 14.04 I can't remember this being a problem either. Only SD RAM cards come to mind as being read only, which is a different problem altogether.
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
Problem appears to have gone away
This is a 5 y/o question on short term release Ubuntu 12.10. The dmesg link is no longer available in the OP's question. But if I plug in a Ubuntu 18.04 Live USB with persistent storage dmesg reveals:
$ dmesg | tail -n18
[115528.249547] usb-storage 1-9:1.0: USB Mass Storage device detected
[115528.250152] scsi host2: usb-storage 1-9:1.0
[115528.250474] usbcore: registered new interface driver usb-storage
[115528.255685] usbcore: registered new interface driver uas
[115529.281407] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO PMAP PQ: 0 ANSI: 6
[115529.282090] sd 2:0:0:0: Attached scsi generic sg1 type 0
[115529.992200] sd 2:0:0:0: [sdb] 30261248 512-byte logical blocks: (15.5 GB/14.4 GiB)
[115529.992998] sd 2:0:0:0: [sdb] Write Protect is off
[115529.993006] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[115529.993787] sd 2:0:0:0: [sdb] No Caching mode page found
[115529.993797] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[115530.592616] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[115530.596279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[115531.018019] EXT4-fs (sdb5): warning: mounting unchecked fs, running e2fsck is recommended
[115531.470201] EXT4-fs (sdb5): mounted filesystem without journal. Opts: (null)
[115531.480738] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.483397] ISO 9660 Extensions: Microsoft Joliet Level 3
[115531.512219] ISO 9660 Extensions: RRIP_1991A
Unlike OP implies, there is no warning for read-only. Notice the line:
sd 2:0:0:0: [sdb] Write Protect is off
Apparently whatever the problem was 5 years ago, it no longer exists today under Ubuntu 16.04 LTS. Also for the only other LTS version today, 14.04 I can't remember this being a problem either. Only SD RAM cards come to mind as being read only, which is a different problem altogether.
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
answered Mar 6 '18 at 3:03
WinEunuuchs2UnixWinEunuuchs2Unix
58.2k17 gold badges117 silver badges228 bronze badges
58.2k17 gold badges117 silver badges228 bronze badges
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
add a comment
|
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I ran into this yesterday on 16.04 so I have to disagree with you that the issue is "gone"
– Thomas Ward♦
Mar 6 '18 at 13:26
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
I should say with a default install. There are all kinds of security overrides that employers want to install. For example to prevent employees downloading a list of customer data to USB.
– WinEunuuchs2Unix
Mar 6 '18 at 13:38
add a comment
|
Nothing is wrong with the mounting options and fstab file, as far as my knowledge, you just have to use below command to get the Required right permissions on the media folder. and I will explain you why.
1) your current permissions on the folder as you mentioned are as below. (Apologize if you know this and I'm bothering you with it.)
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media in this d stands for directory, first group of rwx stands for the rights of the user who owns that object, which is in your case root.
second group of rwx stands for the rights of the group who owns that object & here you have only r-x which means even if you are in the sudoers file or in the admin group you do not have rights to write in it.
Third group of rwx is or other users, who are not owner of that object nor in the group who has ownership rights of that object. if your case it is again r-x only. so that is why you do not have write permissions on it.
2) So you need to change permissions of the media folder. (I am going to consider that you are in admin group or sudoers file, because this will work only in that case). so this is what you need to do.
$ sudo chmod -R 775 /media
3) This will give you required write permissions on the all auto mounted drives.
Please check and let me know if this does not work will tell you what else can be done to fix this issue.
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the-Rflag tochmod. For one thing, the permissions of/media/$USERshould (now) be 750 with an ACL for$USER. (Ubuntu versions later than 15.04 must have theaclpackage sincesystemddepends on it.)
– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,chmod 775 /media/user/deviceis good enough.
– erm3nda
Jan 30 '17 at 18:19
add a comment
|
Nothing is wrong with the mounting options and fstab file, as far as my knowledge, you just have to use below command to get the Required right permissions on the media folder. and I will explain you why.
1) your current permissions on the folder as you mentioned are as below. (Apologize if you know this and I'm bothering you with it.)
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media in this d stands for directory, first group of rwx stands for the rights of the user who owns that object, which is in your case root.
second group of rwx stands for the rights of the group who owns that object & here you have only r-x which means even if you are in the sudoers file or in the admin group you do not have rights to write in it.
Third group of rwx is or other users, who are not owner of that object nor in the group who has ownership rights of that object. if your case it is again r-x only. so that is why you do not have write permissions on it.
2) So you need to change permissions of the media folder. (I am going to consider that you are in admin group or sudoers file, because this will work only in that case). so this is what you need to do.
$ sudo chmod -R 775 /media
3) This will give you required write permissions on the all auto mounted drives.
Please check and let me know if this does not work will tell you what else can be done to fix this issue.
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the-Rflag tochmod. For one thing, the permissions of/media/$USERshould (now) be 750 with an ACL for$USER. (Ubuntu versions later than 15.04 must have theaclpackage sincesystemddepends on it.)
– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,chmod 775 /media/user/deviceis good enough.
– erm3nda
Jan 30 '17 at 18:19
add a comment
|
Nothing is wrong with the mounting options and fstab file, as far as my knowledge, you just have to use below command to get the Required right permissions on the media folder. and I will explain you why.
1) your current permissions on the folder as you mentioned are as below. (Apologize if you know this and I'm bothering you with it.)
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media in this d stands for directory, first group of rwx stands for the rights of the user who owns that object, which is in your case root.
second group of rwx stands for the rights of the group who owns that object & here you have only r-x which means even if you are in the sudoers file or in the admin group you do not have rights to write in it.
Third group of rwx is or other users, who are not owner of that object nor in the group who has ownership rights of that object. if your case it is again r-x only. so that is why you do not have write permissions on it.
2) So you need to change permissions of the media folder. (I am going to consider that you are in admin group or sudoers file, because this will work only in that case). so this is what you need to do.
$ sudo chmod -R 775 /media
3) This will give you required write permissions on the all auto mounted drives.
Please check and let me know if this does not work will tell you what else can be done to fix this issue.
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
Nothing is wrong with the mounting options and fstab file, as far as my knowledge, you just have to use below command to get the Required right permissions on the media folder. and I will explain you why.
1) your current permissions on the folder as you mentioned are as below. (Apologize if you know this and I'm bothering you with it.)
drwxr-xr-x 14 root root 4096 Jan 13 19:37 media in this d stands for directory, first group of rwx stands for the rights of the user who owns that object, which is in your case root.
second group of rwx stands for the rights of the group who owns that object & here you have only r-x which means even if you are in the sudoers file or in the admin group you do not have rights to write in it.
Third group of rwx is or other users, who are not owner of that object nor in the group who has ownership rights of that object. if your case it is again r-x only. so that is why you do not have write permissions on it.
2) So you need to change permissions of the media folder. (I am going to consider that you are in admin group or sudoers file, because this will work only in that case). so this is what you need to do.
$ sudo chmod -R 775 /media
3) This will give you required write permissions on the all auto mounted drives.
Please check and let me know if this does not work will tell you what else can be done to fix this issue.
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
answered Feb 5 '13 at 20:06
HrishHrish
1,38710 gold badges34 silver badges56 bronze badges
1,38710 gold badges34 silver badges56 bronze badges
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the-Rflag tochmod. For one thing, the permissions of/media/$USERshould (now) be 750 with an ACL for$USER. (Ubuntu versions later than 15.04 must have theaclpackage sincesystemddepends on it.)
– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,chmod 775 /media/user/deviceis good enough.
– erm3nda
Jan 30 '17 at 18:19
add a comment
|
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the-Rflag tochmod. For one thing, the permissions of/media/$USERshould (now) be 750 with an ACL for$USER. (Ubuntu versions later than 15.04 must have theaclpackage sincesystemddepends on it.)
– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,chmod 775 /media/user/deviceis good enough.
– erm3nda
Jan 30 '17 at 18:19
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
One more thing... About ACL does not come automatically installed with OS ... so unless you have installed it.. it stays out of Question in your case. if you have installed it pleas let me know.
– Hrish
Feb 5 '13 at 20:09
1
1
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the
-R flag to chmod. For one thing, the permissions of /media/$USER should (now) be 750 with an ACL for $USER. (Ubuntu versions later than 15.04 must have the acl package since systemd depends on it.)– Zanna
Jan 25 '17 at 6:27
No it won't give you write permission, and it's a bad idea too. Being in the sudo group or admin group (if there is one) does not give you group permissions where the group owner is root, so this will not change anything for you. Please also consider the difference between file and directory permissions and possible adverse consequences when recommending the use of the
-R flag to chmod. For one thing, the permissions of /media/$USER should (now) be 750 with an ACL for $USER. (Ubuntu versions later than 15.04 must have the acl package since systemd depends on it.)– Zanna
Jan 25 '17 at 6:27
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,
chmod 775 /media/user/device is good enough.– erm3nda
Jan 30 '17 at 18:19
I had that problem today and i solved it just doing chmod over the mountpoint. I am able to write to subfolders, is just the drive root the one complaining. So,
chmod 775 /media/user/device is good enough.– erm3nda
Jan 30 '17 at 18:19
add a comment
|
I hit this problem too, in my case it was a fat32 corruption problem allowing to read it but not to write.
Then if your usb key is a fat32, it might be that your filesyste is corrupted.
To verify do a sudo dmesg
[17183.485565] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[17205.406905] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
then unmout it, sudo fsck.vfat your_device_partition it then mount it again.
in my specific case :
sudo fsck.vfat /dev/sdc1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/T90bis
Start does point to root directory. Deleting dir.
Reclaimed 93 unused clusters (1523712 bytes).
Free cluster summary wrong (1248506 vs. really 1248599)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/sdc1: 916 files, 704527/1953126 clusters
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
add a comment
|
I hit this problem too, in my case it was a fat32 corruption problem allowing to read it but not to write.
Then if your usb key is a fat32, it might be that your filesyste is corrupted.
To verify do a sudo dmesg
[17183.485565] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[17205.406905] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
then unmout it, sudo fsck.vfat your_device_partition it then mount it again.
in my specific case :
sudo fsck.vfat /dev/sdc1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/T90bis
Start does point to root directory. Deleting dir.
Reclaimed 93 unused clusters (1523712 bytes).
Free cluster summary wrong (1248506 vs. really 1248599)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/sdc1: 916 files, 704527/1953126 clusters
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
add a comment
|
I hit this problem too, in my case it was a fat32 corruption problem allowing to read it but not to write.
Then if your usb key is a fat32, it might be that your filesyste is corrupted.
To verify do a sudo dmesg
[17183.485565] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[17205.406905] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
then unmout it, sudo fsck.vfat your_device_partition it then mount it again.
in my specific case :
sudo fsck.vfat /dev/sdc1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/T90bis
Start does point to root directory. Deleting dir.
Reclaimed 93 unused clusters (1523712 bytes).
Free cluster summary wrong (1248506 vs. really 1248599)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/sdc1: 916 files, 704527/1953126 clusters
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
I hit this problem too, in my case it was a fat32 corruption problem allowing to read it but not to write.
Then if your usb key is a fat32, it might be that your filesyste is corrupted.
To verify do a sudo dmesg
[17183.485565] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[17205.406905] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
then unmout it, sudo fsck.vfat your_device_partition it then mount it again.
in my specific case :
sudo fsck.vfat /dev/sdc1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/T90bis
Start does point to root directory. Deleting dir.
Reclaimed 93 unused clusters (1523712 bytes).
Free cluster summary wrong (1248506 vs. really 1248599)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/sdc1: 916 files, 704527/1953126 clusters
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
answered Apr 15 at 10:49
philippe lhardyphilippe lhardy
2412 silver badges4 bronze badges
2412 silver badges4 bronze badges
add a comment
|
add a comment
|
protected by Community♦ Jun 28 '16 at 1:29
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?
Could you paste/link the relevant part of
dmesgoutput from when you plug in or mount the drive?– onik
Jan 25 '13 at 14:02
How do I do this?
– user5950
Jan 25 '13 at 14:03
Open a terminal and type
dmesgright after plugging in the drive, and a few of the last lines should have information on the device detection. Or you can copy/paste the whole output (censor if needed) on Pastebin and share the link here.– onik
Jan 25 '13 at 14:06
Added the output to the post above.
– user5950
Jan 25 '13 at 14:33
2
Could you paste/ link the output of
cat /etc/fstabandmount(pls ignore the above commend as i can't edit or delete from my phone)– totti
Feb 3 '13 at 6:39