Bios AND system NOT seeing hard drive

NJG252 · 01-27-2008, 07:02 PM

Hi,
Machine is a Compaq EVO d510 CMT. XP Pro SP2, 220W PS, factory equip. no souped up video or such. Maxtor 6E040LO 40GB, just tried to add (in order to clone and make into new boot hard drive, removing the 40gig entirely) a Maxtor 6Y120LO 120GB.
This all went well a week ago, got the 40 cloned onto the 120 - tested for several hours, several diagnostic, defrag, etc. Had gotten to a completely stable state, removed the original drive(40GB) and sent the unit home to it's owners.
They downloaded music for a couple days, no complaints.

Then, on the fifth day, when they hit the Power button, they got this:
Intel Boot Client v ???
(more wording)
Client MAC address numbers and alpha, GUID numbers and alpha and then
DCHP....._ (with a twisting/moving slash above the underline)

the dots will go as far as 6 of them, and then I just got tired of waiting for it to do something. But he stood here while it showed me the dos error.

HELP ?
I was 'told' that music downloading was all they did. No new programs, no new cleaning ,no power outs, it had shut down from the ordinary place when they had shut it off the night before., etc.

I've already tried to adjust jumpers....same or slightly diff. boot error on dos screen
Checked all the cables, did the un/re plug from connectors. All are secure.

I grabbed a copy of SeaTools (seagate/maxtor's new parent), it didn't even SEE the drive.
Tried MaxBlast 5 = same, not seeing hd.

I can still put his original 40GB back in, and the whole shebang works fine.
And this is the second time I am handling this new 120GB drive. Wondering if it is faulty, and just needed used a minute to produce it's death.

I've done installs before.
I do not have her recovery media, since they got her machine from Walmart, and rec'd. no disks WITH it. So working with the 40GB - to keep her at XP Pro, I had planned to Clone.
While waiting for reply, I'm going to get it back to the 'working 40GB" layout, ; (also run a full backup of their data ) and let them use their machine til I get further research done.
hang onto this 120Maxtor for further checking ( I have other test capable machines ), and
keep researching Maxtor, Compaq and such for clues, ideas, etc.

I can work with them on this, Get the machine back once I know how to adjust this 120GB; outweighs continuing this unless it's just a stupid thing I did not check, and someone tells me a place to check or change.Thanks in advance.
Nanci

lensman3 · 01-27-2008, 07:39 PM

Is the disk a Sata I or a Sata II drive by default. You will have to jumper the driver to a slower speed for the MB to see the fast disk. Old MB's can't handle to "newer" Sata II drives.

Because your MB.bios is not seeing the drive it defaults to booting of a network (thats the MAC address boot stuff).

There should be a jumper on the drive to slow it down. It usually is next to the power plugin. Usually the fine print on the label of the drive will tell you which jumper to close.

Good luck. (This is the voice of experience, I had this happen to me with a new drive)

NJG252 · 01-27-2008, 09:33 PM

Hello and Thank you for rapid (really rapid) reply !!
I'm gonna be up all night on this.

All the drives are ATA - but the smaller one is Parallel ATA and the large is simple ATA.
Maxtor 6E040L0 and a Maxtor 6Y120L0 are the ID's of the drives I'm dealing with. If that helps you piece it all together (reference & research).
No SATA's on this machine. No RAID.
UltraATA100 cables, do factor here. I had to check that, and in all the seagate.com stuff it says it made a slight difference.
UDMA enabled, as matter of fact, I found it orig. set at MAX UDMA in bios.

Because your MB.bios is not seeing the drive it defaults to booting of a network (thats the MAC address boot stuff).
Ok....further detail. Please. Far as I know, she has a home router box and this is the only computer. I have a network, but not the type the banks, hospitals use for their network - server + lots of network computers. I have two wired stations with their independent systems, and two wireless the kids' use up on the second floor. I can boot all or one from my machine which is the network hub.....but it took me a long time to get that all set up. It wasn't pretty at times. lol
That error did surprise me. I hadn't even touched anything that would indicate network boot. it had gone smoothly last week, recognized, ran, booted, took the clone of the 40 & booted, all that. Until third day they had it at their house.

The other curious thing, Compaq has seven Bios flashes available, I found the system ROM setting, and when I asked live chat about a recommendation - they blanked. I so think it's partly a bios problem. Nice that live chat is so well trained, huh?

Also, please explain further, if poss. how slowing it down is going to get me headed in the right direction for install, in the end.?
Jumper settings are clearly diagramed on back of each. I've tried almost all of them !!!

Hope you're still nearby. Will peek again at email before I lay this tired body down !!
Nan

lensman3 · 01-27-2008, 11:06 PM

I think the HD died. It was working before and now it doesn't and nothing was done to change it. Since you cloned the 120 from the 40, then everything was communicating OK. You did everything right and a few days later it quits. Infantile suicide. If something is going to quit it will happen in the first month.
The boot from the network happens because the 120 was not found so the bios tries to find the operating system out on the network. It didn't so it quits after a while. Booting from the network is different that getting the IP address from the DHCP server on your router.

Take the 120 out of the computer and put it in another and see if it boots. If it does it will probably boot and then give the "blue screen of death" at some point because it was setup for the Compac EVO and it is a good disk. If it doesn't boot something is probably wrong with the disk.

NJG252 · 01-28-2008, 12:23 AM

Gotcha on that one. I planned to send the thing back to them tomorrow. But set up with the original 40GB that has been holding all his music in the first place. I'll buckle the WD 40GB that always paired with it as slave, and they can get their dang Valentine party music 'ready' (there's some kinda 'deadline' for having the unit working again soon)......WHILE I do the deep investigations on this 120GB .......or trade it in for a new one. (got a repair shop nearby that allows for that.....so cool ).
I plan to use MaxBlast5, and /or Ghost 10 (depending on the IRS & $$) my one trial beta ran out last month !! Either way, I've grabbed a whole ton More info about cloning, and handling issues w/Maxtor (normally my fav. hd's).
The mobo and such are just fine (as of an hour ago) running with the old hard drive config. - so basic bios settings ARE in fact functioning on/in the EVO.
I have a dell prec.workstation I modified to be my 'work horse' - THAT is where I will discover the 120's issues ( 'other' machine to test in ) - and yeppers, very familiar that some of the prep and install stuff for the 120 will HAVE to be done IN the EVO to work in the EVO. Been there myself, before.

You appear to be from out west, but here it's middle of the night. I will post tomorrow afternoon, once I get a few more 'things' tried....and their base config fixed to go home and work a couple days.
Still gonna kill somethin' to figure this bad boy out !! LOL
Nan

NJG252 · 01-31-2008, 09:00 PM

Ok.
So far, (that is, if you are still following this thread);
tried it at all different jumper settings and best I can get to is a DOS prompt, but I can't even get the bad boy to chkdsk.

Used both seagate/maxtor utilities to see if I could roll some response.
I ordered a new drive, got them set up with a temp. config. using their old/orig. drive. Getting machine back Fri. night to re-do the set up, but

Here's my new question .....
Ya think maybe it could be a stronger power supply need ? Larger drive,
larger need ?
I have a 300W sitting here . It's perfect condition. The Compaq is currently rolling a 220W (factory). But, I found out that the kid was running the CD ROM and the CD RW at the same time as downloading from Limewire !! That sorta sounds like to me, that with that much demand.....(and he will again !!)....and if I can get this running by Sat......I can try running all the drives in a similar way and make dang sure it's meeting demand, and boots on Sunday ?

Thoughts ?
Thanks,
Nan

lensman3 · 01-31-2008, 10:04 PM

Yeah. A marginal power supply won't spin the disk up. As a test unhook your old hard drive and just hook up the new and boot up. Go to the bios and see if it can see the new disk. It won't boot but you should get a message like "insert boot disk".

I have 4 disks and a cdrom in my PC. Three of the disks are hot-swap SATA's. Before I upgraded my power supply, last disk would try to get up to speed, but my Linux system get a "disk not ready error". I would pull one of the other disks out, and the disk would get up to speed and mount.

But first unhook your old disk, both the data cable and power cable. Add the new disk and see if the bios can see it.

01-27-2008, 07:02 PM	#1 (permalink)
NJG252 Registered User Join Date: Jan 2008 Posts: 5 OS: XP Pro SP2	Bios AND system NOT seeing hard drive Hi, Machine is a Compaq EVO d510 CMT. XP Pro SP2, 220W PS, factory equip. no souped up video or such. Maxtor 6E040LO 40GB, just tried to add (in order to clone and make into new boot hard drive, removing the 40gig entirely) a Maxtor 6Y120LO 120GB. This all went well a week ago, got the 40 cloned onto the 120 - tested for several hours, several diagnostic, defrag, etc. Had gotten to a completely stable state, removed the original drive(40GB) and sent the unit home to it's owners. They downloaded music for a couple days, no complaints. Then, on the fifth day, when they hit the Power button, they got this: Intel Boot Client v ??? (more wording) Client MAC address numbers and alpha, GUID numbers and alpha and then DCHP....._ (with a twisting/moving slash above the underline) the dots will go as far as 6 of them, and then I just got tired of waiting for it to do something. But he stood here while it showed me the dos error. HELP ? I was 'told' that music downloading was all they did. No new programs, no new cleaning ,no power outs, it had shut down from the ordinary place when they had shut it off the night before., etc. I've already tried to adjust jumpers....same or slightly diff. boot error on dos screen Checked all the cables, did the un/re plug from connectors. All are secure. I grabbed a copy of SeaTools (seagate/maxtor's new parent), it didn't even SEE the drive. Tried MaxBlast 5 = same, not seeing hd. I can still put his original 40GB back in, and the whole shebang works fine. And this is the second time I am handling this new 120GB drive. Wondering if it is faulty, and just needed used a minute to produce it's death. I've done installs before. I do not have her recovery media, since they got her machine from Walmart, and rec'd. no disks WITH it. So working with the 40GB - to keep her at XP Pro, I had planned to Clone. While waiting for reply, I'm going to get it back to the 'working 40GB" layout, ; (also run a full backup of their data ) and let them use their machine til I get further research done. hang onto this 120Maxtor for further checking ( I have other test capable machines ), and keep researching Maxtor, Compaq and such for clues, ideas, etc. I can work with them on this, Get the machine back once I know how to adjust this 120GB; outweighs continuing this unless it's just a stupid thing I did not check, and someone tells me a place to check or change.Thanks in advance. Nanci Last edited by NJG252; 01-27-2008 at 07:29 PM. Reason: add'l info

01-27-2008, 07:39 PM	#2 (permalink)
lensman3 Registered User Join Date: Oct 2007 Location: Littleton, Colorado USA Posts: 470 OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix	Re: Bios AND system NOT seeing hard drive Is the disk a Sata I or a Sata II drive by default. You will have to jumper the driver to a slower speed for the MB to see the fast disk. Old MB's can't handle to "newer" Sata II drives. Because your MB.bios is not seeing the drive it defaults to booting of a network (thats the MAC address boot stuff). There should be a jumper on the drive to slow it down. It usually is next to the power plugin. Usually the fine print on the label of the drive will tell you which jumper to close. Good luck. (This is the voice of experience, I had this happen to me with a new drive)

01-27-2008, 09:33 PM	#3 (permalink)
NJG252 Registered User Join Date: Jan 2008 Posts: 5 OS: XP Pro SP2	Re: Bios AND system NOT seeing hard drive Hello and Thank you for rapid (really rapid) reply !! I'm gonna be up all night on this. All the drives are ATA - but the smaller one is Parallel ATA and the large is simple ATA. Maxtor 6E040L0 and a Maxtor 6Y120L0 are the ID's of the drives I'm dealing with. If that helps you piece it all together (reference & research). No SATA's on this machine. No RAID. UltraATA100 cables, do factor here. I had to check that, and in all the seagate.com stuff it says it made a slight difference. UDMA enabled, as matter of fact, I found it orig. set at MAX UDMA in bios. Because your MB.bios is not seeing the drive it defaults to booting of a network (thats the MAC address boot stuff). Ok....further detail. Please. Far as I know, she has a home router box and this is the only computer. I have a network, but not the type the banks, hospitals use for their network - server + lots of network computers. I have two wired stations with their independent systems, and two wireless the kids' use up on the second floor. I can boot all or one from my machine which is the network hub.....but it took me a long time to get that all set up. It wasn't pretty at times. lol That error did surprise me. I hadn't even touched anything that would indicate network boot. it had gone smoothly last week, recognized, ran, booted, took the *clone* of the 40 & booted, all that. Until third day they had it at their house. The other curious thing, Compaq has seven Bios flashes available, I found the system ROM setting, and when I asked live chat about a recommendation - they blanked. I so think it's partly a bios problem. Nice that live chat is so well trained, huh? Also, please explain further, if poss. how slowing it down is going to get me headed in the right direction for install, in the end.? Jumper settings are clearly diagramed on back of each. I've tried almost all of them !!! Hope you're still nearby. Will peek again at email before I lay this tired body down !! Nan

01-27-2008, 11:06 PM	#4 (permalink)
lensman3 Registered User Join Date: Oct 2007 Location: Littleton, Colorado USA Posts: 470 OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix	Re: Bios AND system NOT seeing hard drive I think the HD died. It was working before and now it doesn't and nothing was done to change it. Since you cloned the 120 from the 40, then everything was communicating OK. You did everything right and a few days later it quits. Infantile suicide. If something is going to quit it will happen in the first month. The boot from the network happens because the 120 was not found so the bios tries to find the operating system out on the network. It didn't so it quits after a while. Booting from the network is different that getting the IP address from the DHCP server on your router. Take the 120 out of the computer and put it in another and see if it boots. If it does it will probably boot and then give the "blue screen of death" at some point because it was setup for the Compac EVO and it is a good disk. If it doesn't boot something is probably wrong with the disk.

01-28-2008, 12:23 AM	#5 (permalink)
NJG252 Registered User Join Date: Jan 2008 Posts: 5 OS: XP Pro SP2	Re: Bios AND system NOT seeing hard drive *Gotcha* on that one. I planned to send the thing back to them tomorrow. But set up with the original 40GB that has been holding all his music in the first place. I'll buckle the WD 40GB that always paired with it as slave, and they can get their dang Valentine party music 'ready' (there's some kinda 'deadline' for having the unit working again soon)......WHILE I do the deep investigations on this 120GB .......or trade it in for a new one. (got a repair shop nearby that allows for that.....so cool ). I plan to use MaxBlast5, and /or Ghost 10 (depending on the IRS & $$) my one trial beta ran out last month !! Either way, I've grabbed a whole ton More info about cloning, and handling issues w/Maxtor (normally my fav. hd's). The mobo and such are just fine (as of an hour ago) running with the old hard drive config. - so basic *bios settings ARE* in fact functioning on/in the EVO. I have a dell prec.workstation I modified to be my 'work horse' - THAT is where I will discover the 120's issues ( 'other' machine to test in ) - and yeppers, very familiar that some of the prep and install stuff for the 120 will HAVE to be done IN the EVO to work in the EVO. Been there myself, before. You appear to be from out west, but here it's middle of the night. I will post tomorrow afternoon, once I get a few more 'things' tried....and their base config fixed to go home and work a couple days. Still gonna kill somethin' to figure this bad boy out !! LOL Nan

01-31-2008, 09:00 PM	#6 (permalink)
NJG252 Registered User Join Date: Jan 2008 Posts: 5 OS: XP Pro SP2	Re: Bios AND system NOT seeing hard drive Ok. So far, (that is, if you are still following this thread); tried it at all different jumper settings and best I can get to is a DOS prompt, but I can't even get the bad boy to chkdsk. Used both seagate/maxtor utilities to see if I could roll some response. I ordered a new drive, got them set up with a temp. config. using their old/orig. drive. Getting machine back Fri. night to re-do the set up, but Here's my new question ..... Ya think maybe it could be a stronger power supply need ? Larger drive, larger need ? I have a 300W sitting here . It's perfect condition. The Compaq is currently rolling a 220W (factory). But, I found out that the kid was running the CD ROM and the CD RW at the same time as downloading from Limewire !! That sorta sounds like to me, that with that much demand.....(and he will again !!)....and if I can get this running by Sat......I can try running all the drives in a similar way and make dang sure it's meeting demand, and boots on Sunday ? Thoughts ? Thanks, Nan

01-31-2008, 10:04 PM	#7 (permalink)
lensman3 Registered User Join Date: Oct 2007 Location: Littleton, Colorado USA Posts: 470 OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix	Re: Bios AND system NOT seeing hard drive Yeah. A marginal power supply won't spin the disk up. As a test unhook your old hard drive and just hook up the new and boot up. Go to the bios and see if it can see the new disk. It won't boot but you should get a message like "insert boot disk". I have 4 disks and a cdrom in my PC. Three of the disks are hot-swap SATA's. Before I upgraded my power supply, last disk would try to get up to speed, but my Linux system get a "disk not ready error". I would pull one of the other disks out, and the disk would get up to speed and mount. But first unhook your old disk, both the data cable and power cable. Add the new disk and see if the bios can see it.