USB not getting mounted due to Read-Only


up vote
0
down vote
favorite
Here is the image:
I have tried the following command but got nothing:
sudo hdparm -r0 /dev/sde
/dev/sde:
setting readonly to 0 (off)
readonly = 0 (off)
Kindly, help me in this situation.
**Edited output of the command dmesg -w
Here is the output Gist
16.04 usb mount read-only
 |Â
show 1 more comment
up vote
0
down vote
favorite
Here is the image:
I have tried the following command but got nothing:
sudo hdparm -r0 /dev/sde
/dev/sde:
setting readonly to 0 (off)
readonly = 0 (off)
Kindly, help me in this situation.
**Edited output of the command dmesg -w
Here is the output Gist
16.04 usb mount read-only
It would help if you add the output ofdmesg -w
when you plug the usb
â Katu
Mar 9 at 14:06
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
I didn't explain correctly, sorry.dmesg
shows the kernel messages.dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, typedmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look atfdisk
,gparted
or others.
â Katu
Mar 11 at 9:16
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Here is the image:
I have tried the following command but got nothing:
sudo hdparm -r0 /dev/sde
/dev/sde:
setting readonly to 0 (off)
readonly = 0 (off)
Kindly, help me in this situation.
**Edited output of the command dmesg -w
Here is the output Gist
16.04 usb mount read-only
Here is the image:
I have tried the following command but got nothing:
sudo hdparm -r0 /dev/sde
/dev/sde:
setting readonly to 0 (off)
readonly = 0 (off)
Kindly, help me in this situation.
**Edited output of the command dmesg -w
Here is the output Gist
16.04 usb mount read-only
16.04 usb mount read-only
edited Mar 10 at 5:07
asked Mar 9 at 13:13
Jaffer Wilson
580721
580721
It would help if you add the output ofdmesg -w
when you plug the usb
â Katu
Mar 9 at 14:06
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
I didn't explain correctly, sorry.dmesg
shows the kernel messages.dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, typedmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look atfdisk
,gparted
or others.
â Katu
Mar 11 at 9:16
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31
 |Â
show 1 more comment
It would help if you add the output ofdmesg -w
when you plug the usb
â Katu
Mar 9 at 14:06
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
I didn't explain correctly, sorry.dmesg
shows the kernel messages.dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, typedmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look atfdisk
,gparted
or others.
â Katu
Mar 11 at 9:16
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31
It would help if you add the output of
dmesg -w
when you plug the usbâ Katu
Mar 9 at 14:06
It would help if you add the output of
dmesg -w
when you plug the usbâ Katu
Mar 9 at 14:06
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
I didn't explain correctly, sorry.
dmesg
shows the kernel messages. dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, type dmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look at fdisk
, gparted
or others.â Katu
Mar 11 at 9:16
I didn't explain correctly, sorry.
dmesg
shows the kernel messages. dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, type dmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look at fdisk
, gparted
or others.â Katu
Mar 11 at 9:16
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
You can try restoring the USB drive to a standard format. There is a utility called mkusb
. Look at this link. Add the ppa, update apt and then sudo apt install mkusb
and when done, run mkusb
.
Step by step instructions. Run these commands:
sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
mkusb
and select option d see below:
if prompted for root password, enter it. Follow the insturctions on the screen:
and then select the Restore to a Standard Storage Device option (WARNING: you will loose all your data on the USB drive):
That should do it.
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned byroot
and after I changed the owner/group to my user name, the issue went away. In the terminal, type:ls /media/$USER -dl
and for owner / group, see if it saysroot root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.
â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.
â marko
Mar 10 at 7:28
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can try restoring the USB drive to a standard format. There is a utility called mkusb
. Look at this link. Add the ppa, update apt and then sudo apt install mkusb
and when done, run mkusb
.
Step by step instructions. Run these commands:
sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
mkusb
and select option d see below:
if prompted for root password, enter it. Follow the insturctions on the screen:
and then select the Restore to a Standard Storage Device option (WARNING: you will loose all your data on the USB drive):
That should do it.
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned byroot
and after I changed the owner/group to my user name, the issue went away. In the terminal, type:ls /media/$USER -dl
and for owner / group, see if it saysroot root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.
â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.
â marko
Mar 10 at 7:28
 |Â
show 1 more comment
up vote
0
down vote
You can try restoring the USB drive to a standard format. There is a utility called mkusb
. Look at this link. Add the ppa, update apt and then sudo apt install mkusb
and when done, run mkusb
.
Step by step instructions. Run these commands:
sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
mkusb
and select option d see below:
if prompted for root password, enter it. Follow the insturctions on the screen:
and then select the Restore to a Standard Storage Device option (WARNING: you will loose all your data on the USB drive):
That should do it.
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned byroot
and after I changed the owner/group to my user name, the issue went away. In the terminal, type:ls /media/$USER -dl
and for owner / group, see if it saysroot root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.
â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.
â marko
Mar 10 at 7:28
 |Â
show 1 more comment
up vote
0
down vote
up vote
0
down vote
You can try restoring the USB drive to a standard format. There is a utility called mkusb
. Look at this link. Add the ppa, update apt and then sudo apt install mkusb
and when done, run mkusb
.
Step by step instructions. Run these commands:
sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
mkusb
and select option d see below:
if prompted for root password, enter it. Follow the insturctions on the screen:
and then select the Restore to a Standard Storage Device option (WARNING: you will loose all your data on the USB drive):
That should do it.
You can try restoring the USB drive to a standard format. There is a utility called mkusb
. Look at this link. Add the ppa, update apt and then sudo apt install mkusb
and when done, run mkusb
.
Step by step instructions. Run these commands:
sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
mkusb
and select option d see below:
if prompted for root password, enter it. Follow the insturctions on the screen:
and then select the Restore to a Standard Storage Device option (WARNING: you will loose all your data on the USB drive):
That should do it.
edited Mar 10 at 5:28
answered Mar 10 at 5:19
marko
4557
4557
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned byroot
and after I changed the owner/group to my user name, the issue went away. In the terminal, type:ls /media/$USER -dl
and for owner / group, see if it saysroot root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.
â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.
â marko
Mar 10 at 7:28
 |Â
show 1 more comment
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned byroot
and after I changed the owner/group to my user name, the issue went away. In the terminal, type:ls /media/$USER -dl
and for owner / group, see if it saysroot root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.
â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.
â marko
Mar 10 at 7:28
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I got error: Error gist. Kindly, let me know what I can do.
â Jaffer Wilson
Mar 10 at 6:31
I might know what's happening. in
/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned by root
and after I changed the owner/group to my user name, the issue went away. In the terminal, type: ls /media/$USER -dl
and for owner / group, see if it says root root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.â marko
Mar 10 at 6:43
I might know what's happening. in
/media
there should be a directory with your user name. In the past I had similar issues and I found that the directory was owned by root
and after I changed the owner/group to my user name, the issue went away. In the terminal, type: ls /media/$USER -dl
and for owner / group, see if it says root root
and if so, I believe that's the issue. You can try changing the permissions to your user name and try it again.â marko
Mar 10 at 6:43
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
How I can change the permissions ? Please guide me.
â Jaffer Wilson
Mar 10 at 6:58
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I have tried changing the permissions. See the gist of error I have got.
â Jaffer Wilson
Mar 10 at 7:02
I just noticed this,
/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.â marko
Mar 10 at 7:28
I just noticed this,
/dev/sdd1: No such file or directory
and to me this indicates an issue with your partition table on the disk. Are you experienced with GParted? You can try creating a new partition table: Device->Create Partition Table and then create different partitions. Select the msdos version. You will lose all your data.â marko
Mar 10 at 7:28
 |Â
show 1 more comment
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1013398%2fusb-not-getting-mounted-due-to-read-only%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
It would help if you add the output of
dmesg -w
when you plug the usbâ Katu
Mar 9 at 14:06
sure.. Let me edit the output of the command.
â Jaffer Wilson
Mar 10 at 5:03
I didn't explain correctly, sorry.
dmesg
shows the kernel messages.dmesg -w
leaves these open and live updates. What it might help you is to disconnect the USB, typedmesg -w
and then connect the USB. You will see new messages appearing related to your USB and you might see an error message if the device is damaged. Ubuntu configuration often states that if there are errors reading a system, is mounted read only and this is what I was trying to figure out. If you don't mind losing the information in the drive, reformatting it may help. Have a look atfdisk
,gparted
or others.â Katu
Mar 11 at 9:16
@Katu Thank you for the explanation. But what I should do if my pen drive is corrupted or damaged? Please can you help me in making it operational again?
â Jaffer Wilson
Mar 12 at 5:06
If it's the /dev/sdd device that your dmesg shows, it doesn't look damaged. Try help.ubuntu.com/community/DataRecovery
â Katu
Mar 12 at 8:31