«

============================

EXECUTIVE SUMMARY:

Flash-USB-memory-stick (2gig) DEAD, advice on recovery needed.
- udev, lsusb *do* recognise the drive,
- but *no device* /dev/sdxx is created

Question: partition-table? Mbr?

output of dmesg, udevinfo, lsusb is here:
http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware

PRIZE! A free http://y23.com/apd ASTRO-POCKET-DIARY for 2011!!

=============================

Hello everyone, and thank you for your responses ...

Again, The the stick *does* appear in system responses,
but there is NO DEVICE.

My guess: the USB-mechanism receives a "yes it is a Storage-USB"
but then it gets a wrong nonsense response...

For Windows users:
When I insert the usbstick I hear THREE DINGS (SOUNDS)
- The three low dings is Windows XP's way of saying "this screwed up"
- This device cannot start (Code 10)


Hi Lusotec!

> Check if a /dev/sdX is created when you connect the USB drive.

No DEVICE CREATED.


> If a file system is detect then use the mount command to mount it.

What do you mean? Have you looked at
the output of dmesg, udevinfo, lsusb???
http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware



Hi Enkidu, Cliff!

> Since you can't see
> anything, even a device, the thing is probably beyond recovery.

Thanks for being vague and depressing.

"probably" - How probable?

"even a device" ?? I *can* see the hardware.
The boot-sector/partition-table is bad.
DO YOU HAVE ANY INSPIRATION OF ANY TOOLS I CAN TRY????


Hello Mark,

> I suspect you also did something that wrote to /dev/sda,
> wiping out the partition table, rendering the drive
> as not recognizable from within Microsoft Windows.

If there was only a bad partition-table, I would be able
to ACCESS it, and erase the partition.

> You can use drives without a partition table,
> but it is not a good idea if they are intented to be moved
> across systems, because some systems may see
> the drive as unusable or empty.

aha. So how do I access a this drive "without a partition table"
i.e. RAW????

Remember: I **DO NOT GET** a "DRIVE".
It is like I have to LOW LEVEL REPAIR it.

If anyone has a suggestion WHICH TOOL to try,
make wild assumptions and crazy suggestions!!

And remember:

It is bad luck to be superstitious!!

On Sat, 27 Feb 2010 18:26:50 -0800, NotSure wrote:

> If anyone has a suggestion WHICH TOOL to try, make wild assumptions and
> crazy suggestions!!

Is this data really that important to you? Where is your backup copy? Why don't you use that?


--
"Filtering the Internet is like trying to boil the ocean"

On 2010-02-27, Richard <> wrote:
> NotSure wrote:
>> Hi guys! Some #$%^& computer ruined my 2gig thumbdrive.
>>
>> executive summary:
>> - Linux *fdisk* does not see the USBstick (udev does)
>> - (every) Windows says: This device cannot start (Code 10)
>>
>> Details here http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware
>> (output of dmesg, udevinfo, lsusb)
>>
>> Knoppix, Winxp win98, HirenBootCD... a few old laptops.. available..
>>
>> I'd be stoked if someone helped to recover my data, I'll gladly send
>> you a 2010 (or 2011) Astronomical Pocket Diary http://y23.com/apd or a
>> lifetime subscription to the online Astro Diary http://y23.com/apdoe
>> ..
>>

>
> I had one die and had to get someone to move the flash chip to an
> identical drive to get the data off it.
>
> Newer smaller ones are all integrated so you dont even have that option.

History here. Backups, you know the things that worth SFA, until something
happens and then they rise in value faster than a rocket.

HD used to fail, oh dear they still do. Since they days of sailing ships
people have been insuring things, ships and Lloyds of London resulted from
it.

Strange how easily it is to get a digital copy, and yet the saying remains.

There are two typoes of computer users: those that have needed a backup and
those that who will need to have a backup.

How much risk do you wish to carry? Data is valuable protect it, yes?

NotSure <> wrote:
> Flash-USB-memory-stick (2gig) DEAD, advice on recovery needed.
> - udev, lsusb *do* recognise the drive,
> - but *no device* /dev/sdxx is created

Reboot the machine and kill the automounter.

Now plug the stick in.

ls /dev/sd? (only one question mark, we are looking for the whole stick here)

That will tell us what the stick is. These notes assume /dev/sda. But if you
have been plugging the stick in and out, it may be something else

Blank the penstick using the data dumper:

dd if=/dev/zero of=/dev/sda

Now use fdisk to create a partion table:

fdisk /dev/sda

n (to create a new partition)
p (for a primary partition)

create a partition of maximum size, and of type b (fat32).

w (write the partition table to disk)
q (quit fdisk)

Now a partition should have appeared:

ls /dev/sda1

Now you need to format the partition.

mkfs -t vfat /dev/sda1

> If there was only a bad partition-table, I would be able
> to ACCESS it, and erase the partition.

You used the wrong device name, so there is no partition table. Your partition
effectively starts where the partition table should have gone.

> aha. So how do I access a this drive "without a partition table"

Right. If you do not create a partition table, you will not be able to use
the penstick on other machines. Do not do this!!!

> Remember: I **DO NOT GET** a "DRIVE".

You won't get a drive, until you create a formatted partition.
Do as I say above!

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/

NotSure wrote:
>
> Hi Enkidu, Cliff!
>
>> Since you can't see
>> anything, even a device, the thing is probably beyond recovery.
>
> Thanks for being vague and depressing.
>
I've only ever recovered a USB stick and that one showed as having 8kB
rather than one GB, so there was something there. I've had devices that
have behaved similar to the one you are having problems with, and I've
never been able to recover them. There's an HP utility that helps in
some cases.

I think of USB sticks as big floppy disks. If a floppy disk goes bad,
you might as well chuck it. Same with USB sticks. They are much more
fragile than hard disks.
>
> "probably" - How probable?
>
Very probably.
>
> "even a device" ?? I *can* see the hardware.
> The boot-sector/partition-table is bad.
> DO YOU HAVE ANY INSPIRATION OF ANY TOOLS I CAN TRY????
>
You can see the hardware, but you can't see a device as in /dev/????

Sorry you think that I am being depressing. I believe that I'm being
realistic.

Cheers,

Cliff

Sweetpea <Herit...@Sweetpea.com> wrote:

> Is this data really that important to you?
> Where is your backup copy? Why don't you use that?

Thanks for the suggestion. What *was* I thinking?

Gordon <gor...@clear.net.nz> wrote:

> History here. Backups, you know the things that worth SFA,
> until something happens and then they rise in value faster
> than a rocket.

indeed indeed.

> Strange how easily it is to get a digital copy,
> and yet the saying remains.
> There are two typoes of computer users:
> those that have needed a backup and
> those that who will need to have a backup.
> How much risk do you wish to carry?
> Data is valuable protect it, yes?

yes yes, You would make a good priest, Gordon.
Preaching to the sinners...

Its is actually a bit like christianity,
we only start to believe in God on our death-bed.
You have no idea how many staunch atheists
pray and pray when the final moment has arrived.

My USB stick, however, I believe to be comatose



Golden California Girls <gldncag...@aol.com.mil> wrote:

> Finally you set a followup to header!!!

sorrrrry, yes. I should have done that immediately.

> May I suggest a bath in liquid nitrogen
> while you try and access.
> Very likely the stick itself has failed and
> getting it cold may allow it to have its data read out.

Yey! A good suggestion for a change. I'll keep that in mind
muchas gracias!!!

> If this fails I suggest a sledgehammer
> to make sure no CIA type with
> an electron microscope can read the data.

Hehe, the NSA and CIA will want the data!
I kept pictures of bearded men and high buildings
on it. They can construct another terror-case
and "keep America safe" (in constant fear)
while getting huuuge budgets to develop even
more clandestine exotic weaponry, in order to
commit the mext 9/11 terror snuff-job.
It sure is necessary soon, The world wants it's
money back, see
http://en.wikipedia.org/wiki/List_of...ccount_balance

> If you don't have data on it,
> quit wasting your time, they aren't that expensive.

Its the data I need...

> Or course if your intent is to spam
> for some pocket diary ...

HEY! It's not "some" Pocket Diary!
Its can tell you the future! Ah, but
US empire doesn't have one, never mind then.


MARK HOBLEY

Please say after me:

"When the USB Stick is plugged in, no
/dev/sdx? -- node is created"

THANK YOU very much for the typing-grease
and the PERFECT instructions for any linux
newbie to format a USB stick from the shell.

> You used the wrong device name,

there is *NO* device-node.

> so there is no partition table.
> Your partition effectively starts where
> the partition table should have gone.

Nice theory.

> You won't get a drive, until you create
> a formatted partition.Do as I say above!

there is no /dev/sda1 no /dev/sda2 no /dev/sda3
no /dev/sdb1 no /dev/sdb2 no /dev/sdb3
no /dev/sdc1 no /dev/sdc1
no /dev- NOTHING. only /dev/hda1 (which is my HDD)


Enkidu <enkidu....@com.cliffp.com> wrote:

>. You can see the hardware, but you can't
> see a device as in /dev/????

yep. In all 3 computers I have available.

again: lsusb and udevinfo report all details,
manufacturer, everything.
but linux does not assigne a /dev/sdxx node.

- LED blinks normal when inserted
- gives a windows code 10 error (three ding-sounds)
- linux udevinfo, lsusb report flashDrive present, but no /dev/sdxx
node is made

Flash-memory was corrupted?

Is there any programme that can access the flash-memory-chip
differently though USB?
Can the chip be talked-to in a low-level access via USBus AT ALL??

NotSure wrote:
> ============================
>
> EXECUTIVE SUMMARY:
>
> Flash-USB-memory-stick (2gig) DEAD, advice on recovery needed.
> - udev, lsusb *do* recognise the drive,
> - but *no device* /dev/sdxx is created
>> Question: partition-table? Mbr?
>
> output of dmesg, udevinfo, lsusb is here:
> http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware
>
> PRIZE! A free http://y23.com/apd ASTRO-POCKET-DIARY for 2011!!
>
> =============================
>
> Hello everyone, and thank you for your responses ...
>
> Again, The the stick *does* appear in system responses,
> but there is NO DEVICE.
>
> My guess: the USB-mechanism receives a "yes it is a Storage-USB"
> but then it gets a wrong nonsense response...
>
> For Windows users:
> When I insert the usbstick I hear THREE DINGS (SOUNDS)
> - The three low dings is Windows XP's way of saying "this screwed up"
> - This device cannot start (Code 10)
>
>
> Hi Lusotec!
>
>> Check if a /dev/sdX is created when you connect the USB drive.
>
> No DEVICE CREATED.

Since no device is created, my best guess is that the problem is in the USB
drive hardware. Note that the creation of the device does not depend on the
state of the MBR or partition table.

>> If a file system is detect then use the mount command to mount it.
>
> What do you mean? Have you looked at
> the output of dmesg, udevinfo, lsusb???
> http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware

Without a /dev/sd* there is no way to access the data on the device, much
less mount it.

> Hi Enkidu, Cliff!
>
>> Since you can't see
>> anything, even a device, the thing is probably beyond recovery.
>
> Thanks for being vague and depressing.
>
> "probably" - How probable?
>
> "even a device" ?? I *can* see the hardware.

The USB handshaking is working and thus the system sees the USB device but
when trying to access it as a storage device something does not work.

> The boot-sector/partition-table is bad.
> DO YOU HAVE ANY INSPIRATION OF ANY TOOLS I CAN TRY????

Even if the boot sector and the partition table where complete trash that
would not be a problem to access it as a RAW block device. The /dev/sdX file
device should still be created and accessible.

> Hello Mark,
>
>> I suspect you also did something that wrote to /dev/sda,
>> wiping out the partition table, rendering the drive
>> as not recognizable from within Microsoft Windows.
>
> If there was only a bad partition-table, I would be able
> to ACCESS it, and erase the partition.

If a bad partition table was the problem then it would be easy to recover
the data by accessing the /dev/sdX device. The fact that no /dev/sdX device
is created indicated that some other more fundamental problem is occurring.

>> You can use drives without a partition table,
>> but it is not a good idea if they are intented to be moved
>> across systems, because some systems may see
>> the drive as unusable or empty.
>
> aha. So how do I access a this drive "without a partition table"
> i.e. RAW????

Use the /dev/sdX devices and not the /dev/sdX[1-9] ones.

> Remember: I **DO NOT GET** a "DRIVE".
> It is like I have to LOW LEVEL REPAIR it.
>
> If anyone has a suggestion WHICH TOOL to try,
> make wild assumptions and crazy suggestions!!

One wild recommendation coming up.

1) get one USB sniffer (http://www.linux-usb.org/tools.html);
2) get a working USB drive as similar as possible to the one that want to
access. Another exactly equal would be ideal;
3) Disconnect any auto mounter to minimize the USB traffic;
4) activate the USB sniffer;
5) connect the working USB drive;
6) disconnect the working USB drive;
7) save the working USB traffic;
connect the non working USB drive;
9) disconnect the non working USB drive;
10) save the non working USB traffic;
11) Compare the working USB traffic with the non USB traffic.

If there is a significant difference in USB traffic between the devices then
a hardware problem is the most likely cause.

If it is a hardware problem but the flash memory is intact and is separate
from the controller chip then you (or someone with electronics experience)
may be able to swap the flash memories and access the data that way.

> And remember:
>
> It is bad luck to be superstitious!!

Only if you say it three times and don't knock on wood!

Regards.

Thank you, thank you very much.

> usbtools

good info!
... something to monkey around with on long winter evenings.

One would think that some programmer has already written an analysis-
programme
that has all the answers about what's happening on the US-bus.

I tried the HP_Drive_Key_Boot_Utility---cp006049.exe (50mB) but it too
is blind to my usb-memory-stick, can't see it.

DOS-USB drivers don't even start.. when the stick is inserted.

>> Can the chip be talked-to in a low-level access via USBus AT ALL??

your answer is a "probably not" ... I take it...

many thanks again.. I'll keep this thread updated as I find out new
things.

Am I ambivalent? Well, yes and no.

Gordon wrote:

> Strange how easily it is to get a digital copy, and yet the saying remains.
>
> There are two typoes of computer users: those that have needed a backup and
> those that who will need to have a backup.
>
> How much risk do you wish to carry? Data is valuable protect it, yes?

Yes, but when it is something that is logging to the USB device and it
fails, there isnt a backup at that stage.

For everything else there is online backups etc.

In article <b08bc997-be89-4f26-97bc-4d39c35f9cb5
@z1g2000prc.googlegroups.com>, says...
>
> Hi guys! Some #$%^& computer ruined my 2gig thumbdrive.
>
> executive summary:
> - Linux *fdisk* does not see the USBstick (udev does)
> - (every) Windows says: This device cannot start (Code 10)
>
> Details here http://y23.com/wiki/pmwiki.php/Main/RecoverySoftware
> (output of dmesg, udevinfo, lsusb)
>
> Knoppix, Winxp win98, HirenBootCD... a few old laptops.. available..
>
> I'd be stoked if someone helped to recover my data, I'll gladly send
> you a 2010 (or 2011) Astronomical Pocket Diary http://y23.com/apd or a
> lifetime subscription to the online Astro Diary http://y23.com/apdoe
> ..
>
> Always remember: Insomnia is nothing to loose sleep about!

Try test disk data recovery - dunno if it'll correctly see removable
drives...

http://www.cgsecurity.org/

I've used it for HDD data recovery and it works well.

--
Duncan.