I have a problem USB Flash Drive that under MATE is displaying the incorrect volume label (it says it’s RED-JUMP-Drive but is supposed to be Sega-Blue)and I can’t copy any files to it or create a folder or delete files. It does not have this problem in Windows and if I boot Mint Linux from a Jump Drive it also does not have this problem, Only under Ubuntu MATE does it have this problem.
I was able to format it so now I have to recover all the data that was on it.
I tried doing this
sudo dosfsck -a /dev/sdc1
and this
sudo hdparm -r0 /dev/sdc1
dmesg | grep sdc will show you how the drive is mounted, RO read only or RW read write. But … if you formatted the drive, how will you be able to recover data from it?
I typed dmesg | grep sdc
in a terminal and it did not do anything, it did not display anything and went back to the prompt
If I type just grep sdc
the prompt does not come back as if it locked up and if I try to close the terminal it says
There is still a process running in this terminal. Closing the terminal will kill it.
If I type just dsesg
it displays a whole window full of test I can’t read or understand.
As far as recovering the data, I backed it up first and the restored it under Windows 7.
If you type dmesg in the terminal you should get a long listing. The grep
subsets that listing for sdc (since you wrote earlier the usb drive was
sdc). If your drive is sdb then grep for sdb. If you plug in a usb drive,
dmesg will show the size of the drive and if it was able to open is as RW.
Example, I plugged in my usb drive and dmesg contains: … it found a drive
8 GB in size, the write protect is off (that means RW) and it has only one
partition (sdc is the device, sdc1 is the partition)
I managed to some how do a fsck on the drive and it said it had a dirty bit because it was not unmounted properly so I told it to remove the dirty bit and then it checked the drive and said something about the fat being corrupt and asked which back up fat to use I chose 1 and it did it’s thing and I was able to change the volume label but it still is read only under Ubuntu MATE only and Not under Windows 7 or if I boot Linux Mint from a jump drive.
Now when I try to do a fsck on it it fails with this message
/dev/sda5 is mounted.
e2fsck: Cannot continue, aborting.
I’m Not trying to fsck on /dev/sda5, I’m trying to fsck the jump drive on /dev/sdj1 or maybe it’s
/mnt/usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:0-part1
because if I do a
cd /mnt/usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:0-part1 it changes to the jump drive.
So the usb drive is sdj … when it mounts it, can you show the location? type df to see the mount point. Change directory into that mount point and type, touch bob it should create a file called bob with zero bytes. In my case it mounts it in /media/pavlos/something (pavlos is the user, something is the label of the usb drive)
I found out the only way I can write to the drive is to launch a file manager as a super user by typing sudo caja or sudo nautilus and than clicking on file system and then mnt where I can then see the drive and create folders or write files to it or delete files from it. If it check the properties, permissions it shows it’s owned by root and if I try to change it to any other user it won’t let me, even if I log on as a super user in a terminal window by typing su and and launch nautilus I get this error message
Sorry, could not change the owner of “usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:0-part1”: Error setting owner: Operation not permitted
This is what I get when I type
touch bob ; ls -l
touch: cannot touch ‘bob’: Permission denied
total 240
drwxr-xr-x 3 root root 16384 Jun 10 20:28 apps
-rwxr-xr-x 1 root root 44 Aug 20 2017 BLUE LED
drwxr-xr-x 2 root root 16384 Jun 19 11:00 Created as ROOT
drwxr-xr-x 2 root root 16384 Jun 19 10:03 Created in Linux Mint
drwxr-xr-x 3 root root 16384 Apr 28 05:30 DCIM
drwxr-xr-x 2 root root 16384 May 4 01:46 Games
drwxr-xr-x 5 root root 16384 Jun 1 20:13 gxgeo
drwxr-xr-x 5 root root 16384 Jun 1 20:24 hugo
-rwxr-xr-x 1 root root 12000 May 3 18:25 ndebug.log
-rwxr-xr-x 1 root root 544 May 3 17:42 nincfg.bin
drwxr-xr-x 2 root root 16384 Jun 19 12:25 On Hold
drwxr-xr-x 9 root root 16384 May 30 16:23 SEGA
drwxr-xr-x 2 root root 16384 May 28 22:28 System Volume Information
drwxr-xr-x 6 root root 16384 May 30 16:42 TG-16
drwxr-xr-x 5 root root 16384 May 30 16:06 wiisxr
taslim@Taslims-Ubuntu-Mate:/mnt/usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=97aecfea-8188-4561-8eb3-317fdb9f9d32 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=e7c0752c-cf7d-469e-ac77-e4d680ca094b none swap sw 0 0
# swap was on /dev/sdb3 during installation
UUID=2e691c3d-e984-451b-8bcd-39786e538cbe none swap sw 0 0
/dev/disk/by-id/usb-Initio_HM160HC_0000000000000000W-0:0-part1 /mnt/usb-Initio_HM160HC_0000000000000000W-0:0-part1 auto nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-name=160GBUSB 0 0
/dev/disk/by-id/usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:0-part1 /mnt/usb-SanDisk_Cruzer_Glide_4C530001010701113445-0:0-part1 auto nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-name=SEGA-BLUE 0 0
I wrote earlier that usb drives usually mount under /media and the user’s name, eg /media/pavlos/usbdrive. I have no idea who added the mount line to /etc/fstab, that dictates the usb drive be mounted under /mnt But I see 2 swap files (kinda strange, one reference to sda6 (correct) but also to sdb3 which does not exist in blkid). Earlier, you showed that the usb drive appeared as sdj, now it appears as sde, formatted as VFAT. There is also a 160 GB usb-Initio which I do not see in the blkid listing.
You could try, sudo chmod 777 /mnt that will open /mnt to be RW by everyone and this may help to read/write files in there as a normal user. To revert back, use sudo chmod 755 /mnt
I think I fixed it, I deleted the line in the fstab file that refereed to the Jump Drive I was having trouble with and now I can write to it again without having to open a file browser as a super user.
see, it no longer says root for the owner
drwxr-xr-x 3 taslim taslim 16384 Jun 10 20:28 apps
-rw-r–r-- 1 taslim taslim 44 Aug 20 2017 BLUE LED
-rw-r–r-- 1 taslim taslim 0 Jun 20 22:31 bob
drwxr-xr-x 2 taslim taslim 16384 Jun 19 11:00 Created as ROOT
drwxr-xr-x 2 taslim taslim 16384 Jun 19 10:03 Created in Linux Mint
drwxr-xr-x 3 taslim taslim 16384 Apr 28 05:30 DCIM
drwxr-xr-x 2 taslim taslim 16384 Jun 20 21:58 fixed it
drwxr-xr-x 2 taslim taslim 16384 May 4 01:46 Games
drwxr-xr-x 5 taslim taslim 16384 Jun 1 20:13 gxgeo
drwxr-xr-x 5 taslim taslim 16384 Jun 1 20:24 hugo
-rw-r–r-- 1 taslim taslim 12000 May 3 18:25 ndebug.log
-rw-r–r-- 1 taslim taslim 544 May 3 17:42 nincfg.bin
drwxr-xr-x 2 taslim taslim 16384 Jun 19 12:25 On Hold
drwxr-xr-x 9 taslim taslim 16384 May 30 16:23 SEGA
drwxr-xr-x 2 taslim taslim 16384 May 28 22:28 System Volume Information
drwxr-xr-x 6 taslim taslim 16384 May 30 16:42 TG-16
drwxr-xr-x 5 taslim taslim 16384 May 30 16:06 wiisxr
it also changed it’s mount point to
/media/taslim/SEGA-BLUE$
I did make a back up of the fstab file just in case I screwed something up by doing that.