HDD GURU FORUMS

Hello.
I have a PenDrive that when Plugged it to the system, Linux can't open it and show it as "Generic".

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 008: ID 058f:1234 Alcor Micro Corp. Flash Drive

I did :

$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 976773167 488386583+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00d600d6

Device Boot Start End Blocks Id System
/dev/sdb1 63 419425019 209712478+ 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.
/dev/sdb2 419425020 976773167 278674074 7 HPFS/NTFS/exFAT
Partition 2 does not start on physical sector boundary.


$ sudo dmesg | grep sd
[ 3727.121665] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 3727.121953] sd 6:0:0:0: [sdc] 31703040 512-byte logical blocks: (16.2 GB/15.1 GiB)
[ 3727.122588] sd 6:0:0:0: [sdc] Write Protect is off
[ 3727.122596] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 3727.123244] sd 6:0:0:0: [sdc] No Caching mode page found
[ 3727.123250] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 3727.125581] sd 6:0:0:0: [sdc] No Caching mode page found
[ 3727.125591] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 3727.126562] sdc: sdc1
[ 3727.128604] sd 6:0:0:0: [sdc] No Caching mode page found
[ 3727.128613] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 3727.128620] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 3733.025632] FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 3847.075170] sdc: detected capacity change from 16231956480 to 0
[ 6204.812250] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 6204.812506] sd 7:0:0:0: [sdc] 1953394095 512-byte logical blocks: (1.00 TB/931 GiB)
[ 6204.813092] sd 7:0:0:0: [sdc] Write Protect is off
[ 6204.813099] sd 7:0:0:0: [sdc] Mode Sense: 1f 00 10 08
[ 6204.813695] sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 6204.842490] sdc: sdc1
[ 6204.844271] sd 7:0:0:0: [sdc] Attached SCSI disk
[11686.493120] sd 8:0:0:0: Attached scsi generic sg3 type 0
[11686.493787] sd 8:0:0:0: [sdc] Attached SCSI removable disk


$ sudo dd if=/dev/zero of=/dev/sdc bs=512 count=1
dd: opening `/dev/sdc': No medium found

$ sudo dd if=/dev/zero of=/dev/sdc1 bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 2.6831e-05 s, 19.1 MB/s

$ sudo fdisk /dev/sdc1
fdisk: unable to read /dev/sdc1: Inappropriate ioctl for device

$ sudo mkdosfs -F32 /dev/sdc1
mkdosfs 3.0.13 (30 Jun 2012)
mkdosfs: Too few blocks for viable file system

$ sudo mkfs.ext3 /dev/sdc1
mke2fs 1.42.5 (29-Jul-2012)
/dev/sdc1 is not a block special device.
Proceed anyway? (y,n) y
mkfs.ext3: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.

$ sudo fsck.vfat -a /dev/sdc1
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
Logical sector size is zero.

$ sudo dumpe2fs /dev/sdc | grep superblock
dumpe2fs 1.42.5 (29-Jul-2012)
dumpe2fs: No medium found while trying to open /dev/sdc
Couldn't find valid filesystem superblock.


Can I have any hope?

Thank you.

Hi, Pendrive appears to be faulty, yes. If you want to recover files, this is quite possible. But doesn't look like you are wanting files. Definitely time for a new one!

HaQue wrote:Hi, Pendrive appears to be faulty, yes. If you want to recover files, this is quite possible. But doesn't look like you are wanting files. Definitely time for a new one!

Can I find a way for format it? It can't mount in Linux.

No the flash drive controller firmware is corrupt or there is an issue with the NAND chip, and the controller cant initialise NAND. It is cactus

HaQue wrote:No the flash drive controller firmware is corrupt or there is an issue with the NAND chip, and the controller cant initialise NAND. It is cactus

How about Firmware upgrade? Is it possible?

You would need to ask yourself, why did the firmware become corrupt, and also is there a physical issue? Even if you managed to figure out the poorly documented firmware tools, I wouldn't ever trust the drive. You could try it, tools are probably on flashboot or the like.

HaQue wrote:You would need to ask yourself, why did the firmware become corrupt, and also is there a physical issue? Even if you managed to figure out the poorly documented firmware tools, I wouldn't ever trust the drive. You could try it, tools are probably on flashboot or the like.

No, physical issue not exist. When I plugged the Pendrive to the system the light is turned on but Linux can't mount it. I visited some websites that provide Eraser tools and.. but how can I find the Model number of my Pendrive? Linux just tell me it is Alcor Micro.

The LED turning on means that power is getting to it. It does not mean that a cap or resistor or XTAL couldn't be faulty, taking the circuit out of spec and causing it to not work. Have you tested each capacitor and resistor to make sure it is reading to it's specification?

You pull the drive apart and look on the controller chip. The number would be AU6989 or something like that

You need the MP tools, along with burner and firmware files, and also must figure out how to use them. Other info you need is the NAND chip numbers and ID's.

Unless the pendrive is something pretty expensive or something, effort spent on this is, I fear, futile.

Thank you.
The number on my Flash is "618316 8421 JF300".
I wanted to use MP Tool but got an error. I attached some photos.

What is your idea?

is there RMRMRM over the top of the SanDisk name on the Flash chip?

I fear the flash is faulty and is a refurbished chip

HaQue wrote:is there RMRMRM over the top of the SanDisk name on the Flash chip?

I fear the flash is faulty and is a refurbished chip

Sandisk? It is Alcor Micro.

hack3rcon wrote:Sandisk? It is Alcor Micro.

yes SanDisk ! SDTNPNAHEM-004G = SanDisk

(pic. taken from FE site made by arvika)

jermy wrote:

hack3rcon wrote:Sandisk? It is Alcor Micro.

yes SanDisk ! SDTNPNAHEM-004G = SanDisk

SD4G.JPG

(pic. taken from FE site made by arvika)

You mean is that I must open the Pendrive?

unless you have another way to read what's written on the chip

HaQue wrote:......
You pull the drive apart and look on the controller chip. The number would be AU6989 or something like that

You need the MP tools, along with burner and firmware files, and also must figure out how to use them. Other info you need is the NAND chip numbers and ID's.

Unless the pendrive is something pretty expensive or something, effort spent on this is, I fear, futile.

There are 2 chips.. a controller chip and a NAND chip. The controller chip is the Alcor, and named as I said. The NAND flash is the SDTNxxxx chip. I am guessing the NAND will look like this:


you must know the exact number of the controller and the chip, the chips geometry etc to be able to pick the correct MP Tools (Mass Production Tools)

So it looks like it is a 4GB drive. A much better drive than that one retails here for AU$5.97 is there a reason you are trying to fix the drive to a possibly working, but never trustworthy state?

HaQue wrote:I fear the flash is faulty and is a refurbished chip

@HaQue why do you fear it's faulty and or refurbished ?

because a) it is Alcor, which tend to be in some of the crappiest drives in existence (I know I have at least 700 flash drives) and b) that chip number SDTNxxx.. is a common number for a refurbished chip. SanDisk check the chip, if the errors or bad blocks are over a certain amount, they sell it as refurbished. The chip is retested, errors are added to error tables and RMRMRM is lazered over the SanDisk name. if it was a real SanDisk, it usually is coupled with a SanDisk controller. The above makes me suspicious of its condition, and the fact that it isn't working....

so to continue, open it up and post some photos, or I suggest get a new drive.

what other details of the drive can you provide?

We all know how NAND industry likes to refurbish.

My bet is on a refurbished chip.

HaQue wrote:I know I have at least 700 flash drives

That would have to be the biggest flash donor collection i know of

day1data wrote:

HaQue wrote:I know I have at least 700 flash drives

That would have to be the biggest flash donor collection i know of

It isn't a donor collection - it is a research collection! And almost all of them have different properties, data, Spare Area sizes and formats, XORS, wear levelling algorithms, NAND chip properties like crystals, block and page geometry etc..