Default mount options cause USB to mount in read-only

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












When I plug USB stick, it is mounted in read-only mode. dmesg output:



[189999.758776] sdc: sdc1
[189999.759811] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[190000.140329] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[190000.269130] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[190000.269135] FAT-fs (sdc1): Filesystem has been set read-only
[190217.318154] FAT-fs (sdc1): error, corrupted directory (invalid entries)


Basically, because of some minor error it remounts disk as read-only. I believe this is due to default mount options being errors=remount-ro. I want to change those default options, but I cannot find relevant configs.



I don't want to add this particular usb stick to /etc/fstab list or to mount it manually.










share|improve this question





















  • Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
    – sudodus
    Mar 29 at 9:51










  • @sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
    – Andrei R.
    Mar 29 at 10:06










  • Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
    – sudodus
    Mar 29 at 11:06











  • @sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
    – Andrei R.
    Mar 30 at 3:30










  • You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
    – sudodus
    Mar 30 at 5:33














up vote
0
down vote

favorite












When I plug USB stick, it is mounted in read-only mode. dmesg output:



[189999.758776] sdc: sdc1
[189999.759811] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[190000.140329] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[190000.269130] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[190000.269135] FAT-fs (sdc1): Filesystem has been set read-only
[190217.318154] FAT-fs (sdc1): error, corrupted directory (invalid entries)


Basically, because of some minor error it remounts disk as read-only. I believe this is due to default mount options being errors=remount-ro. I want to change those default options, but I cannot find relevant configs.



I don't want to add this particular usb stick to /etc/fstab list or to mount it manually.










share|improve this question





















  • Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
    – sudodus
    Mar 29 at 9:51










  • @sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
    – Andrei R.
    Mar 29 at 10:06










  • Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
    – sudodus
    Mar 29 at 11:06











  • @sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
    – Andrei R.
    Mar 30 at 3:30










  • You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
    – sudodus
    Mar 30 at 5:33












up vote
0
down vote

favorite









up vote
0
down vote

favorite











When I plug USB stick, it is mounted in read-only mode. dmesg output:



[189999.758776] sdc: sdc1
[189999.759811] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[190000.140329] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[190000.269130] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[190000.269135] FAT-fs (sdc1): Filesystem has been set read-only
[190217.318154] FAT-fs (sdc1): error, corrupted directory (invalid entries)


Basically, because of some minor error it remounts disk as read-only. I believe this is due to default mount options being errors=remount-ro. I want to change those default options, but I cannot find relevant configs.



I don't want to add this particular usb stick to /etc/fstab list or to mount it manually.










share|improve this question













When I plug USB stick, it is mounted in read-only mode. dmesg output:



[189999.758776] sdc: sdc1
[189999.759811] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[190000.140329] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[190000.269130] FAT-fs (sdc1): error, corrupted directory (invalid entries)
[190000.269135] FAT-fs (sdc1): Filesystem has been set read-only
[190217.318154] FAT-fs (sdc1): error, corrupted directory (invalid entries)


Basically, because of some minor error it remounts disk as read-only. I believe this is due to default mount options being errors=remount-ro. I want to change those default options, but I cannot find relevant configs.



I don't want to add this particular usb stick to /etc/fstab list or to mount it manually.







usb mount 17.10






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 29 at 9:48









Andrei R.

7817




7817











  • Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
    – sudodus
    Mar 29 at 9:51










  • @sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
    – Andrei R.
    Mar 29 at 10:06










  • Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
    – sudodus
    Mar 29 at 11:06











  • @sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
    – Andrei R.
    Mar 30 at 3:30










  • You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
    – sudodus
    Mar 30 at 5:33
















  • Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
    – sudodus
    Mar 29 at 9:51










  • @sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
    – Andrei R.
    Mar 29 at 10:06










  • Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
    – sudodus
    Mar 29 at 11:06











  • @sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
    – Andrei R.
    Mar 30 at 3:30










  • You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
    – sudodus
    Mar 30 at 5:33















Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
– sudodus
Mar 29 at 9:51




Have you tried to check/repair the FAT file system? See this link, Repair the partition table and file system of a pendrive
– sudodus
Mar 29 at 9:51












@sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
– Andrei R.
Mar 29 at 10:06




@sudodus, this happens often - I assume its windows messing up the file system. And I don't want to do it every time by hand
– Andrei R.
Mar 29 at 10:06












Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
– sudodus
Mar 29 at 11:06





Does it happen also when you eject the USB drive safely (alias unmount it)? In that case, maybe you have no real choice. But you can create (if necessary get some help to create) a shellscript, that will run all the commands for you, so it will be rather convenient.
– sudodus
Mar 29 at 11:06













@sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
– Andrei R.
Mar 30 at 3:30




@sudodus, no, drives may be ejected in unsafe manner. I want issue to be resolved once, without need to run scripts or whatsoever.
– Andrei R.
Mar 30 at 3:30












You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
– sudodus
Mar 30 at 5:33




You can create a bug report at Launchpad, launchpad.net and wait for a developer to fix the problem. (But if the linux developers think that it is caused by a bug in Windows, it will not be fixed.)
– sudodus
Mar 30 at 5:33















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020207%2fdefault-mount-options-cause-usb-to-mount-in-read-only%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020207%2fdefault-mount-options-cause-usb-to-mount-in-read-only%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491