Cannot copy to USB - every USB stick is read only (16.04)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Every USB stick I plug in is read-only and I cannot copy files to it.
Here's what I've tried so far.
- I've formated each one to either FAT32 or NTFS, quick and detailed
format in Disks and GParted - I've used GParted to format the stick and recreate the msdos
partition table layout. The device mounts fine, but won't copy files - I've tried using other USBs that already have files.
- I've tried to unmount, remount:
sudo chmod 777 /media/USER/USB_LABEL and
sudo mount -o remount,rw '/media/gaj/Working'
- I've changed permissions on all my media
There are no panic messsages when pluging in the USB:
dmesg | grep -i panic
- These are the dmesg log messages after pluging in and trying to copy to USB ( is the brand)
[ 4596.836206] scsi 4:0:0:0: Direct-Access Kingston DT 101 G2 PMAP PQ: 0 ANSI: 0 CCS
[ 4596.836620] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 4598.105667] sd 4:0:0:0: [sdb] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 4598.107900] sd 4:0:0:0: [sdb] Write Protect is off
[ 4598.107903] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4598.110120] sd 4:0:0:0: [sdb] No Caching mode page found
[ 4598.110123] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4598.140729] sdb: sdb1
[ 4598.146626] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 4598.372004] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
- I run fsck on my USB device /dev/sdb1, which finds some "dirt" and fixes it, but again nothing changes.
Can anyone help me before I smash my computer into pieces and move to fedora?
boot partitioning usb mount
add a comment |
Every USB stick I plug in is read-only and I cannot copy files to it.
Here's what I've tried so far.
- I've formated each one to either FAT32 or NTFS, quick and detailed
format in Disks and GParted - I've used GParted to format the stick and recreate the msdos
partition table layout. The device mounts fine, but won't copy files - I've tried using other USBs that already have files.
- I've tried to unmount, remount:
sudo chmod 777 /media/USER/USB_LABEL and
sudo mount -o remount,rw '/media/gaj/Working'
- I've changed permissions on all my media
There are no panic messsages when pluging in the USB:
dmesg | grep -i panic
- These are the dmesg log messages after pluging in and trying to copy to USB ( is the brand)
[ 4596.836206] scsi 4:0:0:0: Direct-Access Kingston DT 101 G2 PMAP PQ: 0 ANSI: 0 CCS
[ 4596.836620] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 4598.105667] sd 4:0:0:0: [sdb] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 4598.107900] sd 4:0:0:0: [sdb] Write Protect is off
[ 4598.107903] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4598.110120] sd 4:0:0:0: [sdb] No Caching mode page found
[ 4598.110123] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4598.140729] sdb: sdb1
[ 4598.146626] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 4598.372004] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
- I run fsck on my USB device /dev/sdb1, which finds some "dirt" and fixes it, but again nothing changes.
Can anyone help me before I smash my computer into pieces and move to fedora?
boot partitioning usb mount
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56
add a comment |
Every USB stick I plug in is read-only and I cannot copy files to it.
Here's what I've tried so far.
- I've formated each one to either FAT32 or NTFS, quick and detailed
format in Disks and GParted - I've used GParted to format the stick and recreate the msdos
partition table layout. The device mounts fine, but won't copy files - I've tried using other USBs that already have files.
- I've tried to unmount, remount:
sudo chmod 777 /media/USER/USB_LABEL and
sudo mount -o remount,rw '/media/gaj/Working'
- I've changed permissions on all my media
There are no panic messsages when pluging in the USB:
dmesg | grep -i panic
- These are the dmesg log messages after pluging in and trying to copy to USB ( is the brand)
[ 4596.836206] scsi 4:0:0:0: Direct-Access Kingston DT 101 G2 PMAP PQ: 0 ANSI: 0 CCS
[ 4596.836620] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 4598.105667] sd 4:0:0:0: [sdb] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 4598.107900] sd 4:0:0:0: [sdb] Write Protect is off
[ 4598.107903] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4598.110120] sd 4:0:0:0: [sdb] No Caching mode page found
[ 4598.110123] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4598.140729] sdb: sdb1
[ 4598.146626] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 4598.372004] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
- I run fsck on my USB device /dev/sdb1, which finds some "dirt" and fixes it, but again nothing changes.
Can anyone help me before I smash my computer into pieces and move to fedora?
boot partitioning usb mount
Every USB stick I plug in is read-only and I cannot copy files to it.
Here's what I've tried so far.
- I've formated each one to either FAT32 or NTFS, quick and detailed
format in Disks and GParted - I've used GParted to format the stick and recreate the msdos
partition table layout. The device mounts fine, but won't copy files - I've tried using other USBs that already have files.
- I've tried to unmount, remount:
sudo chmod 777 /media/USER/USB_LABEL and
sudo mount -o remount,rw '/media/gaj/Working'
- I've changed permissions on all my media
There are no panic messsages when pluging in the USB:
dmesg | grep -i panic
- These are the dmesg log messages after pluging in and trying to copy to USB ( is the brand)
[ 4596.836206] scsi 4:0:0:0: Direct-Access Kingston DT 101 G2 PMAP PQ: 0 ANSI: 0 CCS
[ 4596.836620] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 4598.105667] sd 4:0:0:0: [sdb] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
[ 4598.107900] sd 4:0:0:0: [sdb] Write Protect is off
[ 4598.107903] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4598.110120] sd 4:0:0:0: [sdb] No Caching mode page found
[ 4598.110123] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 4598.140729] sdb: sdb1
[ 4598.146626] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 4598.372004] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
- I run fsck on my USB device /dev/sdb1, which finds some "dirt" and fixes it, but again nothing changes.
Can anyone help me before I smash my computer into pieces and move to fedora?
boot partitioning usb mount
boot partitioning usb mount
edited Mar 22 '17 at 7:02
Seanny123
191213
191213
asked Sep 18 '16 at 7:34
MookeyMookey
2,785112854
2,785112854
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56
add a comment |
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56
add a comment |
5 Answers
5
active
oldest
votes
I found this info. Try this: http://sharadchhetri.com/2013/12/19/how-to-fix-read-only-usb-pen-drive-in-ubuntu/
I do not know why every USB stick would be read-only? Hope it helps anyway.
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
add a comment |
My head hurts a little from all this, but hey turned out to be this bug. It's a shame to see the community take such a setback from the dismissal of Unity, and while they start over the giants like Microsoft and OS continue to progress down the road.
killall nautilus
Worked for me.
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
add a comment |
You should try formatting it with the Ext4
partition format. That should let Ubuntu at least read and write to the USB drive correctly.
add a comment |
This is how I fixed the permissions of my pen drive that 'suddenly' became readonly.
Switch to super user with:
sudo su -
Find in which directory the USB drive has been mounted by running:
df -Th
You should get a list of drives and your USB drive should be listed as:
/dev/sda1 fuseblk 15G 65M 15G 1% /media/someuser/myUsbDrive
Change the permissions of your USB pen drive (located at
/dev/sda1
) with:find /dev/sda1 -type f -exec chmod 666 {} ;
or with
find /dev/sda1 -type f -exec chmod 644 {} ;
Now your drive should be writable.
If the above doesn't work then change the permissions of the directories to make them writable:
find /dev/sda1 -type d -exec chmod 755 {} ;
add a comment |
For a FAT formatted drive the following should work.
Mounting this way in Ubuntu 18.10 is now deprecated, but still works. With a spot of luck your external drive will be mounted as the current user. Please note though that sdb1
may not be the name of your drive.
gvfs-mount -d /dev/sdb1
add a comment |
protected by Community♦ Jul 11 '18 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?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found this info. Try this: http://sharadchhetri.com/2013/12/19/how-to-fix-read-only-usb-pen-drive-in-ubuntu/
I do not know why every USB stick would be read-only? Hope it helps anyway.
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
add a comment |
I found this info. Try this: http://sharadchhetri.com/2013/12/19/how-to-fix-read-only-usb-pen-drive-in-ubuntu/
I do not know why every USB stick would be read-only? Hope it helps anyway.
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
add a comment |
I found this info. Try this: http://sharadchhetri.com/2013/12/19/how-to-fix-read-only-usb-pen-drive-in-ubuntu/
I do not know why every USB stick would be read-only? Hope it helps anyway.
I found this info. Try this: http://sharadchhetri.com/2013/12/19/how-to-fix-read-only-usb-pen-drive-in-ubuntu/
I do not know why every USB stick would be read-only? Hope it helps anyway.
answered Sep 18 '16 at 8:55
MarcellusMarcellus
18818
18818
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
add a comment |
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
Thanks, I got it fixed and this link will serve as future reference for potential USB issues. I'm accepting it.
– Mookey
Sep 19 '16 at 6:48
1
1
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
@Mookey link is broken :'(
– codeaviator
Jul 26 '17 at 11:00
1
1
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
Doesn't work. I'll just get used to throwing usb keys in the trash. Ubuntu = perfect paradox. Startup disk creator doesn't work with 100% reliability, so use Etcher instead which creates tons of partitions, then comes Ubuntu block size 512 error in gparted if you want to format it, so you have to dd if=/dev/zero... the usb drive, recreate, then permissions are broke, can't write. Linux distros are suffering from a segmentation problem that is unfortunately BAD news for Linux as a whole. Sorry but the switch to Linux has been very sad.
– wayofthefuture
Sep 9 '17 at 21:02
1
1
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
@codeaviator - try the Google web cache here: webcache.googleusercontent.com/…
– dmcquiggin
Oct 3 '17 at 19:23
add a comment |
My head hurts a little from all this, but hey turned out to be this bug. It's a shame to see the community take such a setback from the dismissal of Unity, and while they start over the giants like Microsoft and OS continue to progress down the road.
killall nautilus
Worked for me.
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
add a comment |
My head hurts a little from all this, but hey turned out to be this bug. It's a shame to see the community take such a setback from the dismissal of Unity, and while they start over the giants like Microsoft and OS continue to progress down the road.
killall nautilus
Worked for me.
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
add a comment |
My head hurts a little from all this, but hey turned out to be this bug. It's a shame to see the community take such a setback from the dismissal of Unity, and while they start over the giants like Microsoft and OS continue to progress down the road.
killall nautilus
Worked for me.
My head hurts a little from all this, but hey turned out to be this bug. It's a shame to see the community take such a setback from the dismissal of Unity, and while they start over the giants like Microsoft and OS continue to progress down the road.
killall nautilus
Worked for me.
answered Sep 9 '17 at 21:07
wayofthefuturewayofthefuture
2,8961810
2,8961810
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
add a comment |
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
Nice! This worked for me too.
– bfz
Sep 29 '17 at 9:18
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
I experienced this issue few times with fresh installations.. that worked perfectly and should be the answer.
– Interesting Knox
Oct 9 '17 at 11:03
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
Totally agree. These indefinite Unity "bugs" have reached a limit now, I'm switching to Ubuntu-MATE as early as possible.
– Prahlad Yeri
Dec 2 '17 at 21:40
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
I found this solution just to find out that I already up-voted and commented on it before. Its a shame we're not getting any fix for this, especially since its what we have out of the box in 16.04 LTS.
– bfz
Jan 24 '18 at 16:37
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
This is nuts. I'm sure there's a "technical" reason for this, but how a bug like this passed through QA and hasn't been fixed in over a year, is beyond me. I love Linux, but blatant issues like this, you just don't see on Windows.
– Dan Dascalescu
Sep 15 '18 at 1:50
add a comment |
You should try formatting it with the Ext4
partition format. That should let Ubuntu at least read and write to the USB drive correctly.
add a comment |
You should try formatting it with the Ext4
partition format. That should let Ubuntu at least read and write to the USB drive correctly.
add a comment |
You should try formatting it with the Ext4
partition format. That should let Ubuntu at least read and write to the USB drive correctly.
You should try formatting it with the Ext4
partition format. That should let Ubuntu at least read and write to the USB drive correctly.
answered Sep 27 '17 at 0:05
VarunAgrawalVarunAgrawal
30327
30327
add a comment |
add a comment |
This is how I fixed the permissions of my pen drive that 'suddenly' became readonly.
Switch to super user with:
sudo su -
Find in which directory the USB drive has been mounted by running:
df -Th
You should get a list of drives and your USB drive should be listed as:
/dev/sda1 fuseblk 15G 65M 15G 1% /media/someuser/myUsbDrive
Change the permissions of your USB pen drive (located at
/dev/sda1
) with:find /dev/sda1 -type f -exec chmod 666 {} ;
or with
find /dev/sda1 -type f -exec chmod 644 {} ;
Now your drive should be writable.
If the above doesn't work then change the permissions of the directories to make them writable:
find /dev/sda1 -type d -exec chmod 755 {} ;
add a comment |
This is how I fixed the permissions of my pen drive that 'suddenly' became readonly.
Switch to super user with:
sudo su -
Find in which directory the USB drive has been mounted by running:
df -Th
You should get a list of drives and your USB drive should be listed as:
/dev/sda1 fuseblk 15G 65M 15G 1% /media/someuser/myUsbDrive
Change the permissions of your USB pen drive (located at
/dev/sda1
) with:find /dev/sda1 -type f -exec chmod 666 {} ;
or with
find /dev/sda1 -type f -exec chmod 644 {} ;
Now your drive should be writable.
If the above doesn't work then change the permissions of the directories to make them writable:
find /dev/sda1 -type d -exec chmod 755 {} ;
add a comment |
This is how I fixed the permissions of my pen drive that 'suddenly' became readonly.
Switch to super user with:
sudo su -
Find in which directory the USB drive has been mounted by running:
df -Th
You should get a list of drives and your USB drive should be listed as:
/dev/sda1 fuseblk 15G 65M 15G 1% /media/someuser/myUsbDrive
Change the permissions of your USB pen drive (located at
/dev/sda1
) with:find /dev/sda1 -type f -exec chmod 666 {} ;
or with
find /dev/sda1 -type f -exec chmod 644 {} ;
Now your drive should be writable.
If the above doesn't work then change the permissions of the directories to make them writable:
find /dev/sda1 -type d -exec chmod 755 {} ;
This is how I fixed the permissions of my pen drive that 'suddenly' became readonly.
Switch to super user with:
sudo su -
Find in which directory the USB drive has been mounted by running:
df -Th
You should get a list of drives and your USB drive should be listed as:
/dev/sda1 fuseblk 15G 65M 15G 1% /media/someuser/myUsbDrive
Change the permissions of your USB pen drive (located at
/dev/sda1
) with:find /dev/sda1 -type f -exec chmod 666 {} ;
or with
find /dev/sda1 -type f -exec chmod 644 {} ;
Now your drive should be writable.
If the above doesn't work then change the permissions of the directories to make them writable:
find /dev/sda1 -type d -exec chmod 755 {} ;
edited May 15 '18 at 14:31
answered Dec 29 '17 at 16:32
consuelaconsuela
1535
1535
add a comment |
add a comment |
For a FAT formatted drive the following should work.
Mounting this way in Ubuntu 18.10 is now deprecated, but still works. With a spot of luck your external drive will be mounted as the current user. Please note though that sdb1
may not be the name of your drive.
gvfs-mount -d /dev/sdb1
add a comment |
For a FAT formatted drive the following should work.
Mounting this way in Ubuntu 18.10 is now deprecated, but still works. With a spot of luck your external drive will be mounted as the current user. Please note though that sdb1
may not be the name of your drive.
gvfs-mount -d /dev/sdb1
add a comment |
For a FAT formatted drive the following should work.
Mounting this way in Ubuntu 18.10 is now deprecated, but still works. With a spot of luck your external drive will be mounted as the current user. Please note though that sdb1
may not be the name of your drive.
gvfs-mount -d /dev/sdb1
For a FAT formatted drive the following should work.
Mounting this way in Ubuntu 18.10 is now deprecated, but still works. With a spot of luck your external drive will be mounted as the current user. Please note though that sdb1
may not be the name of your drive.
gvfs-mount -d /dev/sdb1
answered Mar 30 at 2:20
JackJack
1,13921522
1,13921522
add a comment |
add a comment |
protected by Community♦ Jul 11 '18 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?
for me diskpart in windows worked well.
– Brij Raj Kishore
Sep 18 '16 at 7:39
I think I did something right, cause now it works. I umnounted and did the step 8, and now every USB works. But there must have been a glitch, cause it had applied to all the USBs I have.
– Mookey
Sep 18 '16 at 8:56