B
Bob Horton
Hi,
I apologize in advance for the cross-post as well as the length of the post;
I have previously posted this in an ASUS group and have contacted the
various suppliers involved, but I screwed around with this issue for better
part of a day with no luck and no one on the ASUS group had any ideas and I
have gotten no useful feedback from the manufacturers. so I thought I'd ask
the knowledgeable folks at these two places.
First the basics: I have the following system specs: an ASUS A8N32-SLI
Deluxe mobo, 2 GB RAM, AMD Athlon 64x2 4800+ processor, two 400 GB Western
Digital SATA drives running in spanning/JBOD mode (XP is installed here; the
"spanned" disk is the boot drive), with a legacy 120 GB Western Digital IDE
133 drive that I "brought over" when the machine was built -- it was in
place when the OS was installed. OS is XP Pro SP2, all service packs
installed. I built the machine a couple of weeks ago and all has been well.
The only issue I've had is doing backups over our Gigabit (wired) LAN to a
networked drive. I eventually decided that the network backup was just not
going to be reliable at this point (too many "delayed write failures" and
not enough time to try to figure out what was causing them, but have
narrowed it down I believe to one problem machine -- but I digress; sorry)
and decided to install another internal drive for nothing but backups. I
had a brand new 250 GB Maxtor IDE 133, so I decided to use it. To hopefully
avoid any Windows issues, I decided to put the drive on the secondary IDE
controller (this controller had nothing on it but an HP DVD burner; the 120
GB WD was on the primary IDE -- it was the only device on the primary
controller). Long, long, long, long story short, no matter how or where I
installed the 250 GB Maxtor, XP refused to boot, returning a black
"DOS-type" screen with a hardware configuration error message. I went
through every combination of jumpers on both the DVD burner and the 250 GB
drive, with the "best" result being the machine just sitting there with a
blinking cursor. The POST check was fine (1 beep). After exhausting all
the permutations/combinations of jumpers/cable connections as well as
swapping out the IDE cable, I decided to move the 250 GB drive to the
primary IDE controller and see what happened. I got the same results, again
no matter what jumper settings I used or which drive was plugged into the
master or slave ends of the cable. I finally broke down and used a WD SATA
drive that was going to go into another new machine and installed in on SATA
3. I got it set up properly in the NVIDIA RAID utility, Windows booted up
fine and the SATA drive is now my "backup drive". I should note that, at
any time during this process, I could remove the 250 GB IDE drive from the
system and it would boot up normally. I also scoured the BIOS looking for
something that I might have missed. I changed boot orders and something
that IIRC was called drive priorities or something to that effect. Nothing
mattered. All the devices were detected in the BIOS properly and it didn't
matter whether the JBOD array was first, last, or even in the boot device
list (it actually didn't seem to matter what was in the boot device list or
what order things were in).
One other thing that has me wondering if this has something to do with XP
and SATA boot drives: I have another machine (XP Pro SP2) that boots from a
WD 120 GB SATA drive. If I have an external USB2 hard drive plugged in when
that machine is re-booted, it will refuse to boot (displaying a DOS-type
black screen with a message about incorrect hardware configuration) until
the external drive is unplugged. XP was obviously installed on that machine
without the external drive being attached.
Anyway, the system works fine now, but not as I had desired. I guess I'll
build the
next system with the IDE drive, but I'd rather have it for data storage than
being my boot drive. I seem to recall having an issue with a Windows XP box
behaving something like this before, but I can't for the life of me remember
what I did to correct it. FWIW, I added additional storage drives to 3
other machines today with no problems at all (for the same network backup
issue), but none of those machines had SATA drives in them.
Sorry for the long post. Thanks in advance for any ideas or suggestions.
I apologize in advance for the cross-post as well as the length of the post;
I have previously posted this in an ASUS group and have contacted the
various suppliers involved, but I screwed around with this issue for better
part of a day with no luck and no one on the ASUS group had any ideas and I
have gotten no useful feedback from the manufacturers. so I thought I'd ask
the knowledgeable folks at these two places.
First the basics: I have the following system specs: an ASUS A8N32-SLI
Deluxe mobo, 2 GB RAM, AMD Athlon 64x2 4800+ processor, two 400 GB Western
Digital SATA drives running in spanning/JBOD mode (XP is installed here; the
"spanned" disk is the boot drive), with a legacy 120 GB Western Digital IDE
133 drive that I "brought over" when the machine was built -- it was in
place when the OS was installed. OS is XP Pro SP2, all service packs
installed. I built the machine a couple of weeks ago and all has been well.
The only issue I've had is doing backups over our Gigabit (wired) LAN to a
networked drive. I eventually decided that the network backup was just not
going to be reliable at this point (too many "delayed write failures" and
not enough time to try to figure out what was causing them, but have
narrowed it down I believe to one problem machine -- but I digress; sorry)
and decided to install another internal drive for nothing but backups. I
had a brand new 250 GB Maxtor IDE 133, so I decided to use it. To hopefully
avoid any Windows issues, I decided to put the drive on the secondary IDE
controller (this controller had nothing on it but an HP DVD burner; the 120
GB WD was on the primary IDE -- it was the only device on the primary
controller). Long, long, long, long story short, no matter how or where I
installed the 250 GB Maxtor, XP refused to boot, returning a black
"DOS-type" screen with a hardware configuration error message. I went
through every combination of jumpers on both the DVD burner and the 250 GB
drive, with the "best" result being the machine just sitting there with a
blinking cursor. The POST check was fine (1 beep). After exhausting all
the permutations/combinations of jumpers/cable connections as well as
swapping out the IDE cable, I decided to move the 250 GB drive to the
primary IDE controller and see what happened. I got the same results, again
no matter what jumper settings I used or which drive was plugged into the
master or slave ends of the cable. I finally broke down and used a WD SATA
drive that was going to go into another new machine and installed in on SATA
3. I got it set up properly in the NVIDIA RAID utility, Windows booted up
fine and the SATA drive is now my "backup drive". I should note that, at
any time during this process, I could remove the 250 GB IDE drive from the
system and it would boot up normally. I also scoured the BIOS looking for
something that I might have missed. I changed boot orders and something
that IIRC was called drive priorities or something to that effect. Nothing
mattered. All the devices were detected in the BIOS properly and it didn't
matter whether the JBOD array was first, last, or even in the boot device
list (it actually didn't seem to matter what was in the boot device list or
what order things were in).
One other thing that has me wondering if this has something to do with XP
and SATA boot drives: I have another machine (XP Pro SP2) that boots from a
WD 120 GB SATA drive. If I have an external USB2 hard drive plugged in when
that machine is re-booted, it will refuse to boot (displaying a DOS-type
black screen with a message about incorrect hardware configuration) until
the external drive is unplugged. XP was obviously installed on that machine
without the external drive being attached.
Anyway, the system works fine now, but not as I had desired. I guess I'll
build the
next system with the IDE drive, but I'd rather have it for data storage than
being my boot drive. I seem to recall having an issue with a Windows XP box
behaving something like this before, but I can't for the life of me remember
what I did to correct it. FWIW, I added additional storage drives to 3
other machines today with no problems at all (for the same network backup
issue), but none of those machines had SATA drives in them.
Sorry for the long post. Thanks in advance for any ideas or suggestions.