USB key not mounted
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Using Ubuntu 16.04, this is the output of dmesg when inserting an USB key:
usb 3-1: new high-speed USB device number 5 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host7: usb-storage 3-1:1.0
scsi 7:0:0:0: Direct-Access <product_name> 2.00 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 16384 512-byte logical blocks: (8.39 MB/8.00 MiB)
sd 7:0:0:0: [sdc] Write Protect is on
sd 7:0:0:0: [sdc] Mode Sense: 0b 00 80 08
sd 7:0:0:0: [sdc] No Caching mode page found
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk
usb 3-1: USB disconnect, device number 5
It is not mounted in the filesystem. This key contains a fat32 partition with several documents and I did nothing to it, but it suddenly ceased to work. It doesn't work in Windows as well (it asks if I want to format it).
Another working USB key generates the following dmesg lines in Linux:
usb 3-1: new high-speed USB device number 6 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: <name>
usb 3-1: Manufacturer: <manufacturer_name>
usb 3-1: SerialNumber: <serial>
usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host8: usb-storage 3-1:1.0
scsi 8:0:0:0: Direct-Access <product_name> 1100 PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:0: [sdc] 15663104 512-byte logical blocks: (8.02 GB/7.47 GiB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 8:0:0:0: [sdc] No Caching mode page found
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 8:0:0:0: [sdc] Attached SCSI removable disk
The line with Mfr=1, Product=2, SerialNumber=3 is different and in the second case three more lines follow. Moreover, sdc: sdc1 is missing in the first dmesg.
Following this question, I also tried mount /dev/sdc/ /mnt/test, but this is the output:
mount: /dev/sdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
sudo parted /dev/sdc print gives:
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Error: /dev/sdc: unrecognized disk label
Model: <manufacturer_model> (scsi)
Disk /dev/sdc: 8389kB
Sector dimensions (logic/physical): 512B/512B
Partition table: unknown
Disk flags:
1) Can the first dmesg certainly state that the first USB key is damaged?
And, if not:
2) Is there any other test that can be done on the first key to determine if and where it has any damage?
partition data-recovery usb-drive readonly flash-memory
asked Nov 5 '17 at 17:25
BowPark
1,46182139
add a comment |Â
up vote
0
down vote
favorite
Using Ubuntu 16.04, this is the output of dmesg when inserting an USB key:
usb 3-1: new high-speed USB device number 5 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host7: usb-storage 3-1:1.0
scsi 7:0:0:0: Direct-Access <product_name> 2.00 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 16384 512-byte logical blocks: (8.39 MB/8.00 MiB)
sd 7:0:0:0: [sdc] Write Protect is on
sd 7:0:0:0: [sdc] Mode Sense: 0b 00 80 08
sd 7:0:0:0: [sdc] No Caching mode page found
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk
usb 3-1: USB disconnect, device number 5
It is not mounted in the filesystem. This key contains a fat32 partition with several documents and I did nothing to it, but it suddenly ceased to work. It doesn't work in Windows as well (it asks if I want to format it).
Another working USB key generates the following dmesg lines in Linux:
usb 3-1: new high-speed USB device number 6 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: <name>
usb 3-1: Manufacturer: <manufacturer_name>
usb 3-1: SerialNumber: <serial>
usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host8: usb-storage 3-1:1.0
scsi 8:0:0:0: Direct-Access <product_name> 1100 PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:0: [sdc] 15663104 512-byte logical blocks: (8.02 GB/7.47 GiB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 8:0:0:0: [sdc] No Caching mode page found
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 8:0:0:0: [sdc] Attached SCSI removable disk
The line with Mfr=1, Product=2, SerialNumber=3 is different and in the second case three more lines follow. Moreover, sdc: sdc1 is missing in the first dmesg.
Following this question, I also tried mount /dev/sdc/ /mnt/test, but this is the output:
mount: /dev/sdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
sudo parted /dev/sdc print gives:
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Error: /dev/sdc: unrecognized disk label
Model: <manufacturer_model> (scsi)
Disk /dev/sdc: 8389kB
Sector dimensions (logic/physical): 512B/512B
Partition table: unknown
Disk flags:
1) Can the first dmesg certainly state that the first USB key is damaged?
And, if not:
2) Is there any other test that can be done on the first key to determine if and where it has any damage?
partition data-recovery usb-drive readonly flash-memory
asked Nov 5 '17 at 17:25
BowPark
1,46182139
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Using Ubuntu 16.04, this is the output of dmesg when inserting an USB key:
usb 3-1: new high-speed USB device number 5 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host7: usb-storage 3-1:1.0
scsi 7:0:0:0: Direct-Access <product_name> 2.00 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 16384 512-byte logical blocks: (8.39 MB/8.00 MiB)
sd 7:0:0:0: [sdc] Write Protect is on
sd 7:0:0:0: [sdc] Mode Sense: 0b 00 80 08
sd 7:0:0:0: [sdc] No Caching mode page found
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk
usb 3-1: USB disconnect, device number 5
It is not mounted in the filesystem. This key contains a fat32 partition with several documents and I did nothing to it, but it suddenly ceased to work. It doesn't work in Windows as well (it asks if I want to format it).
Another working USB key generates the following dmesg lines in Linux:
usb 3-1: new high-speed USB device number 6 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: <name>
usb 3-1: Manufacturer: <manufacturer_name>
usb 3-1: SerialNumber: <serial>
usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host8: usb-storage 3-1:1.0
scsi 8:0:0:0: Direct-Access <product_name> 1100 PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:0: [sdc] 15663104 512-byte logical blocks: (8.02 GB/7.47 GiB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 8:0:0:0: [sdc] No Caching mode page found
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 8:0:0:0: [sdc] Attached SCSI removable disk
The line with Mfr=1, Product=2, SerialNumber=3 is different and in the second case three more lines follow. Moreover, sdc: sdc1 is missing in the first dmesg.
Following this question, I also tried mount /dev/sdc/ /mnt/test, but this is the output:
mount: /dev/sdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
sudo parted /dev/sdc print gives:
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Error: /dev/sdc: unrecognized disk label
Model: <manufacturer_model> (scsi)
Disk /dev/sdc: 8389kB
Sector dimensions (logic/physical): 512B/512B
Partition table: unknown
Disk flags:
1) Can the first dmesg certainly state that the first USB key is damaged?
And, if not:
2) Is there any other test that can be done on the first key to determine if and where it has any damage?
partition data-recovery usb-drive readonly flash-memory
asked Nov 5 '17 at 17:25
BowPark
1,46182139
Using Ubuntu 16.04, this is the output of dmesg when inserting an USB key:
usb 3-1: new high-speed USB device number 5 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host7: usb-storage 3-1:1.0
scsi 7:0:0:0: Direct-Access <product_name> 2.00 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 16384 512-byte logical blocks: (8.39 MB/8.00 MiB)
sd 7:0:0:0: [sdc] Write Protect is on
sd 7:0:0:0: [sdc] Mode Sense: 0b 00 80 08
sd 7:0:0:0: [sdc] No Caching mode page found
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk
usb 3-1: USB disconnect, device number 5
It is not mounted in the filesystem. This key contains a fat32 partition with several documents and I did nothing to it, but it suddenly ceased to work. It doesn't work in Windows as well (it asks if I want to format it).
Another working USB key generates the following dmesg lines in Linux:
usb 3-1: new high-speed USB device number 6 using xhci_hcd
usb 3-1: New USB device found, idVendor=<id1>, idProduct=<id2>
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: <name>
usb 3-1: Manufacturer: <manufacturer_name>
usb 3-1: SerialNumber: <serial>
usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host8: usb-storage 3-1:1.0
scsi 8:0:0:0: Direct-Access <product_name> 1100 PQ: 0 ANSI: 0 CCS
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:0: [sdc] 15663104 512-byte logical blocks: (8.02 GB/7.47 GiB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 8:0:0:0: [sdc] No Caching mode page found
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 8:0:0:0: [sdc] Attached SCSI removable disk
The line with Mfr=1, Product=2, SerialNumber=3 is different and in the second case three more lines follow. Moreover, sdc: sdc1 is missing in the first dmesg.
Following this question, I also tried mount /dev/sdc/ /mnt/test, but this is the output:
mount: /dev/sdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
sudo parted /dev/sdc print gives:
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
Error: /dev/sdc: unrecognized disk label
Model: <manufacturer_model> (scsi)
Disk /dev/sdc: 8389kB
Sector dimensions (logic/physical): 512B/512B
Partition table: unknown
Disk flags:
1) Can the first dmesg certainly state that the first USB key is damaged?
And, if not:
2) Is there any other test that can be done on the first key to determine if and where it has any damage?
partition data-recovery usb-drive readonly flash-memory
asked Nov 5 '17 at 17:25
BowPark
1,46182139
asked Nov 5 '17 at 17:25
BowPark
1,46182139
asked Nov 5 '17 at 17:25
BowPark
1,46182139
asked Nov 5 '17 at 17:25
BowPark
1,46182139
1,46182139
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45
add a comment |Â
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402689%2fusb-key-not-mounted%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The, probably damaged, USB memory shows a capacity of 8MB. This may be a small section of the addressable memory or maybe some artifact of the on-board microcontroller's addressing circuitry. There's no other software only test I can think of. However, if you have knowledge of the internal electronics, you could open the case, remove the electronics and attempt to reflow the solder in your oven. Something like this Instructable ... you may lose whatever data is on the USB memory and/or destroy the unit, but it might work.
– RubberStamp
Nov 5 '17 at 17:45