USB & SD Devices Stuck on Read Only

[NeMesiS34]

Hey everyone...
I converted from Windows to Linux about a year ago and never looked back.
I've been quite happy with using Kali Linux as my primary operating system.
Usually a quick Google search had always turned up solutions to my problems.
However I haven't been able to find a permanent fix to my current situation.

USB Devices
When I insert my USB flash drives it keeps mounting as a read only file system.
I ran the following "mount -o rw,remount /media/root/SanDisk" Sometimes it works...
Sometimes it doesn't or only momentarily but can never get it to work permanently.

SD Device
I have the same problem with mounting SD devices becoming read only.
But another odd thing that happens, is that the SD device would unmount.
Upon trying to remount I get the following message "No object for D-Bus interface"
Only way I've been able to fix this is to reboot every time it occurs...

I'm stumped as to why this is happening, Its only been doing this for the past day or so.
Its becoming quite a problem for me..

Thanks in advance for any advice, NeMesiS

[pyth0n]

Boot to kali desktop (assuming you are running as root) and open the terminal, post the output of:

fdisk -l

Last character lowercase"L"

Then try and mount all drives in fstab, type

mount -a

You then need to look at the kernel messages, so type dmesg scroll to the bottom and paste output
of dmesg.

If a drive has been mounted as read-only its usually due to corruption and you may need to run
fsck, the version depends on what filesystem you choose for / and /home e.g. ext4 or etc3 etc
Post this back so someone can help further

[NeMesiS34]

The following commands solved the read only issue...
"umount /media/root/usbdevice"
"dosfsck -a /dev/sdc1"

However I'm still having trouble mounting the SD card...
"No object for D-Bus interface"

[pyth0n]

OK, never use a weak filesystem like DOS or FAT32 or NTFS unless you have some special need to share data
with windows. These filesystems will always fragment but, the side effects of wear and tear mean your avaerage
hard drive only lasts about 3 or 4 years.
I have an old PC with HD formatted with ext3 in 2001, and it still runs, fragmentation in 6 years was a mere 1.6%
and its even lower with ext4.

The SD card the same still applies.
Check the output from dmesg, then insert the SD card, look at dmesg messages and post any new lines.
SD cards are still detected as a block device by the linux kernel so with SD card inserted post the
output of:

blkid

My Raspberry Pi SD card is detected as /dev/mmcblk0 with 2 partitions:

pi@Bianka ~ $ sudo blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="993B-8922" TYPE="vfat"
/dev/mmcblk0p2: UUID="fc254b57-8fff-4f96-9609-ea202d871acf" TYPE="ext4"

You may see something similar or just a standard /dev/sdx enumeration.

The other thing to rememeber is that Gnome 3, the kali desktop uses the gnome virtual
filesystem, gvfs so try unmounting gvfs first:

umount -fl /root.gvfs

Unplug the sd card wait a couple of seconds and then reinsert it.
Try:

mount -a

and see if you have access to the card

[duxim]

However I'm still having trouble mounting the SD card...
"No object for D-Bus interface"

I have a similar problem in another Linux distro (slackware).
see and check
/etc/fstab
if you have in it (your SD card) and delete it
also check with gparted if it see your SD card an read this solution
https://bbs.archlinux.org/viewtopic.php?id=140456

[NeMesiS34]

Thanks for the replies...
I'll try your suggestions once I get my SD card back.
My RPi2 is being well used as my father is catching up on a couple of movies.

So yea obviously I've been playing around with the SD card for my 1st RPi2 I just got.
Was still able to use gparted to format the card, I think when I used ext4 it was mountable again.
When I build the SD card using "dd" command, I still cannot mount the card afterwards (not sure what FS it uses)
I quickly moved onto Berryboot, where I needed to format as FAT and transfer files.
Again I could format with gparted but the only way I could transfer the files across,
was to use the SD card in my camera and connected it to my laptop via USB.
I've achieved what I wanted with the SD card but I still will try out the suggestions.

Thanks again, NeMesiS

[pyth0n]

Sorry did not realise you were running Kali on a Raspberry Pi 2.
The Pi SD card has two partitions VFAT and ext4.

To run a file filesystem check you need to unmount the card, place it in your camera,
connect it to your laptop and then run

fdisk -l

or sudo fdisk -l if the distro on your laptop is not Kali.
The device may be listed differently in the output from fdisk but the command is

fdisk.ext4 /dev/sdax

Replacing sdax with coorect device and partition. As the SD has 2 partitions, it may
be listed as /dev/sdb1 and /dev/sdc1 (as its now usb storage) or maybe still as
/dev/mmcblk0p1 and p2. Ext4 is pretty robust but the FAT partition will always corrupt if
Pi is not shut down properly and your RPi will not boot.

I'm running the opposite have kali on my laptop and testing the security of my Raspberry Pi
Model B.
Post output of fdisk -l if unsure, but think you will work this out.

[NeMesiS34]

This is getting confusing...
I got my Laptop running Kali 2 and is where I'm getting the error message.
I was trying to build SD card for my RPi2... (I now have Kali 2 on RPi but yet to use it)

fdisk -l result (SD card in slot)

/dev/mmcblk0p1 2048 262143 260096 127M e W95 FAT16 (LBA)
/dev/mmcblk0p2 262144 62521343 62259200 29.7G 83 Linux

fdisk -l result (SD card in camera)

/dev/sdc1 2048 262143 260096 127M e W95 FAT16 (LBA)
/dev/sdc2 262144 62521343 62259200 29.7G 83 Linux

blkid results: (SD card in slot)

/dev/mmcblk0: PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" UUID="01EE-5888" TYPE="vfat"
/dev/mmcblk0p2: LABEL="berryboot" UUID="28dd40df-b44a-4980-b611-a1fe8fb84ad1" TYPE="ext4"

blkid results: (SD card in camera)

/dev/sdc1: SEC_TYPE="msdos" UUID="01EE-5888" TYPE="vfat"
/dev/sdc2: LABEL="berryboot" UUID="28dd40df-b44a-4980-b611-a1fe8fb84ad1" TYPE="ext4"

dmesg result: (SD card in slot)

mmc0: cannot verify signal voltage switch
mmc0: new ultra high speed SDR104 SDHC card at address 0001
* Driver 'mmcblk' needs updating - please use bus_type methods
mmcblk0: mmc0:0001 00000 29.8 GiB
mmcblk0: p1 p2
mmcblk0: p1 p2

dmesg result: (SD card in camera)

** FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
EXT4-fs (sdc2): 4 orphan inodes deleted
EXT4-fs (sdc2): recovery complete
EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)

conclusion:

With the SD in the camera I am able to mount all partitions.
* Driver 'mmcblk' needs updating - please use bus_type methods
** Volume was not properly unmounted. Some data may be corrupt.
Are these errors the cause of the problem?

umount gvfs:

I tried "umount -fl /root.gvfs" but can't seem to find the mount point
"umount: /root.gvfs: mountpoint not found"

EDIT: by "SD card in slot" i mean in my laptops card reader and by,
"SD card in camera" is the sd card in the camera then connected to PC via usb