Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 23 Oct 2014, 08:45
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
TestDisk: Flash Drive="CHS and LBA don't match" [SOLVED]
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 9 of 11 [156 Posts]   Goto page: Previous 1, 2, 3, ..., 7, 8, 9, 10, 11 Next
Author Message
Sylvander

Joined: 15 Dec 2008
Posts: 3457
Location: West Lothian, Scotland, UK

PostPosted: Mon 18 Mar 2013, 05:03    Post subject:  

Code:
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 
Bus 001 Device 003: ID 0a16:2004 Trek Technology (S) PTE, Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0024 
Bus 002 Device 003: ID 1a86:7584 Unknown
Bus 002 Device 004: ID 04d9:1133 Holtek Semiconductor, Inc.
#
Back to top
View user's profile Send private message 
amigo

Joined: 02 Apr 2007
Posts: 2258

PostPosted: Mon 18 Mar 2013, 05:29    Post subject:  

So, it's finally working for you. Great!
Back to top
View user's profile Send private message 
linuxcbon

Joined: 09 Aug 2007
Posts: 763

PostPosted: Mon 18 Mar 2013, 07:51    Post subject:  

amigo wrote:
So, it's finally working for you. Great!
No.
Back to top
View user's profile Send private message 
Sylvander

Joined: 15 Dec 2008
Posts: 3457
Location: West Lothian, Scotland, UK

PostPosted: Mon 18 Mar 2013, 11:45    Post subject:  

linuxcbon wrote:
No.

Agreed.
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Tue 19 Mar 2013, 12:04    Post subject:  

Hi Sylvander,

First, I am assuming that you had only your troublesome flash drive plugged in when you ran lsusb. (That's what I wanted, but neglected to say so.) Only one was listed, so it looks like that was the case. Correct?

(If that's not the case, then my assumptions below about the identity of your drive may be wrong.)

I was surprised that it was not listed as a Verbatim product, but it appears that Verbatim sometimes sells devices from other manufacturers such as Kingston Technology, and Trek Technology. The "0a16" manufacturer code identifies yours as being from Trek. I've found no information about the "2004" product code.

In order to find a low level format utility that is known to work with your drive, we need to identify the controller chip used. One might hope that this would be an exact science. There are certainly bloggers on the Web that give one the impression that it is. But such is not the case.

Given the vendor and product codes (0a16:2004 for your drive), it would be nice to just plug those numbers into a data base somewhere and find the controller chip that is used in that product.

And there is a database in Russia that does indeed let you plug those numbers in (http://www.flashboot.ru/iflash.html). But in some cases this results in a list of many chips. And in other cases (such as your drive's 0a16:2004), nothing is found.

Apparently manufacturers use various suppliers for the controller chips that are used in a single product. That is not surprising, but it does make it hard to identify the chip using only the vendor and product codes. What is surprising is that a single vendor and product code can result in a list of devices with various memory sizes. I would have thought that a vendor would assign different product codes for drives of different sizes. But perhaps some vendors consider a product to be one product available in different sizes. It is also certainly possible that the database contains a lot of misinformation -- not surprising since at one time the database was open for anyone to add data. And it is also possible that some of the data was reported based on data from counterfeit flash drives, and so that data is not legitimate.

Anyway, searching just on the vendor code "0a16" gave a short list of flash drives described as "Verbatim Store 'n' Go", or "Verbatim Store 'n' Go Mini". So we are getting warm. Most entries indicated that these use the Trek "TD2SMG12L" controller chip.


So, did I find any utility that you might try? Yes.

I had hoped to find a utility that came from a manufacturer's web site, as was the case for the other utility that you tried. But I didn't. I am less likely to trust something downloaded from some file-sharing web site, and am reluctant to even mention any, lest your "Mini-XP" become infested with some virus.

So first I am going to suggest a newer version of the utility that you already tried. I'm not very hopeful that a newer version will work any better for you than the old one did, but I think it would be safer to try that first, since it comes from a manufacturer's web site.

Looking into the binary, I see references to many chips, so apparently this utility is not limited to one type of controller chip (which explains why someone got it to work with a non-Apacer drive). My guess is that when you got the "USB Flash disk not found", it was not because it couldn't see your flash drive, but because it didn't find a flash drive that was supported by the utility. My hope (although it's not much hope) is that support for your drive has been added to the newest version.

A little digging turned up many versions of the utility at the Apacer web site. I'll document the full list here, but I would suggest that you not bother trying any other than the newest one, for which I've added a live link:

http://www.apacer.com/en/support/downloads/HS2.0_Utility_Repair.zip
2004-04-28 225280 bytes HS20_RepairTool/Repair.exe

http://www.apacer.com/en/support/downloads/HS2.0_Utility_Repair_2.zip
2005-12-16 208896 bytes 2134repair_v2.3.1/Formatter.exe

http://www.apacer.com/en/support/downloads/HS2.0_Utility_Repair_3.zip
2006-07-28 270336 bytes Repair2611/Formatter_2611.exe

http://www.apacer.com/en/support/downloads/Repair_v2.8.1.1.zip
2007-04-09 233472 bytes Repair_V2.8.1.1/Formatter.exe

http://www.apacer.com/en/support/downloads/Repair_v2.9.1.1.zip
2008-03-12 503808 bytes Repair_v2.9.1.1.exe

http://www.apacer.com/en/support/downloads/Repair_v2.9.1.8A.zip
2009-06-12 528384 bytes Repair_v2.9.1.8A/Formatter2.9.1.8A.exe

http://www.apacer.com/en/support/downloads/Repair_v2.9.1.9.zip
2009-12-18 524288 bytes Repair_v2.9.1.9/Formatter.exe

http://www.apacer.com/en/support/downloads/Repair_v2.10.1.1.zip
2010-03-29 512000 bytes Repair_v2.10.1.1/Formatter.exe

(These files also live in an alternative directory: http://ap.apacer.com/pub/media/file/downloads/)

Again, the only one worth trying is the newest, v2.10.1.1; if that doesn't support your drive, it is unlikely (though not impossible) that the older ones will.


If that doesn't work, there are a couple of more you can try.

It looks like the best utility for the TD2SMG12L controller chip is this:

http://flashboot.ru/files/public/USBest/Super_Stick_Recovery_Tool_V1.0.2.19.rar
2008-12-04 6029380 bytes Super Stick Recovery Tool V1.0.2.19.exe

(If your "Mini-XP" doesn't support .rar files, and your Puppy doesn't already have the unrar utility (i.e., the unrar command says, "bash: unrar: command not found"), you will also need to get that utility, which is available on the forum here: http://www.murga-linux.com/puppy/viewtopic.php?p=655167#655167)

Again, I am reluctant to suggest files from unknown web sites, but at least flashboot.ru is not just a file sharing web site, and looks fairly legitimate to me. This is the same site that has the database used earlier for looking up the flash drive controller chip. They also have a copy of the Repair_v2.9.1.1.exe file that you downloaded from the Apacer web site. I checked and verified that the one from flashboot.ru is exactly the same as the one from apacer.com, which gives me hope that nothing nasty has been added to their files. (Of course, I can make no guarantees.)

If you choose to try it, you'll need to run it in your "Mini-XP".

If your "Mini-XP" doesn't support .rar files, you can use Puppy to extract the executable like so:

1. Download the file to your /root/ directory.

2. Run these commands:
Code:
mkdir /root/supper_stick
cd /root/supper_stick
unrar e /root/Super_Stick_Recovery_Tool_V1.0.2.19.rar

(Naturally, you then need to move the executable to a place where "Mini-XP" can find it.)


If this utility doesn't help, I know of one more you could try, but will wait 'till we see how this one did before I post that.


Again, I hasten to point out that I have no experience with this utility. I only know that others claimed to have used it successfully with a flash drive containing a Trek TD2SMG12L controller chip.

And I don't even know for sure if your drive has a TD2SMG12L controller chip, since I found no information on your product code (PID) "2004". I only know that all the "Verbatim Store 'n' Go" drives listed with your vendor code (VID) "0a16" used that controller chip, so maybe yours does as well.

So again I remind you that it is possible that the use of this utility could damage your flash drive beyond repair. But since you have already tried the other utility despite a similar warning, I'm guessing you have decided that you will be no worse off than you already are if it does.

And, as we all know, it is certainly possible that we are beating a dead horse. Your drive may have been ready to send to the knackers weeks ago. I only keep making suggestions because I admire your determination to exhaust all possibilities before doing so.

Good luck.
Back to top
View user's profile Send private message 
Sylvander

Joined: 15 Dec 2008
Posts: 3457
Location: West Lothian, Scotland, UK

PostPosted: Wed 20 Mar 2013, 06:38    Post subject:  

Posting from FalconFour's_UBCD->MiniXP.

1. Yes, had only my troublesome flash drive plugged in when I ran lsusb.

2. Downloaded Repair_v2.10.1.1.zip to a folder on sda2 [FAT32], unzipped it to the same location, and the exe file was auto-placed in its own sub-folder.

3. Rebooted to FalconFour's_UBCD->MiniXP, navigated to the Formatter.exe file, right-clicked it and chose Open.

4. BAD NEWS! Sad
Got the same failure = USB Flash Disk not found!
Used Windows Explorer to delete the folder plus exe file plus zip file.
Will now attempt to download [to the same folder as before] the next suggested tool/file [rar file] and attempt to unpack etc.
7-zip available and tried, but failed to unpack; will go back to Slacko to do the work.

5. Back in Slacko, tried the following on the downloaded rar file:
[I opened a console in the folder holding the file, from within Xfe]
Typed unra and hit <tab>, which completed the commandname=unrar [therefore must be correctly spelled], so it is installed; discovered on my own that "e" was needed, repeated unrar with e, typed S and hit <tab> to complete the filename [therefore also must be correct], and hit <Enter>.
Code:
# unrar e Super_Stick_Recovery_Tool_V1.0.2.19.rar

UNRAR 3.71 beta 1 freeware      Copyright (c) 1993-2007 Alexander Roshal

Super_Stick_Recovery_Tool_V1.0.2.19.rar is not RAR archive
No files to extract
#

Did I get the command right?
This gives the same result as in MiniXP ["is not RAR archive No files to extract"].
Is it truly not a rar archive?

Very thankful for your assistance, and enjoying the learning experience. Very Happy
Back to top
View user's profile Send private message 
Karl Godt


Joined: 20 Jun 2010
Posts: 3972
Location: Kiel,Germany

PostPosted: Wed 20 Mar 2013, 11:07    Post subject:  

http://packages.debian.org/source/squeeze/rar : The src .tar.gz includes a rar_static binary . Version is 3.93 now.

Fails to unrar ?
Could think of unsupported compression algorithms or a needed password Very Happy

[EDIT:]
Nope: Both 4.2.0 from sid repo and 3.9.3 : rar_static extracted it with no problems . Firefox did not dl correctly since i am on 7,65KB for the rest of the month. Needed to copy dl-link and
wget -c http://flashboot.ru/files/public/USBest/Super_Stick_Recovery_Tool_V1.0.2.19.rar

:
Extracting Super Stick Recovery Tool V1.0.2.19.exe OK
Extracting FlashBoot.ru.URL OK
All OK
bash-3.00# pwd
/root/Downloads/rar-4.2.0
bash-3.00# cd ..
bash-3.00# rar e Super_Stick_Recovery_Tool_V1.0.2.19.rar
RAR 3.93 Copyright (c) 1993-2010 Alexander Roshal 15 Mar 2010
Shareware version Type RAR -? for help
Extracting from Super_Stick_Recovery_Tool_V1.0.2.19.rar
Файл загружен с сайта
-------------------------
http://www.flashboot.ru
-------------------------
Extracting Super Stick Recovery Tool V1.0.2.19.exe OK
Extracting FlashBoot.ru.URL OK
All OK
bash-3.00#
Back to top
View user's profile Send private message Visit poster's website 
amigo

Joined: 02 Apr 2007
Posts: 2258

PostPosted: Wed 20 Mar 2013, 13:30    Post subject:  

What is not working? This:
Code:

 ~> fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 512 MB, 512229376 bytes
16 heads, 62 sectors/track, 1008 cylinders
Units = cylinders of 992 * 512 = 507904 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        1008      499937    c  W95 FAT32 (LBA)

Command (m for help): q

~> mkdir /mnt/sdb1
~> mount -t vfat /dev/sdb1  /mnt/sdb1
~>  cp sylpheed.desktop~ /mnt/sdb1/
~> ls -lta  /mnt/sdb1/
total 24
drwxr-xr-x  2 root root 16384 2013-03-17 14:13 .
-rwxr-xr-x  1 root root   456 2013-03-17 14:13 sylpheed.desktop~
drwxr-xr-x 15 root root   140 2013-03-17 14:12 ..
indictaes that the partition is properly recognized and you were able to format it and copy a file to it. What is not working?
Back to top
View user's profile Send private message 
linuxcbon

Joined: 09 Aug 2007
Posts: 763

PostPosted: Wed 20 Mar 2013, 13:38    Post subject:  

amigo wrote:
indictaes that the partition is properly recognized and you were able to format it and copy a file to it. What is not working?
It's not him, it's someone else's disk...
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Wed 20 Mar 2013, 13:53    Post subject:  

Sylvander,

Sylvander wrote:
Code:
# unrar e Super_Stick_Recovery_Tool_V1.0.2.19.rar

UNRAR 3.71 beta 1 freeware      Copyright (c) 1993-2007 Alexander Roshal

Super_Stick_Recovery_Tool_V1.0.2.19.rar is not RAR archive
No files to extract
#

Did I get the command right?

Yes you got it right.

Perhaps it needs a newer version of unrar. You have "3.71 beta 1". I have "4.00 beta 3". Karl had success with "3.9.3 and "4.2.0".

Try downloading the .pet file from the Puppy forum -- it is the one that works for me: http://www.murga-linux.com/puppy/viewtopic.php?p=655167#655167

Also, just to be sure that file downloaded okay for you, what do you get for this?:
Code:
md5sum Super_Stick_Recovery_Tool_V1.0.2.19.rar

I get:
Code:
# md5sum Super_Stick_Recovery_Tool_V1.0.2.19.rar
a668b4fb9a5b303782f65171b18cdd12  Super_Stick_Recovery_Tool_V1.0.2.19.rar
#


Sylvander wrote:
Very thankful for your assistance, and enjoying the learning experience. Very Happy

Good. So far I am enjoying it as well.

----------------------------------------------------------------

Karl,

Thanks for verifying that unrar 3.9.3 and unrar 4.2.0 extracted the file OK. I'm hoping that a newer version of unrar will work for Sylvander as well.
Back to top
View user's profile Send private message 
Karl Godt


Joined: 20 Jun 2010
Posts: 3972
Location: Kiel,Germany

PostPosted: Wed 20 Mar 2013, 17:24    Post subject:  

Norman, it is possible that rar changes the algorithm like .rpm do, so older extracting tools won't probably work on newest .archive s . The Superstick*.rar is made Dec. 2010 and according to http://rescene.wikidot.com/rar-versions rar-3.7.1 came out Sep. 2007 . .. I'm wondering a little that Slackware has such old repo items .
Back to top
View user's profile Send private message Visit poster's website 
Sylvander

Joined: 15 Dec 2008
Posts: 3457
Location: West Lothian, Scotland, UK

PostPosted: Thu 21 Mar 2013, 05:18    Post subject:  

npierce:
Tried the following:
1.
a.
Code:
# md5sum Super_Stick_Recovery_Tool_V1.0.2.19.rar
d41d8cd98f00b204e9800998ecf8427e  Super_Stick_Recovery_Tool_V1.0.2.19.rar
#

md5sum is incorrect?
Hence, no wonder the [newly installed] version 4 of unrar also gets "is not rar archive" when attempting to unpack the file.
I'll have a go at re-download of the rar file.
b. Re-downloaded the rar file and now get:
Code:
# md5sum Super_Stick_Recovery_Tool_V1.0.2.19.rar
a668b4fb9a5b303782f65171b18cdd12  Super_Stick_Recovery_Tool_V1.0.2.19.rar
#

Looking good. Very Happy
Will now attempt to unpack.
c. Here's what I now get:
Code:
# unrar e Super_Stick_Recovery_Tool_V1.0.2.19.rar

UNRAR 4.00 beta 3 freeware      Copyright (c) 1993-2010 Alexander Roshal

Extracting from Super_Stick_Recovery_Tool_V1.0.2.19.rar

Extracting  Super Stick Recovery Tool V1.0.2.19.exe                   OK
Extracting  FlashBoot.ru.URL                                          OK
All OK
#

SUCCESS! Very Happy

2. Will now reboot into "FalconFour's_UBCD->MiniXP", and attempt to run the exe file on the problem Flash Drive.
SUCCESS! The program runs. Very Happy
Dare I continue?
Displays: Kingmax - Super Stick Disk Recovery Wizard.
Displays images of 4GB and 8GB drives [as the drives to which it would normally be applied?]
Displays Verbatim Store-n-Go, (D), 964MB in window as detected drive, with update and close buttons, and 0% completed.
Should I click on update?
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Thu 21 Mar 2013, 06:49    Post subject:  

It's very encouraging that it recognizes your drive. Like I said earlier, I've never used this utility, but Update would seem t be your best option. I can think of nothing better to try. If it were my drive, I'd click.

Good Luck.
Back to top
View user's profile Send private message 
Sylvander

Joined: 15 Dec 2008
Posts: 3457
Location: West Lothian, Scotland, UK

PostPosted: Thu 21 Mar 2013, 07:53    Post subject:  

SUCCESS!
1. I now have a new single partition that occupies all of the space on the drive, with a FAT32 filesystem. Very Happy
2. And it is now mounted. Very Happy
3. And I've made a new folder on it, and copied a file to the folder [the .png file including the image displayed below], and opened the file, and it displays OK. Very Happy
Then deleted the folder and file.

4. I can now mark this thread [SOLVED].
Cheers and applause for npierce.
Many thanks to ALL who assisted. Very Happy

Illustrates the point: don't give up too quickly on hardware that appears faulty or dead.

5. Is there any more to be done to this?
I notice the drive is only 696 MiB instead of 1GB.
00.png
 Description   
 Filesize   28.48 KB
 Viewed   2708 Time(s)

00.png

Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Thu 21 Mar 2013, 08:18    Post subject:  

Yay! Smile

That is good news!

If I were a betting man, I probably would have bet that your drive was dead.

But when a dozen Puppy users get together to work on something, good things happen.

(Still, I probably wouldn't put any irreplaceable files on that drive. Smile )
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 9 of 11 [156 Posts]   Goto page: Previous 1, 2, 3, ..., 7, 8, 9, 10, 11 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1333s ][ Queries: 12 (0.0173s) ][ GZIP on ]