[blackillusion]

jaclaz, on 16 March 2013 - 12:50 PM, said:

NO need to apologize at all, but still we have "only" 4 partitions in this view AND we do have now a "new"[BOOT] partition that has however an "improbable" size.
Try pressing Enter and doing a Deeper scan...

In any case running gdisk seems like a good idea.

jaclaz

Running Testdisk deeper search was taking forever I would have leave it tonight if you think that testdisk will help.

Im a bit clueless on gdisk :

[jaclaz]

blackillusion, on 17 March 2013 - 01:20 PM, said:

Im a bit clueless on gdisk :

Which makes a nice, round, TWO of us!

However it shows the exact same partitions TESTDISK showed once in GPT mode.
The only tool (till now) that "sees" something more (or better) is DMDE.

Ysing the "r" and then the "v" option in gdisk should only provide additional info (and not change the disk contents):
http://www.rodsbooks.../repairing.html

jaclaz

This post has been edited by jaclaz: 17 March 2013 - 01:48 PM

[Tripredacus]

If this is Windows 8 on a GPT disk, that MSR partition is required. I'm not sure what it does exactly or how the OS would react without it, but it is a requirement for deployment. I wonder if you can add it back in with that unallocated space.
http://technet.micro...y/hh825686.aspx

I should try it out, see how Win8 reacts to that partition suddenly disappearing.
edit: will have to wait until monday...

[blackillusion]

Well here is one for you. I changed sector size on testdisk to 512 ran a quick search it found the partitionas like dmde. I then decided to put in in the laptop and try the recovery disk "automatically repair" and it found the boot and os partitions and repaired them. I am able to boot to windows now no problems.

[jaclaz]

blackillusion, on 18 March 2013 - 10:14 AM, said:

Well here is one for you. I changed sector size on testdisk to 512 ran a quick search it found the partitionas like dmde. I then decided to put in in the laptop and try the recovery disk "automatically repair" and it found the boot and os partitions and repaired them. I am able to boot to windows now no problems.

That's good news though of course we don't really know what actually was the issue, nor what could have been the actual fix .
Maybe the actual issue was the originally presumed one (some kind of mismatch between 512 and 4096 bytes sectors) but I wonder how it can happen (unless the original laptop BIOS *somehow* sees the disk as being 512 byts/sector while when you mount it "externally" to your "work PC" it is seen - correctly - as 4096 bytes/sector ).

However, the only important thing is that you are now among the happy bunnies in the basket.

jaclaz

[blackillusion]

Indeed I have no idea of what sorted it. Thanks for your help, maybe this sort of question may come up again.