Flash memory stick blank - can't find boot table or anything - wantsto be reformatted each time I us

  • Thread starter Thread starter daviddschool
  • Start date Start date
D

daviddschool

I have an issue with a memory stick. I used it last night, saved work
on it and it was fine. This morning when I plugged it in, it wasn't
recognized and the data is seemingly gone. I have tried using
EasyRecover Professional and it says it cannot find out whether it is
fat 16, 32, of NTSF. I really need the info on this drive, but I was
wondering what my options are. It is a 2 gig stick, generic, a gift
for Xmas. I have backed up a lot of the stuff a few days ago, but I
have done work on it since then I really don't want to go down the
drain. Any ideas?
The USB is recognized by the system, but when I click on the drive
letter in Windows Explorer, it tells me it should be formatted. Again
worked perfect last night, today not at all...
 
I have an issue with a memory stick.  I used it last night, saved work
on it and it was fine.  This morning when I plugged it in, it wasn't
recognized and the data is seemingly gone.  I have tried using
EasyRecover Professional and it says it cannot find out whether it is
fat 16, 32, of NTSF.  I really need the info on this drive, but I was
wondering what my options are.  It is a 2 gig stick, generic, a gift
for Xmas.  I have backed up a lot of the stuff a few days ago, but I
have done work on it since then I really don't want to go down the
drain.  Any ideas?
The USB is recognized by the system, but when I click on the drive
letter in Windows Explorer, it tells me it should be formatted.  Again
worked perfect last night, today not at all...

Before anything else, try this stick on a different PC.
 
In
smlunatick typed on Tue, 29 Sep 2009 11:13:50 -0700 (PDT):
Before anything else, try this stick on a different PC.

Very good advice. Also memory sticks generally use MLC flash memory.
Which are only good for 5,000 to 10,000 complete writes. I have many and
I never worn one out yet. But I know a guy in France who burns them out
in two months worth of time. His record was one only lasting only two
weeks. Also static electricity is supposed to take them out as well.
Although that never happened to me yet either.
 
Before anything else, try this stick on a different PC.

Yep, done it all. Tried it on 4 different pc nows. Laptop, school
PC, and two others PC's at home. I have run win-TESTDISK 6.11.3 and
it cannot find the partition or anything! This is crazy, how can
everything just be gone? The drive seems to work, but WANTS to be
formatted each time it is put in. With TESTDISK 6.11.3 it cannot find
a partition but asked to ADD one, I am not sure if I should do this.
I am going to try and run KNOPPIX next and see if it can recognize it.
 
Insmlunatick typed on Tue, 29 Sep 2009 11:13:50 -0700 (PDT):



Very good advice. Also memory sticks generally use MLC flash memory.
Which are only good for 5,000 to 10,000 complete writes. I have many and
I never worn one out yet. But I know a guy in France who burns them out
in two months worth of time. His record was one only lasting only two
weeks. Also static electricity is supposed to take them out as well.
Although that never happened to me yet either.

It is fairly new, so it wouldn't be from too much use. Only about 1
year old.
 
It is fairly new, so it wouldn't be from too much use.

It is telling me (using many recovery software trials) that there is
no LOGICAL DRIVE. Not sure what this would mean for recovery...
 
daviddschool said:
It is telling me (using many recovery software trials) that there is
no LOGICAL DRIVE. Not sure what this would mean for recovery...

Since you're a Knoppix guy, you can make a backup copy of the
flash drive, in its current state. Then you can safely work
on it with Testdisk. For example

(save device to file)

sudo dd if=/dev/sda of=/media/hda1/my_flash_stick.dd bs=262144 count=8192

That would extract 2GB of raw data from the flash stick at /dev/sda
and store it in a 2GB file on some mounted volume like /media/hda1.
You'd need to use a hard drive, because there may not be room in
RAM to store the file in the ~knoppix home directory. (In Knoppix, generally
you need to right click a volume icon, and make the volume writable,
before mounting it. Then your /media/hda1 or whatever it is called,
would be writable.)

Later, if testdisk failed to do what you expected (damaged flash contents),
you could put the 2GB image back.

(restore file to device)

sudo dd if=/media/hda1/my_flash_stick.dd of=/dev/sda bs=262144 count=8192

Running the command without a block size and count, should
collect all possible data. But the Windows port of dd, doesn't
"stop" properly when it hits the end of a flash drive. Which is
why I like to specify a block size and count when backing up
a device. This should work properly in Linux.

sudo dd if=/dev/sda of=/media/hda1/my_flash_stick.dd

The testdisk site, also has file recovery software. If you
get desperate, you can try to recover files with this.

http://www.cgsecurity.org/wiki/PhotoRec

But if it was me, I'd do a sector by sector backup first. And
then let Testdisk write a new partition table in sector 0.

Paul
 
Since you're a Knoppix guy, you can make a backup copy of the
flash drive, in its current state. Then you can safely work
on it with Testdisk. For example

I am not, but I was running out of options. Knoppix and ubuntu didn't
even see the drive.
The testdisk site, also has file recovery software. If you
get desperate, you can try to recover files with this.

http://www.cgsecurity.org/wiki/PhotoRec

But if it was me, I'd do a sector by sector backup first. And
then let Testdisk write a new partition table in sector 0.

    Paul

I have tried PhotoRec and it did not recover and files from the
drive. Does this mean it is toast?
 
daviddschool said:
I am not, but I was running out of options. Knoppix and ubuntu didn't
even see the drive.

I have tried PhotoRec and it did not recover and files from the
drive. Does this mean it is toast?

Sounds like it.

If you type "dmesg", do you see any mention of the flash device ?

The thing is, the device doesn't have to be mountable, to be
backed up. "dd" works at the raw device level (just copying
sectors). You have to be "root" to access raw devices, which is
why the sudo pre-command is used.

But if the flash drive isn't even being detected as
a USB device, then the "dd" command can't work with respect to it.

The other command that might be useful, is "lsusb", which lists
the current USB devices detected. "lspci" is the command for
things on the PCI bus. So with a small set of commands, you
can get a fair amount of info about hardware.

Paul
 
Sounds like it.

If you type "dmesg", do you see any mention of the flash device ?

The thing is, the device doesn't have to be mountable, to be
backed up. "dd" works at the raw device level (just copying
sectors). You have to be "root" to access raw devices, which is
why the sudo pre-command is used.

But if the flash drive isn't even being detected as
a USB device, then the "dd" command can't work with respect to it.

The other command that might be useful, is "lsusb", which lists
the current USB devices detected. "lspci" is the command for
things on the PCI bus. So with a small set of commands, you
can get a fair amount of info about hardware.

Paul

WinXP does see the device, but it tell me "You need to format this
device". So the device is being seen by windows, but the info/data on
it is not. Do you want me to run the "lsusb" cmd from DOS? When I go
to COMPUTER MANAGEMENT in windows, the DEVICE manager sees it as
HEALTHY and tells me the files size, but again, this device was full
of info that is now seemingly gone. So the device seem to work, but
how can I get the info back?!?!
 
daviddschool said:
WinXP does see the device, but it tell me "You need to format this
device". So the device is being seen by windows, but the info/data on
it is not. Do you want me to run the "lsusb" cmd from DOS? When I go
to COMPUTER MANAGEMENT in windows, the DEVICE manager sees it as
HEALTHY and tells me the files size, but again, this device was full
of info that is now seemingly gone. So the device seem to work, but
how can I get the info back?!?!

That is a good sign. So it is present as a raw device. You can work
on it with Testdisk then, and put back a partition table. Testdisk will
scan the entire device, looking for partitions of recognizable type.

My recommended procedure is

1) Back up the device, sector by sector, while in Windows.
This program can do that, but you have to figure out the
command syntax. The syntax will be similar to the example
I showed you for Knoppix. You should specify a block size and
count, in order that this program complete the backup copy properly.
(This windows port of dd has a bug, where it cannot detect the
end of a USB flash drive properly. As long as you use block size
and count parameter, the program works properly.)

http://www.chrysocome.net/dd

You run that in an MSDOS window. Do "dd --list" first, to get
the size info, and name of the device. This is my 8GB USB flash
stick. The number below is not 8*1024*1024*1024, it is actually
7648*1024*1024. A reasonable count and block size would be
244736 * 32768. The product of those two numbers is 8019509248.

\\?\Device\Harddisk2\Partition0 <---- to back up the whole stick
link to \\?\Device\Harddisk2\DR10
Removable media other than floppy. Block size = 512
size is 8019509248 bytes

\\?\Device\Harddisk2\Partition1 <---- the first partition
link to \\?\Device\Harddisk2\DP(1)0-0+b
Removable media other than floppy. Block size = 512
size is 8019509248 bytes

Yours is 2GB, so your command might look like this. Divide your
total size for partition0 by 32768. My guess at the value for
count is roughly 61184. Do the math exactly, such that bs * count
is equal to the size declared for partition0 in the --list output.

dd if=\\?\Device\Harddisk2\Partition0 of=my_flash_stick.dd bs=32768 count=61184

That will place a ~2GB file in the current working directory
in the DOS window (likely the same directory you've got the
"dd.exe" program in).

You have to know a minimal amount about working in a command window,
to work with command line stuff. You need to "cd" to the correct
directory, as otherwise, Windows won't know the dd.exe executable
is stored there. The "path" variable for Windows can be edited, but
for a job like this, it is simpler to just CD to the directory
containing dd.exe.

2) Run Testdisk. Let it scan for a partition, and install a partition table.
If Testdisk screws up, use this to restore the flash stick to the state
before Testdisk touched it. This is your insurance policy.

dd if=my_flash_stick.dd of=\\?\Device\Harddisk2\Partition0 bs=32768 count=61184

Just a word of warning. My 8GB stick currently has a FAT file system on it,
and is an image of a floppy diskette. Testdisk did not analyse it properly.
Testdisk should work fine, for more conventional FAT32 or NTFS cases.

If, at any time, you don't like what you see in Testdisk, press control-C
to abort the program. The menus don't all have quit items, but if you're
sitting in a menu, and don't like the results, press control-C and
try some other options in the program. The web site for Testdisk also
has various bits of advice on it. This one, for example, might help you
in the future.

http://www.cgsecurity.org/wiki/Damaged_Hard_Disk

HTH,
Paul
 
In
daviddschool typed on Wed, 30 Sep 2009 13:38:19 -0700 (PDT):
WinXP does see the device, but it tell me "You need to format this
device". So the device is being seen by windows, but the info/data on
it is not. Do you want me to run the "lsusb" cmd from DOS? When I go
to COMPUTER MANAGEMENT in windows, the DEVICE manager sees it as
HEALTHY and tells me the files size, but again, this device was full
of info that is now seemingly gone. So the device seem to work, but
how can I get the info back?!?!

Like I mentioned earlier, flash drives work all the way up to the number
of writes have been exceeded. Usually 5,000 to 10,000 compete writes for
inexpensive models. Once this is hit, poof! They can't be read or
written to anymore. And getting a year with heavy use is doing pretty
good actually. If you want a better flash stick, you can get like an
ADATA SDHC card and use a card reader. These are guaranteed for life.
That is what I use and none have failed me yet.
 
Back
Top