Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Harddrive partitions - GRUB boot loader

  • Please log in to reply




  • Member
  • PipPipPip
  • 254 posts
I'm not actually sure where this post should go. It's kind of applicable to hardware, OS, software...

I recently upgraded my computer with:

Gigabyte P67A-UD3R-B3
Intel core i5 2500K
2x 4GB G.Skill Ripjaws DDR3 RAM
MSI Radeon HD6950 2GB
Seagate 1TB internal hard disk.

The issue i'm having is with my old Internal (A Samsung 1TB.)

On my old hard disk I had it split into a 700GB partition (Windows 7) and the rest had Ubuntu on it. After I upgraded, I reinstalled Windows 7 onto my new disk (had my old unplugged during the process.) After it was installed, and I plugged in my old disk and booted windows up - deleted the partitions on the old disk, and created a new 500GB one, leaving the rest unallocated. This worked fine all night and such - through multiple restarts.

Today I decided to have a little look at overclocking the 2500K, and after fiddling with the BIOS settings I saved and restarted. Usually what will happen is after the POST screen, it will say "Loading Operating System..." or something for a few seconds, then Windows will start loading. What happened though was that it went:

"Loading Operating System...
ERROR: Parition doesn't exist

Or something like that. Considering GRUB was the boot loader that went on with Ubuntu, I figured it had to be something to do with the old hard disk. I'm very unfamiliar with the whole boot sequence, and boot loaders and such, so I don't know how to fix it. Currently i've just unplugged the old hard disk so I could boot up.

Would anyone have an explanation and/or solution to this problem? As far as i'm aware the old disk has about a 500GB partition with nothing on it, and 500GB of unallocated space.

  • 0




    Grumpy Ol' MSgt (Ret.)

  • Retired Staff
  • 3,999 posts
  • MVP
Stop overclocking. At least until this is resolved - then make sure you have properly addressed heat control for all your components, not just the CPU, before bumping up the clock again.

My "guess" is you have 2 problems and the first is that the old disk is listed before the new disk in the BIOS Setup Menu boot sequence. When unplugged, the BIOS looks for the old disk, can't find it so moves on to the next device in the boot sequence. When plugged in, it finds the old disk first and tries to load from it, but chokes. So you need to verify the new disk is listed before the old in the boot order sequence in the BIOS Setup Menu.

I think the second problem is a corrupt MBR - See, Restore Windows 7 MBR. Just make sure you select the right drive.
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP