• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 743
  • Last Modified:

Cannot boot from 160 GB Hard Drive

Hi

I have a new Western Digital 160 GB hard disk with XP Pro SP2 installed. When this is set as the slave drive to a 15 GB Seagate hd (also XP Pro but no SP as there is not enough space left), the system boots and Windows correctly reports the size of the WD disk. When I disconnect the Seagate and set the WD as master however, I get a BSOD with a 0000 007B error (F8A5 9640,  0000 0034, 0000 0000, 0000 0000). I've checked the MSKB articles on the 0000 007B error and also articles on the 137 GB limit for hard disks but I'm not sure these apply as my disk is recognised so long as its not the master.

I've updated the bios and it seems to recognise the disk as the Max LBA Capacity is 160 041 MB. I've also ran WD's Data Lifeguard tests and it reports the disk as ok. The last step would be to partition and format using Data Lifeguard but I'm hanging off in case I'm missing something. The mobo is an Asus CUV4X with a Via 82C605 chipset and the processor is a Pentium 3 667. Can anyone help?

Cheers
0
ShredderB
Asked:
ShredderB
  • 7
  • 5
  • 4
  • +3
1 Solution
 
burrcmCommented:
The error is inaccessible boot device. First check that the drives are all set to auto on the first page - if it is looking for the 15GB drive, it will definitely fall over.

Chris B
0
 
burrcmCommented:
If it has an auto detect HDD page, use that.

Chris B
0
 
ShredderBAuthor Commented:
All the drives are set to auto...
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
burrcmCommented:
Did you install XP clean on this drive or clone the 15? If cloned, how?

Chris B
0
 
ShredderBAuthor Commented:
Clean install of XP
0
 
ridCommented:
Did you format the HD and install XP on this drive in this particular computer? Did it ever work?

If you need to format and reinstall, use the XP tools. They work just as well as third-party tools for any normal situation.
/RID
0
 
burrcmCommented:
Can't find any definitive comment on the matter, but I would suspect the 137 limit. Try partitioning it as 2 x 80 and install on the first partition.

Chris B
0
 
ridCommented:
Isn't the 137 GB limit a BIOS thing? Partitioning won't work properly if BIOS doesn't handle the drive OK, I fear.
/RID
0
 
ShredderBAuthor Commented:
I suspect that I formatted and installed XP on another computer. As I said, the bios does seem to recognise the full 160 GB.
0
 
ridCommented:
Then I think that your problem lies there. Moving the O/S between machines is not a very good idea with XP. I suggest you use the XP install CD and re-partition, format and do a clean install on the 160 GB hard drive, if it can be correctly handled by computer BIOS. Also verify jumper settings (the drive should be master).
/RID
0
 
burrcmCommented:
I thought the 137 was XP - no patch 137, SP1 160, SP2 whatever, but you may be right. However, the first 80 should be OK in any event. All that is irrelevant if the OS was installed on a different PC as you correctly point out. Start again ShredderB and let us know what happens.

Chris B
0
 
ridCommented:
Seems to be alittle of both, actually! There are a few threads here about this. Yes, you need XP SP1, AND you need a modern BIOS or ATA controller.
Cheers
/RID
0
 
ShredderBAuthor Commented:
Ok I'll start again and let you know what happens. Thanks
0
 
radnorCommented:
I saw where he was boting from a 15G seagate and it saw the 160G fine.  Moved the 160G to primary drive now no boot...  Do you have to mark a partition as ACTIVE with XP?  Did not see this in any post above.
0
 
garycaseCommented:
Since there's a bit of "misinformation" here on the 137GB limit I feel compelled to toss in a few comments:

The 137GB limit has NO bearing on this problem.   The BIOS recognizes the correct size (so it's 48-bit LBA compliant); and the OS is XP SP2, which has full 48-bit LBA support.   And if you have a drive that exceeds the 28-bit LBA limit and don't have 48-bit support, partitioning the drive will NOT help -- you still can't address the areas above 137GB.

As rid correctly noted, the issue here is simple:  "... I formatted and installed XP on another computer."  ==>  Different chipset; different hardware; possibly even different CPU !!    All you have to do is install the 160GB drive;  THEN install XP; and all will be well :-)    Note that you DO have to install from a SP1 or SP2 CD -- otherwise it will not correctly recognize the drive (since there's no 48-bit LBA support on an original XP install CD).   Alternatively, you could free up some space on your 15GB drive (partition your new drive into 2 partitions;  copy some stuff to the 2nd partition from your original drive, then delete it from that drive); install SP2; and then image the 15GB drive to the 2nd partition on the new drive -- and then simply "restore" that image to the 1st partition of the new drive.   Then the 160GB drive will boot fine -- without having to do any reinstallations of your programs, etc.
0
 
FriarTukCommented:
since your pc recognized the 160gb wd while it was attached to your 15gb sea, then there isn't anything wrong with your drive.  the problem is that when you installed xp with the 15gb as master, xp installed the boot files there, although you actually installed the o/s on the 160gb slave.

to boot from the 160gb you must keep it as the master once you change it, otherwise you'll end up losing the boot area again

boot using your xp cd, & select (R)epair to enter the recovery console, then see method #2
     http://support.microsoft.com/?kbid=315341
for more info on the recovery console go here
     http://support.microsoft.com/kb/314058/en-us

i recommend doing the "bootcfg /rebuild", then "fixboot c:" commands
0
 
ShredderBAuthor Commented:
Thanks to everyone for your comments. I've reinstalled XP on the 160 GB drive and evrything is fine. Friar Tuk, I have booted the system with the original 15 GB drive as master, then slave, then master again so unless I have misunderstood your comment, this doesn't seem to affect bootability.

Cheers
0
 
FriarTukCommented:
no, what i meant was that if you remove the 15gb & make the 160gb the master, then you must rebuild the boot partition

when you installed xp it installed the boot partition on the 15gb but the os files on the 160gb

repairing would work, but then so would reinstalling xp as that will repartition the drive & reinitialize the boot track
0
 
ShredderBAuthor Commented:
I'm not quite sure what you mean when you say the boot partition was installed to the 15 GB drive and the os files to the 160 GB drive. XP was installed separately to each drive on different machines.
0
 
FriarTukCommented:
ok better clarifying, so you had two separate xp hard disks, which you were trying to put on the same machine

even so, if you booted into the recovery console & ran bootcfg /list (list all os drive) or bootcfg /scan (scans for all boot partitions) or bootcfg /rebuild (add all o/s boot partitions) it would have rebuilt your drives to work together, but as i also stated reinstalling would do the same thing.

as long as you're up & running, have a good one
0
 
ShredderBAuthor Commented:
Thanks FriarTuk, thats useful to know.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 7
  • 5
  • 4
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now