PDA

View Full Version : My USB memory stick has become read only



code_astronomer
19th April 2006, 10:08 AM
hi,

I hope someone can help me...I was copying some files onto my USB Memory stick and something went wrong and it told me it couldn't unmount (perhaps I removed it before it was fully unmounted?) but now I can't delete files because it says it is read only.

I tried to delete them and a deleting box popups up but makes no progress...eventually it just dies on me.

Where is it defined that it is read only?? how can I change that? If I go to permissions in properties, it says the permissions can't be determined...
I'm a bit stuck with this.

Salamandra
19th April 2006, 10:39 AM
Have you tried to edit /etc/fstab and change the permissions there?

code_astronomer
19th April 2006, 11:00 AM
the memory stick doesn't appear in fstab :S
Is there another file that it could be defined in? I'm sure I edited it once before when I was using FC4...but can't remember where that was.

blue13130
19th April 2006, 03:59 PM
mount your USB key then using the terminal cd to the directory and use the command
$ ll
to display the files and their permissions. Post the output here so we can see what is going on.

code_astronomer
19th April 2006, 07:21 PM
hi,
output is below...

for /media/USB MEMORY/


$ ls -al
total 28
drwxr-xr-x 3 code_astro root 16384 Jan 1 1970 .
drwxr-xr-x 3 root root 4096 Apr 19 11:47 ..
drwxr-xr-x 19 code_astro root 4096 Apr 17 16:27 College


for /media/


$ ls -al
total 32
drwxr-xr-x 3 root root 4096 Apr 19 11:47 .
drwxr-xr-x 23 root root 4096 Apr 19 08:07 ..
drwxr-xr-x 3 code_astro root 16384 Jan 1 1970 USB MEMORY


The thing that hits me immedietly is the date...Jan 1 1970?

if I try and delete a file (through nautilus) I get:

"/media/USB...[whatever filename here]" cannot be deleted because it is on a read-only disk.

the scary thing is, I'm getting corrupt filenames such as:


^Hw=^Bl.^O⌐/
╞x▐┘aj═.^W^Fv
^^Ry`z^^9.πH
πc)╓╨.n^Jf
φ'^J^TA^X₧.b┤^D

code_astronomer
19th April 2006, 08:00 PM
Just watched syslog while trying to delete from my USB stick...(tail -f /var/log/messages)
and I get the following!:


Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f60e)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fd1e)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f402)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000eedb)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f103)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fb33)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f1d0)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f6dc)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f42d)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f36f)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f91c)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f0a2)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f712)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f89a)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fa2a)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fada)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fe9d)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f7d9)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f62f)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f67b)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fdc1)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fc4c)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fb35)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000ff9d)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000f449)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: invalid access to FAT (entry 0x0000fe20)
Apr 19 19:58:19 localhost kernel: FAT: Filesystem panic (dev sdb1)
Apr 19 19:58:19 localhost kernel: fat_get_cluster: invalid cluster chain (i_pos 0)

and it goes on....

blue13130
20th April 2006, 01:01 AM
I am not sure what is going on, perhaps try deleting everything from the terminal if possible
$ cd /media/USB MEMORY/
$ sudo rm -fr *

Perhaps you can try formatting it on another machine or windows and see what happens. Other than that I am out of ideas.

dshaw256
20th April 2006, 01:07 AM
It does look like the stick's file system got corrupted. blue13130 says to try formatting on another machine or Windows... Just for my enlightenment, how would one reformat the stick with a FAT file system from Linux?

theophilusmouss
20th April 2006, 01:15 AM
I was at my mom's a couple weeks ago and had what amounts to the exact same problem. Trying to transfer files from a windows laptop to a windows desktop, windows error mesg. said cannot write to a read-ony volume. The advice I got from another forum was...

Some usb thumbdrives have a write-protect switch on them somewhere, check to make sure it's set correctly.

Try defragging and scanning for bad sectors, sometimes that plays havvoc with the file tables.

Get a new usb drive and get as moch of your info of the old one that you can before it finishes dying.

The solution for my mother ended up being getting a new one. The drive that had the problem was a 128MB Dell that she got real cheap from school.

Hope this helps. (hope it's just a bumped write-protect switch)

Omega Blue
20th April 2006, 09:04 AM
Test your USB drive on another computer. If it is still read only, it's the stick. If you can write to it, it maybe a problem with the configuration on your computer.

code_astronomer
20th April 2006, 10:28 AM
Hi and thank you everyone for your replies.
I was hoping there was a way to get around this without having to use Windows, but I will have to format it in Windows I think. This happened to another USB key. I'm sure it was because I had pulled it out after unmounting and it hadn't quite finished.

I think I might attempt to write a program that displays a message until the key has been fully unmounted to prevent this happening in the future...It's difficult for me to see the light on my key to find out when it has been unmounted completely.

Thanks everyone :)

Lluisanunez
20th April 2006, 11:07 AM
Something similar happened to me with a USB external disk. It did'nt become read-only but I couldn't write to it because it said disk was full (it wasn't). I resisted the Windows solution, installed QTparted and reformated it to VFAT

code_astronomer
20th April 2006, 05:31 PM
hi Lluisanunez...I had that happen to a USB stick too once. I gave it to my brother to format on his Windows PC. However I never managed to get back some of the memory on that stick!

I'll have a look at QT parted...but it might be easiest for me to just give it to my brother to format.

Lluisanunez
20th April 2006, 06:14 PM
yum install qtparted
it's very nice :)
then you can install puppy linux in it and give it to your brother to try

Arntech1331
6th January 2013, 09:03 AM
Not sure if this helps but maybe it mught jog someones mind for an answer.

This happened to mewhile using a USB SD card reader.

I created a kubuntu install stick with Universal USB Installer 1.9.2.1 all went well Win 8
When I went to add more files Ubuntu 12.10 to my 8 gig class 10 sd card it came up read only.
Went back to Win 8 same thing read only. Looked for regedit lines from on solution my reg had no entry.
Checked my lock switch and moved it from the position it was allways in to the other position and TADA.
Added files went to Ubuntu 12.10 and added files.
Here is where it gets stranger. I decide to install Kubuntu 12.4.1 so I go to format drive to recreate a install stick with Kubuntu 12.4.1. I try Universal USB Installer 1.9.2.1 with erase disk checked. No go read only again. Try to format Win 8 and no go. Try to format gpart no go. Back to Win 8 change advanced sharing and add my user and select full access for it and the everyone user. Try to format and TADA ! It wipes and I create a Kubuntu 12.4.1 install stick. I install Kubuntu and decide I need a few more files from Win 7 Laptop and no go READ ONLY ! Try everything above again and no go. Frustrated ~~
I removed the SD card and plugged it in the Win 7 Laptop card reader slot and it was a normal working normal and has ever since. If I put it in the USB unit it still comes up Read only.

Hope this Helps

Arntech1331

Blue Marble
It's where we Live !

glennzo
6th January 2013, 11:01 AM
Ancient tread. Closed.