Jump to content


  • Content Count

  • Joined

  • Last visited

About sanguillen

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks, dickster. Sorry for such a late reply on this, but I'm only getting around to taking care of this now. So if I'm understanding this correctly, I can restore it back to when it first came out of the box (ie. Windows 8), but anything added to the laptop after that (ie. programs such as an anti-virus, Microsoft Office, etc, or family photos or whatnot) would be lost, correct?
  2. Thank you for responding, Signman - sorry it took me so long to get back to you. To answer your question, the bottom of the Acer lists a model number of R3-431T-P071.
  3. After all the wonderful help I received regarding my HDD issues, I thought I might be able to get some help in tackling a different problem. A couple of years ago, my wife purchased an Acer laptop with Windows 8 installed. After getting tired of all the Windows 10 popup bubbles that kept showing up, we finally relented and upgraded. Since then, there have been a myriad of problems, from USB ports suddenly not working to printer drivers not working, to whatever. They resolve by either rebooting or just putting the laptop to sleep and then waking it up, but the nuisance of that is starting to grate us. I did a bit of research awhile back and found out that Windows 10 should only be installed on systems that, for lack of a better term, can "handle" it. There was, of course, NO warning whatsoever of this little nugget in the messages, or elsewhere). I then checked Acer's site and sure enough, this laptop was manufactured too early to be properly equipped to handle Windows 10. Obviously if I could go back and do it all over again, I would leave the laptop alone with Windows 8. My question is, do I have any options going forward? As I'd implied above it's been a couple of years now, so whatever option the Windows 10 upgrade came with to revert back (I think it was 30 or 60 days or something) has long since expired.
  4. In hindsight, if you had told me at the beginning that by the end of it we'd be able to save almost all the files but that I might have to go through and identify and rename about 25% of them, I would have taken that in a heartbeat. So for that, and for the tireless efforts of yourself, caintry and nigsy, I give you a heartfelt thanks. You all provide a fantastic service here, and on your own time to boot. This round's on me.
  5. Here is the screenshot after I choose Repair MFT: I'm guessing that you weren't expecting to see anything different from that, and that we've exhausted any hope of recovering the 0 kb files - short of me sifting through the files saved by Disk Digger, figuring out which ones are the ones that are showing as 0 kb on the old drive, and renaming those. But TestDisk identified the drive as Intel (I distinctly remember that part), so I'm not sure how you would have known to rebuild the mbr with efi gpt?
  6. The two Testdisk pics in that last post are where I am currently at, which is still the one 3.0 TB partition showing in Windows, all files and folders list in Windows, but some files at 0 kb. I'm wondering that if I did something wrong and the format didn't take (maybe I accidentally hit "cancel" at some point), then all the last couple of steps did was restore it to this same point, where I never got to the "choose boot and post screenshot" and "choose repair MFT and post screenshot" stage?
  7. Maybe I screwed something up with the quick format? Anyway, I've done the Write as you specified, and it now comes up as: And when I choose Boot: So I think I'm back to where I was just before the following from you regarding the quick format (one 3.0 TB partition showing in Windows, all files and folders list in Windows, but some files at 0 kb): Should I try and do the quick format step again? I'm trying to figure out where I screwed it up because it seems clear I goofed with something....
  8. Before the format, the drive was showing in Windows as 1.90 TB used and roughly 860 MB or so as "free", so I think Windows was recognizing it as a 3.0 TB drive even then. I think the 860 MB "free" represented all the 0 kb files. Merging the partitions didn't really do anything good or bad. But since doing the quick format, I get the same messages that I got early on: that it's RAW, and when I click on it in Explorer it tells me it needs to be formatted, and that "H: is not accessible. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted". When I hit Type, the following shows up: I think even before the rearranging of the partitions and the quick format, all the files were indeed listing in Windows. But some of them were showing up in Windows (and in TestDisk) as 0 kb. Listing the files in TestDisk, they appear the same now as they did before (I don't believe that part has ever changed in TestDisk, even when the drive was first inaccessible) - all files and folders listed, but some are still listed as 0 kb.
  9. Here is a list of one of the subfolders: I'm not seeing an option to choose Boot or Repair MFT? The last screenshot above is what I see when I choose "Advanced"....
  10. Thanks for the guide help. I've gone ahead and done what you and Terry have suggested. After Analyse the efi gpt drive, I get the following: When I hit Quick Search, I get the following:
  11. Thanks to both of you for your continued efforts on this. I ran chkdsk /r (I've already invested a lot of time into this, as have you both, so what's a little more right?), but it found no errors. So I still have some files that are being reported as 0 kb. Disk Digger initially rescued the files, but there are a boatload that I'll have to open individually to determine which one is which as they are all named "avi file at sector xxxxxxxx". I tried making it all into one partition (the 8 mb, the 2.0 tb, and the 7xx gb unallocated), but nothing has changed. At this point, I'm thinking I'll try the first option you listed above and if that doesn't work, I'll call it a day. Just so I understand, what would the steps be regarding quick format and then rebuild the file system?
  12. To see if chkdsk fixes the 0 kb files, would the command be the following? chkdsk /f H:
  13. On the highlighted drive, I'm getting the same " "Can't open filesystem. Filesystem seems damaged." that I got before. When I highlight the second one in the last screenshot, it does list all the files....but I don't know if that's just the same drive that I rebuilt back on page 1 (reference post of August 17), and therefore redundant to it to drive? It does look like the one I wrote in Page 1 had a "Start" of 267350 whereas the second drive in the last screenshot above has a "Start" of 16384 (both have the same "End" point), but I have no idea if that difference means anything. ETA: Actually, I see that the difference in the "End" from the first two drives in that last screenshot (426xxxxxxx vs. 586xxxxxxx) is about the same ratio as the 2.0 TB vs. 2.7 TB of data, so the differences in the two "Start"s is not my missing data, correct? I guess at this point it can't hurt to try running chkdsk on it, before giving up the TestDisk ghost and doing the quick format? Or maybe try caintry's EaseUS suggestion if chkdsk does nothing and if EaseUs doesn't work either, then give up and to the quick format?
  14. So the Deeper Search finally finished. This is what it looked like just before finishing: And this is what it looked like when it finished: So I should make the highlighted one Primary, and then list the files on it and if happy, write to it? And if not happy, run chkdsk as a last resort before the quick format?
  15. OK, I'll post back with my results once Deeper Search is finished. Would there be a point to running chkdsk before doing the quick format gpt that shows a single 3 TB NTFS partition, if TestDisk does not show the partition you listed above?
  • Create New...