Is there any chance this drive was inserted into a windows machine and not removed "safely"? If so it may be possible to mount it again in windows and then remove it properly to restore its read/write status. If not you could try using fsck.vfat in linux to try and repair.
On 11/05/14 20:02, Andrew Greig wrote: > On Sun, 2014-05-11 at 18:29 +1000, Jason White wrote: >> Andrew Greig <[email protected]> wrote: >>> Hi All, >>> >>> I recently copied some files onto a USB stick, but now, I cannot delete >>> them from the stick as the fs is readonly. I have tried to chmod, but >>> no luck. I have tried to chmod as roo, still no good. Then I >>> remembered that the fstab sometimes mounts removable devices readonly, >>> but the only drives referenced in fstab are the swap, / and /home >>> partitions. Where would I be able to change the permissions for this >>> drive, please? OpenSuse 13.1 >> It could be due to file system corruption. Have a look at your kernel logs to >> see whether there's an error message when you mount the file system. Also, >> when you run the mount command, do you get any error messages? > Hi Jason, > Thanks for the reply, here is the tail of dmesg > > [ 6797.283201] usb 1-1: USB disconnect, device number 2 > [ 6916.289618] usb 1-1: new high-speed USB device number 3 using > ehci-pci > [ 6916.423407] usb 1-1: New USB device found, idVendor=13fe, > idProduct=5500 > [ 6916.423424] usb 1-1: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 6916.423433] usb 1-1: Product: USB DISK 3.0 > [ 6916.423442] usb 1-1: Manufacturer: > [ 6916.423449] usb 1-1: SerialNumber: 90003658B035F027 > [ 6916.427618] usb-storage 1-1:1.0: USB Mass Storage device detected > [ 6916.427941] scsi3 : usb-storage 1-1:1.0 > [ 6917.432272] scsi 3:0:0:0: Direct-Access USB DISK 3.0 > PMAP PQ: 0 ANSI: 6 > [ 6917.434522] sd 3:0:0:0: Attached scsi generic sg2 type 0 > [ 6918.136636] sd 3:0:0:0: [sdb] 31555584 512-byte logical blocks: (16.1 > GB/15.0 GiB) > [ 6918.137786] sd 3:0:0:0: [sdb] Write Protect is off > [ 6918.137803] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00 > [ 6918.139522] sd 3:0:0:0: [sdb] No Caching mode page found > [ 6918.139542] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 6918.145683] sd 3:0:0:0: [sdb] No Caching mode page found > [ 6918.145702] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 6918.147147] sdb: sdb1 > [ 6918.151671] sd 3:0:0:0: [sdb] No Caching mode page found > [ 6918.151687] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 6918.151700] sd 3:0:0:0: [sdb] Attached SCSI removable disk > [ 6931.390696] FAT-fs (sdb1): Volume was not properly unmounted. Some > data may be corrupt. Please run fsck. > [ 6933.198312] FAT-fs (sdb1): error, fat_get_cluster: invalid cluster > chain (i_pos 0) > [ 6933.198326] FAT-fs (sdb1): Filesystem has been set read-only > [ 6964.187889] sdb: detected capacity change from 16156459008 to 0 > > The last line is a bit disturbing. I have read the man on fsck, but I > am struggling with the syntax. > > linux-sbl1:/home/andrewg # lsusb > Bus 001 Device 003: ID 13fe:5500 Kingston Technology Company Inc. > Bus 002 Device 002: ID 0c45:6321 Microdia > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > I do not want to run it in parallel with the root filesystem, I tried to > nominate /dev/sdb1 and when that didn't work tried /dev/USB0 ... > nothing. > > Could you recommend the syntax, please? > > Andrew > > > _______________________________________________ > luv-main mailing list > [email protected] > http://lists.luv.asn.au/listinfo/luv-main > _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
