Flash disc issue

[Member andfree]

Hi. I put a flash disc into the usb port and this appears in zzzFM:

- sdb [no media]

I click on it, and this message appears:

Run: Mount /dev/sdb
Status: Finished with error  ( exit status 1 )
udevil: error 63: no media in device /dev/sdb (or specify type with -t)

Is it a hardware issue? Is the disc useless? Thanks.

[Member sybok]

Helpful

Up

0

::

Hi,

I once had a “dying” USB stick that seemed to work in Windows, where I repaired it, but Linux failed to work with it and after some time even the Windows.

0) Are the contacts clean?
1) Does the flash-disc work in other PCs/OSes?
2) If it is formatted, what is the partition filesystem (ext4, ntfs, …)?
3) If you insert it, you may post output of ‘lsblk’ and (relevant part of ‘sudo dmesg | tail -50’ that mentions the new device added)

The step 2)+3) should help to devise an explicit mount command, such as ‘sudo mount [-t ntfs] /dev/sd[b-z] <target folder>’, and see whether its output provides more/useful information other than the error code.
The error 63 indicates that it could be a file-system that needs to be explicitly specified.

[Member andfree]

Helpful

Up

0

::

Many thanks for the reply.

sybok wrote:

0) Are the contacts clean?

I can’t see them. I blew to them, but it didn’t help.

sybok wrote:

1) Does the flash-disc work in other PCs/OSes?

The person that gave it to me said that it didn’t work in his mac OS. I tried it in windows, and infinite windows, one after another, opened with this message:
You need to format the disk in drive E: before you can use it. Do you want to format it now?

sybok wrote:

2) If it is formatted, what is the partition filesystem (ext4, ntfs, …)?

I don’t see how to check it.

sybok wrote:

3) If you insert it, you may post output of ‘lsblk’ and (relevant part of ‘sudo dmesg | tail -50’ that mentions the new device added)

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0  93.2G  0 disk 
├─sda1   8:1    0  91.7G  0 part /
└─sda2   8:2    0   1.5G  0 part [SWAP]
sdb      8:16   1 117.2G  0 disk 
sr0     11:0    1  1024M  0 rom

$ sudo dmesg | tail -50
[ 6355.532967] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.532972] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.532975] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.532984] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.534335] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.534342] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.534347] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.534351] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.534355] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.534364] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.535710] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.535717] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.535722] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.535726] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.535730] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.535739] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.536951] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.536957] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.536962] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.536967] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.536970] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.536978] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.538202] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.538208] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.538212] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.538217] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.538220] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.538229] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.539589] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.539596] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.539601] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.539605] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.539609] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.539616] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.539642] ldm_validate_partition_table(): Disk read failed.
[ 6355.540955] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.540962] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.540966] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.540971] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.540974] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.540982] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.542329] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 6355.542336] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 6355.542340] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Medium not present
[ 6355.542345] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 6355.542348] blk_update_request: I/O error, dev sdb, sector 0
[ 6355.542357] Buffer I/O error on dev sdb, logical block 0, async page read
[ 6355.544724] Dev sdb: unable to read RDB block 0
[ 6355.549846]  sdb: unable to read partition table
[ 6355.552738] sd 2:0:0:0: [sdb] Attached SCSI removable disk

sybok wrote:

The step 2)+3) should help to devise an explicit mount command, such as ‘sudo mount [-t ntfs] /dev/sd[b-z] <target folder>’, and see whether its output provides more/useful information other than the error code.

Does the output above help us to specify that command?

Thanks, again.

• This reply was modified 6 months, 2 weeks ago by andfree.

[Member Robin]

Helpful

Up

0

::

If positively there is no data stored on the drive in question, you should try to partition and format it, e.g. by using gparted from antiX menu. If this attempt fails (as I presume from your dmesg output, but who knows?), try to format it in a Windows PC, best on a different hardware, for validation and exclusion of arbitrary incompatibilities. If this attempt also fails, read first few lines of this posting about USB flash drives defective by design and throw the stick away. There might be a slight chance to recover it, search for instructions by ModdIt here in Forum, or read the thread I’ve linked to in the beforementioned posting, somebody has tried to recover such a stick with special tools, but manufacturers have created kind of labyrinth here.

Windows is like a submarine. Open a window and serious problems will start.

[Member PPC]

Helpful

Up

0

::

Hum… the person that gave you this USB drive told you it didn’t work in a Mac… you said it didn’t work in several Windows PC’s… It does not work in antiX… I think the answer is staring you right in the face… Nothing lasts forever… Even if you “revive” it, the hardware is compromised, do not stare any essential data on it…

P.

[Member sybok]

Helpful

Up

0

::

Hi, as @Robin pointed out, you may try to format it.
When you insert it, start program called ‘gparted’, select the appropriate disk and create a partition.

BEWARE: Selecting wrong disk will result in the drive being formatted and loss of all data on it.

[Author]

Posts