• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mattiasnyc

Profile Information

  • OS
    Windows 7 x64
  1. Went to boot my computer and it wouldn't go past POST. BIOS couldn't find OS or drive. This was as I mentioned the OS drive and I didn't touch it prior to shutting down. I never initialize drives "willy nilly". The words "initialize", "erase", "format" etc throw up red flags in my brain and I've yet to be dumb enough to clean a drive from data. I'm plenty dumb in other ways to make up for it though. Then I went to the thread called " The Solution for Seagate 7200.11 HDDs" and went through the instructions and "unbricked" it. The symptoms of my drive conformed to the ones the "unbricking" would potentially solve. The drive then spun up properly and got detected by the OS. After that I tried absolutely nothing else but instead posted in this thread. I'm guessing "file based recovery" is some sort of time consuming scan where the software tries to intelligently piece together what binary constitutes a file, and what type of file that would be... Would that be the next step? Thanks again for your help and patience.
  2. Hi, downloaded and installed "tiny hexer". Again, this is an application that is way beyond intuitive for a non-programmer/hacker/whatever. Could you tell me what to type and where in steps? I don't even know where to start. (or alternatively let me know if there's a quick guide and what its name would be so I could learn the stuff).
  3. Q1: not really. I've never touched vista in my life, and 7 was just an os i messed sound with on the drive i have up and running now. It would be epic if it wasnt xp. Q2: i only recall having worked with one partition. I have a system with at least 4 drives normally so my usage is pretty compartmentalized. So i think it was one partition only. On it was xp x64, and it was fat or ntfs i suppose, but can unfortunately not recall which one.
  4. I believe what is attached is what you're looking for... Or hope rather... Pulled a 17-hour overnight work session so my brain has been pure garbage for the past couple of days. The joy of working in television. Anyway, let me know if the file is what you were looking for. I had a hard time finding out how to operate the **** program. I love command prompts as long as I know what the hell I'm doing which is not the case here. So just so you know what I did...: 1. Searched for "dsfo", found and downloaded, put .exe file in new folder called "apps" on C 2. Went to command prompts and typed in: C:\apps\dsfo \\.\PhysicalDrive6 0 51200 F:\drive6 where "PhysicalDrive6" was the damaged drive ID and "F" is a USB flash drive. I based the syntax off of what you wrote in a different thread, so I'm hoping it's accurate. I couldn't get rawcopy to work at first, probably because I screwed up the syntax. drive6.7z
  5. Yeah, I know, LoL, still with this issue right? So, here's the deal: I've been busy with a bunch of stuff and was about to give up on this when I remembered files that I now need so I figured I'd give it a shot and got into my head to plug in the original un-bricked drive just to see if testdisk would find anything on it, as opposed to the clone. In testdisk after the initial search I now found the following: >L, FAT16, LBA, 22947, 1 , 1 , 60799 , 254 63 , 600108382 Basically I'm now jumping back in the thread in response to your post #26, reporting back before I do anything else... ...standing by... PS. The commas in the string above are only there to give distance between numbers, they obviously don't appear in test disk.
  6. The above are two different things, right? The first addressing the first 16 sectors and the second talking about where the NTFS "lives", right? So I'm looking at re-running one of the tests over the whole drive to cover where NTFS "lives", and re-running the other test with dsfo or dd. Right? I'll have to get back to this later this evening, but "no", I was not prompted to "initialize" and I do not recall having changed the source or clone drives in any way (meaning their partitions). One day the darn thing wouldn't spin, that's all. The only thing I can think of is if I some how screwed up the de-bricking of the source (as far as me being the culprit is concerned). I'll come back later with more info.
  7. Thanks. I've attached HDhacker again, sectors 1 through 16 as that's all it took in one go. The DMDE result is pretty much zeroes in general and an NTFS search of the first 5GB shows nothing. I didn't really have time for anything else right now, but I'll try to do more in a by this evening. Sector_1through16.7z
  8. Done. Still nothing. Same options; add partition, load backup or enter to continue...
  9. Thanks. Can you tell I'm a noob at this? It's at 12%. I will report back.
  10. I've now run test disk through the "Quick Search" function and it has found no partitions at all. My options at the bottom of the screen are: "Keys A: add partition, L: load backup, Enter: to continue" please advise, and thanks for all your time and help!
  11. I will try this and NOT write anything until I've posted results here. One more thing: What do you refer to when you say "use the /log"? That particular sign/word ("/log") doesn't appear on the "testdisk step by step" guide page.
  12. Thanks jaclaz, I will try Testdisk today. Does it take hours to do its thing or is it a matter of minutes? (I have to work from home today because of the hurricane)
  13. For the record, I'm not sure I fully comprehend the procedure in getting the PBR (unless it stands for Pabst Blue Ribbon, in which case I know how to but just don't want to). Would it be unwise to move along to the next step with only a copy of the MBR and NOT the PBR?