GPT drive problem or...

PetarPan

Distinguished
May 18, 2011
4
0
18,510
Hi,

Today, I've installed 2TB Samsung F4 on rather old system (AMD nForce4 based), disk got recognized by the BIOS, Windows too... However, after choosing to initialize it as a GPT disk, and rebooting, PC wouldn't boot any more. New drive would still be recognized, but it just hangs at the IDE detection phase (it correctly displays all devices).

I hope I'm not posting on the wrong forum, but I got the idea that somehow choosing GPT instead of MBR cause the problem. I did try the disk on another computer (same chipset), and I got the same symptom. Also, I'm thinking, if it got recognized initially, without any partitions, and everything worked, it should rule out BIOS not supporting 2TB drive...

Disconnecting new drive solves the problem. Other drives are WD Blue 640GB. Same symptom if only Samsung is connected to the motherboard. If anyone has the idea regarding the issue I've described, or had a similar problem, please let me know. In the meantime, I'll try to connect the drive to P35 system and see what happens...

Thank you in advance
 
It's Windows 7 installed on one WD drive. It uses MS drivers. But since it doesn't even start loading windows, I'm not sure it's driver related. Windows did recognize the drive in the first place, and let me create partitions on it. Can't even boot from DVD...

Also, I forgot to mention, with Samsung HDD connected, PC won't enter BIOS any more, just hangs on IDE detection screen.
 


Samsung is not a boot disk. Wasn't set up to be. I don't know when i disconnected it if that affected boot order, but since I can't get into BIOS, don't know how to change it...
Will try to clear CMOS and see what happens (F4 is on SATA 3 port)
 


Hi,

I have exactly the same behaviour:
On a "Tranquil PC" platform (1,5 GHz Intel Celeron, 512 MB RAM), I set-up a Compact Flash to boot the FreeNAS FreeBSD OS.
The last 2 editions of FreeNAS take "advantage" of using GPT.
After my SATA 160 GB was GPTed, no way to boot on the CF anymore.
The BIOS lists the drives, and then stops without attempting any boot process.
If I disconnect the SATA drive, boot is OK. After booting was completed, I re-connected the SATA HD. I had to rescan disks within FreeNAS but things do work.
However, as soon as a reboot is launched, I come across the same issue.

I tried to browse within the BIOS options and toggled some, without any success.

I am very interested in knowing why the presence of a GPT HD could stop the booting process ...