GUID Partition Table & MBR Mistake

Koda239 · 24 Jan 2014

jumanji said:

My disk 1 is not initialised, and Windows is asking me to initialise.

I say OK boss, do it.

And the boss takes the order :) . Initialised.

The buck stops there. This is what happened in OP's case.

He merely initialised it. And initialising merely writes the MBR code into the first sector. Nothing more than that.

That first screenshot is exactly where I chose MBR.

gregrocker · 24 Jan 2014

So follow the steps I gave you in my last post to determine if you had that HD in a UEFI system, meaning it was most definitely GPT initialized, which you then changed to MBR. In that case change it back to GPT to see if you see the data and if you don't try the PW Partition Recovery undelete.

To double-check this look at the current format of the HD first, as I also showed you how to do.

jumanji · 24 Jan 2014

Sorry, it was bedtime for me and so did not see greg's post seven hours ago.

I would advise the OP to desist making any changes to the HDD at the moment.

The fact is if it was indeed a GPT disk ( which we do not know yet but easy to find out) writing the MBR code again into the HDD as had been done by the OP, should not alter the GPT status of the disk. So in my opinion, it is not necessary to do anything to make it GPT again. I am only worried that it may turn counterproductive.

My suspicion at the moment squarely centers around the dock used by OP. Yes, suspicion at the moment based on many users who had reported problems with older docks that were not designed to take cognisance of GPT disks. Is OP's one? ( He hasn't answered my question on it because perhaps he does not know anything about his dock.)

I shall now await OP's confirmation that he hasn't attempted anything or stop him doing that if he is still awake. For that purpose, I will close this post and come back again after a while.

gregrocker · 24 Jan 2014

I also have doubts about the dock so would do all operations with the HD plugged in internally if possible.

It's also critical to stay within the steps being posted and execute them fully and correctly - so if there's any doubt ask back before acting.

Let us know where you are in the steps given and detailed results.

jumanji · 25 Jan 2014

Yep, it is always desirable, to put the HDD either in a good external casing or hook it up into a desktop as a second drive and do all the troubleshooting for then we will be operating in a known environment eliminating the unknown add-ons.

But then the OPs may not always be equipped to do that. But again if it comes to that he has to do it.

So in this case I would first examine whether there are any telltale signs of the HDD being a GPT one.

Because of the unknown interface, I would not rely on the conventional partitioning software like partition Wizard or AOMEI Partition Assistant or even Windows but would rather examine the contents in the physical sectors.

To the OP:

Install Bootice ( the correct bit version of your OS) and examine the partition information. Booooooooting ? View topic - [ BOOTICE: A poweful boot-related utility ] - v1.3.2.1

GUID Partition Table & MBR Mistake-25-01-2014-09-41-23.jpg

Does it show the GPT header, GPT table, and the partition LBAs?

If yes, then take it out of the dock and put it in an external casing ( better still if you can hook it up as a second drive on a desktop). In all probability, you should be able to access the drive.

If no, then don't give up so easily.

Examine the last sector(nth sector), n-1 sector, n-2 sector, n-3 sector etc., upto about say n-10 sector. That is where the backup of the GPT data exists and if it is real GPT partition data even if it is missing in sector 1 to sector 62, the backup will always be taken and rewritten when you place it in an external drive(desktop) and you should be able to access the drive.

Note: All this only if it is really a GPT drive, and you have not manipulated the drive in any way on the dock ( save for the MBR write in sector 0 you had already done. For a GPT drive what is in sector 0 is irrelevant, in a sense, as long as the partition table in it -which will be read as a single unrecognised partition by GPT-unaware systems/programs - has not been overwritten. I believe your MBR write has only written the MBR code and not touched the partition table in sector 0)

For more information and acquaint yourself with Bootice Lost partitions! (But you will do only what is indicated in this post - examine and report.)

EDIT: Take screenshots using Windows Snipping Tool and upload it.

Koda239 · 25 Jan 2014

Sorry for the delay folks, I was having quite the time at work the past couple days. Just now touching base in this thread again. Gregrocker, Stand by... Taking a look at your previous post now & going to see if I can determine if my machine is UEFI or not. (Not even sure how to properly state that)...

UPDATE: Alright. I've done as you have requested. Here are the results I came up with.
I believe my computer my not support UEFI, however I might be wrong. The thread you provided was somewhat confusing to me. Attached are 4 images from my BIOS that might help you decide if it does or doesn't support UEFI. I did see that it has Legacy Something or other in it, I thought that might possibly be it but wasn't sure.

Attachments: Image 1, Image 2, Image 3, Image 4

When I load the disk in Disk Manager, I only have 4 options. Convert to Dynamic Disk, Offline, Properties, and Help. The option to convert to GPT Disk is "Grayed Out".

I have not tried the Partition Wizard option you suggested. Standing by for further suggestions on what I should do. Would you like for me to try the Partition Wizard option?

Thanks again!

jumanji · 28 Jan 2014

Hi Koda239,

As I said in my previous post - which you seem to have ignored in toto - I would examine the physical structure of that HDD. If it is a GPT drive you will see the GPT header, GPT Table and the NTFS VBR sectors.(as shown in the screenshot in the previous post)

If it is an MBR disk, you will see only the MBR, and VBRs as in the following screenshot.( In my case I have extended partition and logical drives in it. So EBRs and VBRs in the extended partition are also shown.)

GUID Partition Table & MBR Mistake-28-01-2014-12-40-24.jpg

And one more question: Did the HDD have any problems in the System because of which you removed it and replaced it with the SSD?

Note: Use Windows Snipping Tool to capture the shots and upload it.

EDIT: The presence or absence of the partition tables will tell us whether all is OK with the drive and the dock is standing in the way or something is radically wrong with the drive.

Koda239 · 28 Jan 2014

To my knowledge, I don't think there was anything wrong with the drive itself. I just needed larger space, so I purchased another drive.

I'll try Bootice. And correct, I didn't see your post, I apologize. I was still back-tracked on Greg's post on the previous page. I'll be performing that today.

Just a bit of situational awareness, I'm performing all these tests on my Windows 7 Professional - 32-Bit Machine in my house, attaching the drive by an Internal SATA cable and power. It is currently the only functioning Windows OS Machine that I have in my home. I've taken the dock out of the equation.

jumanji · 28 Jan 2014

That's good.

Post a screenshot of how the drive looks in Windows Disk Management in its new home even as you prepare yourself for the Bootice experiment. (Again with Windows Snipping Tool and uploading it to SevenForums server)

gregrocker · 28 Jan 2014

Eager to see a screenshot of Disk Management - Post a Screen Capture Image
with the drive attached. Let us also see the choices available when you rightclick the Disk Number box.

Pending confirmation of this using Jumanji's process, I believe you had and have an MBR install on the drive, but wonder why the drive needed initialization if you had not wiped it.

Next I would run Partition Wizard Partition Recovery Wizard - Video Help. Report back what it finds.

Please also post another camera snap of the Boot tab from BIOS.