New
#171
I boot testdisk from a usb heh
this is when I first tried it,
then today I did testdisk again it became like this
I am backing up my data now & I will probably send seagate an email together with a link to this thread & ask them about the hdd ^^
thanks for the help guys! XD
I'm so grateful you came back to share what you found.
When you say you booted testdisk from a USB:
-- OR --
- does that mean you had testdisk stored on the USB, and just launched it from there (in other words, you booted your machine normally via your installed OS and simply launched testdisk from where it was stored on a USB)?
I'm surprised to see that drive represented the way it is, in both screenshots, just with a couple of insignificant differences between the two. The drive appears to be represented as three separate entries in each screenshot. Now that the drive is "fixed" I would've expected to see only one entry that represented the problematic drive.
- does that mean you booted your machine off of a bootable USB, and then ran testdisk?
I'm missing something stoleaway. Both of those screenshots look the same to me. I know that they are differnt - the background changes slightly. Please enlighten me - what do you see that I don't?
Would you mind explaining the process used to put Testdisk on the USB and make it bootable?
You are welcome stoleaway, glad you are able to get your data.
Good luck with Seagate, I'm sure they'll make it right.
Most importantly - thank you for sticking through a difficult trouble shooting session. Your system is up-to-date too.
Two weeks is about my limit with my own machines, and we made it just iunder the wire. I was very glad to hear the news.
Bill
.
The only two differences I can spot relate to drive locations (dev/sdb vs. dev/sdd and PhysicalDisk1 vs. PhysicalDisk3).
As far as I know, there is no "bootable version" of Testdisk. But it can run on many OSs, and is included in a few live iso's (although it is usually not the most up to date stable version). Or he could've just used some USB with a bootable system on it and run it from the location he originally downloaded it to on his hard drive.
You're most welcome! Hopefully you can grab all of the data off of it while it's relatively responsive.
Please let us know if you're able to finish copying out your data, and how it goes with Seagate as well.
Yeah, the only problem with "this close" is it often remains that way forever!
It's like trying to get somewhere by cutting the distance travelled in half - there's always the other half to travel.
10 miles to go, 5 miles to go, 2.5 miles to go, 1.25 miles to go.........
But sure, I am persistent - another thing I like to try is the "give it a rest" method. I'll come back to a problem months later and the bits have magically healed - try one last ditch effort and Wow, it works.
Did you get all of your data off of the drive? Great if you did!
Ok, seriously - please tell me what you and F5ing see in the two images that I'm missing.
edit: never mind - thanks Steve, I see it now
And also please describe the USB procedure you used - was it a bootable USB? How did you create it - what tools, methods?
The information might help other members. I'm helping on another thread with a similar yet different ext HD issue - they can't get as far with Testdisk in Windows, maybe the USB route will help.
Thanks,
Bill
.
Thanks Steve, I missed that. Sheesh - 20 times I missed that. But I did notice the version 6.14 - that's the beta version, stable is 6.13. C'est la vie! - it worked.
As you noted, Testdisk site references Live CDs (Hirens, UBCD, etc). It would be useful to know how stoelaway did it. I suppose you could run command from a Windows install disk, if you put Testdisk on the Flash drive.
I forgot to mention that your suggestion, running Testdisk offline, was a great one. Appearantly stoleaway came to the same conclusion or took your advice and that seemed to help immensely.
Thanks to all - we saved the patient!
Bill
.
Hum Bill and F5 what a performance I suppose in hindsight it might have been worth doing a TeamViewer session and you could have had a "fiddle" with the thing
You were on the right track in the beginning with the Ubuntu boot - not sure about PartWiz though, it's a different beast. Since you have a "dead" external, you have a great opportunity to play with Testdisk trying to ressurect your drive. Remember, you can do all sorts of scenarios before that write command finalizes your decisions Read up on the Tesdisk site - the documentation is deeper than I originally thought.
Thanks for your help on this one John.
I don't make housecalls