Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I had been using two PATA HDs. I replaced the smallest/oldest HD with a new SATA Seagate Barracuda. MY mobo (Abit KV7-V) is SATA ready. That leaves me with a PATA Seagate Barracuda, which is the boot disk and a SATA Barracuda that I want to make as the boot disk. I find the new disk in disk manager and format and allocate it. I use Acronis Migrate to fully copy my PATA data (OS and all) to the new SATA. The HD is fully functional and I can read and write to it. I then enter BIOS to set boot sequence and the new HD is not an option for Boot. I go to integrated peripherals in BIOS and enable SATA RAID BIOS, go back to boot sequence in BIOS and there it is. I set the new HD as first Boot and restart. I then get an error during boot that tells me that there are insufficient HDs to set up a RAID. I disable the SATA RAID BIOS, which removes the new HD as an option in boot sequence, reboot and it boots fine, from the old HD. THe new HD is still functional and usable, but I can't boot from it. Any ideas?
Thanks!
How is the SATA drive configured in the BIOS harddrive setup screen? There may be a different option to Enable the SATA to be part of the boot order. Look on the second of third screen fo an option to set SATA as first harddrive.
When you first installed the SATA drive did windows pick it up as new hardware?
Your issue MAY be 48bit LBA compliance. Is the SATA identified by model number and full size in the POST screens? Look at the link below for more on 48bit LBA.
0 
Is the SATA Drive set to IDE Mode ?
Also you may need to undertake a XP Repair Install, because XP does not always recognise SATA Controller Chipsets and therefore additional drivers need to be offered!
0
Response #1: I dont see the SATA HD referenced anywhere in the BIOS. The closest thing is the SATA RAID BIOS option, And i'm not using a RAID. SO I dont see anyway to set new HD first in BOOT except when enabling the RAID BIOS, which then gives me BOOT error saying not enough HDs for RAID. And Windows did not see HD at first. I first had to allocate and Format in MAnager, then it saw it. And no, the SATA HD is not recognized in POST screens.
Response #2: I dont know if SATA is set to IDE. Where would I see that? And because I dont have a valid WinXP install I do not have a WinXP disc with which to perform repair with.
mmmmm frustration
Thanks!
0
If the SATA drive isn't appearing in the BIOS then your computer probably isn't 48bit LBA compliant. WinXP with at least SP1 is 48bit LBA compliant. However, to have a successful installation BOTH need to be 48 bit LBA compliant.
Is your other drive larger than 127GB? Look at the link below for more info.
0
Well I have XP PRO SP2 so my OS should be LBA compliant. I am able to set my old HD to LBA in the BIOS, which I did. And the old HD is 120GB and the new one is 160GB. I'm at work now so when I get home I will look into some of the tools available from 48bitlba.com. I'll let you know.
Thanks!
0
Setting the drive to LBA is confusing. That setting is an old setting. The prior size limit was base on 28bit numbers, which ccomes out to a maximum size of 128GB. When harddrives stared getting larger than that the standard had to be raised to 48bit LBA ( Logical Block Addressing). What that means is this. If your BIOS can't see the entire drive but your OS can you can write to parts of the drive that aren't properly addressed, resulting in data loss. Your drive falls into that area. Normally, at least with an IDE (ATA) drive the BIOS will recognize the drive but at 127GB.
You may not have something set correctly in the BIOS. Windows is configuring your hardware by BIOS default so it is possible for Windows to see the drive even if it is improperly configured.
One common mistake is to NOT connect to the lowest number SATA port. Also, check to see that the SATA controllers are Enabled in the BIOS.
0
If the only way you can get the drive to show up in the boot order is to enable SATA RAID, you can use that setting. You don't have to actually set up a RAID array and you can't anyway if only one SATA drive is connected.
"I then get an error during boot that tells me that there are insufficient HDs to set up a RAID."
The bios has a built in RAID setup utility - it loads every time you boot, either whether you have a SATA drive installed or not, or maybe only if you have a SATA drive installed, if the onboard IDE doesn't support RAID. If you have only one SATA drive, or if you have more than one SATA drive but have not set up an array and or don't want to, the utility will abort loading or time out when you don't press a key or respond, every time you boot - that is normal and is nothing to worry about.As far as the mode the SATA drive runs in, or if the bios sees the drive but Windows Setup doesn't see the drive, see response 2 in this:
http://www.computing.net/hardware/w...
The actual labels for the SATA modes in your bios vary and may be different. When you have SATA RAID, you may not have a SATA mode to select, and if you need to install drivers in Windows Setup you may have no choice but to install RAID chipset drivers - that's okay - the RAID drivers include support for non-RAID use.If you set the bios to SATA RAID, are able to place the drive first in the boot order, but it will not boot, you can correct that by running an XP Repair Setup and installing the drivers for the SATA controllers at the beginning of Setup as explained at the above link.
An XP Repair Setup will not delete or harm your existing Windows installation. (Although, if you want XP to see itself as on C and there are other Windows installations on the computer on other drives, disconnect the other drives that have a Windows installation while running this.)
You will need a Windows CD of the same version as the one of your Windows installation, and the Product Key, preferably the one that was used to install it, but it can be one for the same version as the one of your Windows installation.How to do an XP Repair Setup, step by step:
http://www.windowsreinstall.com/win...If your Windows CD did not have SP1 or SP2 updates included, and you updated to SP1 or SP2, you may have to install that again to get SP1 or SP2 working properly again. SP1 or later is required for USB 2.0 and hard drives larger than 137gb (manufacturer's size; 128gb in Windows and most bioses).
If your XP CD does not have at least SP1 updates included, and you have hard drives larger than 128gb (in Windows; = 137gb manufacturer's size), you need to burn a slipstreamed CD that has the contents of both the original Windows CD and the SP1 or SP2 updates - e.g.
Slipstreamed Windows XP CD Using SP2
http://www.theeldergeek.com/slipstr...
0
One other thing I should have mentioned in response #6 and Walter touched on also, is that when you connected the drive originally, Windows should have identified it as new hardware and asked for the driver disk. That would be the MBoard CD. If that didn't happen you don't have any SATA drivers installed in WinXP.
That should have NO effect on wheather the drive is seen by the BIOS. That is a separate issue that tubes addressed above.
0
chuckiles
"...when you connected the drive originally, Windows should have identified it as new hardware and asked for the driver disk. That would be the MBoard CD. If that didn't happen you don't have any SATA drivers installed in WinXP."
That is why this would be the case:
"If you set the bios to SATA RAID, are able to place the drive first in the boot order, but it will not boot......"
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
