Surely there are many many questions on this topic, But I've a reason to believe that this is different.
Things that I've already tried
- Formatting from Nautilus
- Formatting from Gnome-Disks
- Creating a new partition table from Gparted
- Formatting from Gparted
chown
to get ownership- remounting with
rw
- forcefully remounting wit
ntfs-3g
outputs (mounting)
$ sudo mount -o remount,rw /dev/sdc1
mount: cannot remount /dev/sdc1 read-write, is write-protected
$ sudo mount -o remount,rw '/media/sumeet/4CCF-3379'
mount: cannot remount /dev/sdc1 read-write, is write-protected
$ sudo mount -t ntfs-3g -o uid=$(id -u) /dev/sdc1 /media/sumeet/4CCF-3379
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
Chown
$ sudo chown -R sumeet:sumeet /media/sumeet/4CCF-3379
chown: changing ownership of '/media/sumeet/4CCF-3379/LOST.DIR/134797': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/LOST.DIR': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/.android_secure': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/.cache/tb': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/.cache': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/.log': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/app': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/music': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/video': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/photo': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/misc': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/backup': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/doodle/.nomedia': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/doodle': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya/folder': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379/zapya': Read-only file system
chown: changing ownership of '/media/sumeet/4CCF-3379': Read-only file system
dd
$ sudo dd if="/dev/zero" of="/dev/sdc1" bs=1M count=10
dd: error writing '/dev/sdc1': Operation not permitted
1+0 records in
0+0 records out
0 bytes copied, 0.000825744 s, 0.0 kB/s
hdparm
$ sudo hdparm -r0 /dev/sdc
/dev/sdc:
setting readonly to 0 (off)
readonly = 0 (off)
Creating new partition
$ sudo fdisk /dev/sdc
Welcome to fdisk (util-linux 2.29).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
fdisk: cannot open /dev/sdc: Read-only file system
Still isn't working
Device info
Bus 002 Device 008: ID 0781:5567 SanDisk Corp. Cruzer Blade
sudo fdisk /dev/sdX
and press "o" to create a new partition table then "w" to write it to the disk. – Ravexina Jun 20 '17 at 16:26sudo fdisk /dev/sdc
notsdc1
– Ravexina Jun 20 '17 at 16:31sudo hdparm -r0 /dev/sdc
then again try creating a new partition table using fdisk. – Ravexina Jun 20 '17 at 16:35