MibunoOokami
March 30th, 2018, 04:49 AM
I'm trying to format a 16GB USB install disk that I have been given, it contains Windows 7 or something. I could do with an extra flash drive but I can't get it to format because it is read only. Gparted doesn't want anything to do with it and I've looked at a bunch of things online but no luck. One Youtube video looked promising but the command
df -Th doesn't list sdc1. Per the title, is it possible to format this flash drive to make it usable as a storage device?
These are the following commands I have tried.
mount /dev/sdc1 /media/usb
Error opening read-only '/dev/sdc1': No such device or address
Failed to mount '/dev/sdc1': No such device or address
Either the device is missing or it's powered down, or you have
SoftRAID hardware and must use an activated, different device under
/dev/mapper/, (e.g. /dev/mapper/nvidia_eahaabcc1) to mount NTFS.
Please see the 'dmraid' documentation for help.
mount /dev/sdc1 /mnt
mount: /dev/sdc1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
dmesg | tail
[ 6714.479663] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 f5 3c 78 00 00 88 00
[ 6714.479667] print_req_error: I/O error, dev sdc, sector 32849016
[ 6714.897343] sdc: sdc1
[ 6747.086647] usb 3-2: reset high-speed USB device number 10 using xhci_hcd
[ 6747.247169] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6747.247175] sd 6:0:0:0: [sdc] tag#0 Sense Key : Unit Attention [current]
[ 6747.247179] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 6747.247184] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 f5 3c 78 00 00 88 00
[ 6747.247187] print_req_error: I/O error, dev sdc, sector 32849016
[ 6747.664878] sdc: sdc1
e2fsck -f /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
e2fsck: Operation not permitted while trying to open /dev/sdc1
You must have r/w access to the filesystem or be root
root@mno:~# sudo e2fsck -f /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
e2fsck: Read-only file system while trying to open /dev/sdc1
Disk write-protected; use the -n option to do a read-only
check of the device.
sudo e2fsck -n /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
The short answer is no in this case, it seems micro$oft made the device read-only.
df -Th doesn't list sdc1. Per the title, is it possible to format this flash drive to make it usable as a storage device?
These are the following commands I have tried.
mount /dev/sdc1 /media/usb
Error opening read-only '/dev/sdc1': No such device or address
Failed to mount '/dev/sdc1': No such device or address
Either the device is missing or it's powered down, or you have
SoftRAID hardware and must use an activated, different device under
/dev/mapper/, (e.g. /dev/mapper/nvidia_eahaabcc1) to mount NTFS.
Please see the 'dmraid' documentation for help.
mount /dev/sdc1 /mnt
mount: /dev/sdc1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
dmesg | tail
[ 6714.479663] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 f5 3c 78 00 00 88 00
[ 6714.479667] print_req_error: I/O error, dev sdc, sector 32849016
[ 6714.897343] sdc: sdc1
[ 6747.086647] usb 3-2: reset high-speed USB device number 10 using xhci_hcd
[ 6747.247169] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6747.247175] sd 6:0:0:0: [sdc] tag#0 Sense Key : Unit Attention [current]
[ 6747.247179] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 6747.247184] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 f5 3c 78 00 00 88 00
[ 6747.247187] print_req_error: I/O error, dev sdc, sector 32849016
[ 6747.664878] sdc: sdc1
e2fsck -f /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
e2fsck: Operation not permitted while trying to open /dev/sdc1
You must have r/w access to the filesystem or be root
root@mno:~# sudo e2fsck -f /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
e2fsck: Read-only file system while trying to open /dev/sdc1
Disk write-protected; use the -n option to do a read-only
check of the device.
sudo e2fsck -n /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
The short answer is no in this case, it seems micro$oft made the device read-only.