#%&*ing Partition (Drive)! PLZ HELP!

This forum is for help with and discussion about your video hardware.

#%&*ing Partition (Drive)! PLZ HELP!

Postby Akashio » Thu Aug 04, 2005 9:29 pm

I just got a 250GB SATA-II HDD, installed it, and decided--to make my editing programs run faster--that I would copy my bootup partition onto this new drive, delete the old partition, and boot up like a happy clam.

Well that's what I did with Partition Magic 8.0 and things have gone horribly wrong.

It seems that now I can't boot up at all. I'm sure I made this new (copied) partition primary and active in Partition Magic 8.0! Obviously though, my computer does not agree with me. What can I do? (FYI, when I select the new drive to boot up, the BIOS says, "NTDLR is missing, press Crtl-Alt-Del to restart")

I've tried using fdisk, but when I go into the "set active partition" menu, although it shows two partitions (one of them the copied bootup), it says "no partitions available to set active." I guess all my drives are NTFS, but still, there is an "A" before the copied bootup partition! Doesn't that mean it IS active?

I've even tried re-installing windows. It doesn't work! It says every partition is not Windows XP-compatible! Even when I delete an empty, formated partition and ask XP to install there, it even rejects that!

Can anyone help me with this? I REALLY need my computer! Don't let a fellow nerd commit suicide!
User avatar
Akashio
 
Joined: 25 Nov 2001

Postby Beefy_Suavo » Thu Aug 04, 2005 10:11 pm

I never used Partition Magic, so I'm not familiar with it.

Is your SATA controller built-in to the motherboard or is it an add-on PCI card?

Did Partition Magic copy just the partition, or did it copy the master boot record as well?

If the master boot record is corrupted, you can tell fdisk to replace it by using the mbr switch.

Example:
a:\fdisk.exe /mbr
"WELDING! Oooo pretty light... AHHH! It burns!"
"Keep that up you'll go blind."
User avatar
Beefy_Suavo
 
Joined: 26 Feb 2005
Location: Denver, CO
Status: Dead and loving it

Postby Akashio » Thu Aug 04, 2005 11:08 pm

I just did that and it still tells me I'm missing the NTLDR file... even tho I've copied it from an XP disk to both C: and C:\WINDOWS\ using the recovery console

BTW, my SATA controller is built in on an A8N-SLI Deluxe sporting an Athlon 64 3500+
User avatar
Akashio
 
Joined: 25 Nov 2001

Postby bum » Fri Aug 05, 2005 8:06 am

If your puting an os onto a hard disk, simply moving it across is bound to get you in alot of trouble. Best to just do a fresh install (and make sure to allways do a full format instead of a quick format).
User avatar
bum
17747114553
 
Joined: 08 Nov 2003

Postby Zero1 » Fri Aug 05, 2005 3:59 pm

Did you remember to change the HD boot priority in the BIOS? :roll:
User avatar
Zero1
 
Joined: 02 Jan 2004
Location: Sheffield, United Kingdom

Postby V13tB0i » Fri Aug 05, 2005 5:16 pm

Umm.... check the jump packs. If that 250 GB hard drive is a secondary, make sure the jumper socket is in the second. If your 250 GB hard drive is a primary, put it in the first socket.
V13tB0i
 
Joined: 19 Feb 2005
Location: CA - San Jose

Postby jbone » Fri Aug 05, 2005 6:17 pm

Short answer: You are fucked.

Windows NT is very picky about where it is installed. You can not "move" the partition to a new drive of a different type on a different controller/channel, because it will always think it is on its original partition/drive. Thus, if you try to move it in the way you did, it will choke and die.

You can try booting off your Windows CD and going through the full "repair" routine, but it might not actually fix what's wrong. You may need to reinstall Windows.

Good news is that, as long as you don't reformat the drive (just install Windows onto the old partition), you shouldn't lose any information. You'll just need to reinstall all your programs.
"If someone feels the need to 'express' himself or herself with a huge graphical 'singature' that has nothing to do with anything, that person should reevaluate his or her reasons for needing said form of expression, possibly with the help of a licensed mental health practitioner."
User avatar
jbone
 
Joined: 12 Jan 2002
Location: DC, USA
Status: Single. (Lllladies.)

Postby Akashio » Fri Aug 05, 2005 8:35 pm

ok, I'm sadly game for installing a fresh XP OS, but like I said earlier, my XP CD says that every partition I have is "not Windows XP-compatible"

What can I do? Can I format a partition with fdisk? will that work?
User avatar
Akashio
 
Joined: 25 Nov 2001

Postby Beefy_Suavo » Fri Aug 05, 2005 8:59 pm

jbone wrote:Windows NT is very picky about where it is installed. You can not "move" the partition to a new drive of a different type on a different controller/channel, because it will always think it is on its original partition/drive.

True, this has to do with the boot.ini file. It is still telling Windows XP to look for the operating system files on your old hard drive controller.

Akashio wrote:ok, I'm sadly game for installing a fresh XP OS, but like I said earlier, my XP CD says that every partition I have is "not Windows XP-compatible"

What can I do? Can I format a partition with fdisk? will that work?

When you boot with the XP CD, and it shows you the partitions, does it give you the option to delete the partition? Sadly that will delete all your data. Can you put the old drive back in, reinstall Windows on it, and use it to copy the files you want saved off the SATA drive?

Also when you first boot off the Windows XP CD, it says "Press F6 to install a 3rd party RAID or SCSI driver." Try using that to install the drivers for the SATA controller to see if Windows setup will then recognize the partitions on the SATA drive.
"WELDING! Oooo pretty light... AHHH! It burns!"
"Keep that up you'll go blind."
User avatar
Beefy_Suavo
 
Joined: 26 Feb 2005
Location: Denver, CO
Status: Dead and loving it

Postby Akashio » Sun Aug 07, 2005 10:02 pm

Hmmm ok

1. I did delete a partition and asked windows to install on it also. It still says it is not XP-compatible. Could this be because I am using a packaged DELL cd of XP and do not have a Dell mobo? (I only have an XP upgrade CD, so I'm using the full Dell version.)

2. I tried the F6 SCSI/RAID drivers thing and it refuses to recognize that I am pressing F6. It has no problem recognizing F2 for automated repair blah (sadly I never made a floppy for automated repair).

3. Is there any way to edit the boot.ini in the recovery console? Everytime I type, "C:\Windows\>edit boot.ini", it says it cannot recognize that command.

I AM SO TIRED OF BORROWING SOMEONE'S COMPUTER TO MAKE DISTRESS CALLS TO THE HELPFUL PEOPLE HERE. But I love the helpful people. I really appreciate you guys' continued help.
User avatar
Akashio
 
Joined: 25 Nov 2001

Postby Beefy_Suavo » Sun Aug 07, 2005 10:45 pm

It looks like getting Windows setup to find the driver for the SATA controller is what needs to be done before it can recognize any vaild partitions or talk with the drive correctly.

Akashio wrote:2. I tried the F6 SCSI/RAID drivers thing and it refuses to recognize that I am pressing F6. It has no problem recognizing F2 for automated repair blah (sadly I never made a floppy for automated repair).
When you press F6, the setup program will continue to load, but eventually take you to a screen that says:
"Setup could not determine the type of one or more mass storage devices installed in your system, or you have chosen to manually specify a driver."
It should then let you load a driver for the SATA controller off a floppy disk.

Akashio wrote:3. Is there any way to edit the boot.ini in the recovery console? Everytime I type, "C:\Windows\>edit boot.ini", it says it cannot recognize that command.
The recovery console does not come with a text editor. You have to make a boot.ini file on another computer, save it to a floppy disk, and use the recovery console to copy it to the hard drive.
A sample boot.ini file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Microsoft Windows XP Professional" /fastdetect


multi() is the drive controller. The first valid number is 0.
disk() is always 0
rdisk() is the physical hard disk attached to drive controller in multi(). The first valid number is 0.
partition() is the partition number on the physical disk specified by rdisk(). The first valid number is 1.

You can try to have the recovery console repair the boot.ini file by using the bootcfg /rebuild command. If that doesn't work you can view the existing hard drive information by using the map command in the recovery console. You use the information from the map command to create and edit a new boot.ini file using another computer and copy it over.
I would try increasing the number in multi() one by one and see what happens.

More information on the boot.ini file can be found here.
"WELDING! Oooo pretty light... AHHH! It burns!"
"Keep that up you'll go blind."
User avatar
Beefy_Suavo
 
Joined: 26 Feb 2005
Location: Denver, CO
Status: Dead and loving it


Return to Video Hardware Discussion

Who is online

Users browsing this forum: No registered users and 0 guests