p4p800 deluxe losing sata drives

"D" <anon RemoveThis @spoof.com> wrote in message news:kG4Ac.249$Y75.170@newsfe6-win...
 > Download hd manu disk checking utility, for both drives and test
 >
Both drives are now tested and report no errors, any more ideas?
thanks, ezman<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: p4p800 deluxe losing sata drives 

"ezman" <ezm2k3.RemoveThis@mailinator.com> wrote in message
news:pN4Ac.790$A74.605@newsfe1-win...
 >
 > "D" <anon.RemoveThis@spoof.com> wrote in message
news:kG4Ac.249$Y75.170@newsfe6-win...
  > > Download hd manu disk checking utility, for both drives and test
  > >
 > Both drives are now tested and report no errors, any more ideas?
 > thanks, ezman

Check mobo lithium cell (3V minimum) - if not that, it's probably
a mobo hardware fault (I assume you have the latest BIOS?)
Possibly bad power connectors/cables to the SATA drives?
PSU gone bad? Whatever it is, it's common to both drives.
HTH
--
Rob<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: p4p800 deluxe losing sata drives 

 > Check mobo lithium cell (3V minimum) - if not that, it's probably
 > a mobo hardware fault (I assume you have the latest BIOS?)
 > Possibly bad power connectors/cables to the SATA drives?
 > PSU gone bad? Whatever it is, it's common to both drives.
 > HTH
 > --
 > Rob
 >
Thanks will look into those ideas. Any ideas why this could be happening
intermittently then (like once or twice every 20 boots)<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: p4p800 deluxe losing sata drives 

In article <AgnAc.32$D4.9@newsfe6-win>, "ezman" <ezm2k3.TakeThisOut@mailinator.com> wrote:

  > > Check mobo lithium cell (3V minimum) - if not that, it's probably
  > > a mobo hardware fault (I assume you have the latest BIOS?)
  > > Possibly bad power connectors/cables to the SATA drives?
  > > PSU gone bad? Whatever it is, it's common to both drives.
  > > HTH
  > > --
  > > Rob
  > >
 > Thanks will look into those ideas. Any ideas why this could be happening
 > intermittently then (like once or twice every 20 boots)

Try "Quick Boot" [Disable] and "Full Logo" [Disabled].
Perhaps this will allow extra time to elapse, between the
disks spinning up, and the BIOS attempting to access the
disks. With Full Logo disabled, you should be able to see
when the various phases of the BIOS testing are complete.
With Quick Boot disabled, the memory may be tested multiple
times, before the POST continues.

While there is an "IDE Detect Time Out (sec)" field and a
default value of 35 seconds, I don't think this timeout
applies to devices on a separate RAID chip. The RAID BIOS
may have its own, non-programmable delay timer in its code.
That is why I am suggesting the "Quick Boot" [Disabled], as
this compensates for an inability to program the RAID chip
timer.

HTH,
Paul<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: p4p800 deluxe losing sata drives 

----- Original Message -----
 > Try "Quick Boot" [Disable] and "Full Logo" [Disabled].
 > Perhaps this will allow extra time to elapse, between the
 > disks spinning up, and the BIOS attempting to access the
 > disks. With Full Logo disabled, you should be able to see
 > when the various phases of the BIOS testing are complete.
 > With Quick Boot disabled, the memory may be tested multiple
 > times, before the POST continues.
 >
 > While there is an "IDE Detect Time Out (sec)" field and a
 > default value of 35 seconds, I don't think this timeout
 > applies to devices on a separate RAID chip. The RAID BIOS
 > may have its own, non-programmable delay timer in its code.
 > That is why I am suggesting the "Quick Boot" [Disabled], as
 > this compensates for an inability to program the RAID chip
 > timer.
 >
 > HTH,
 > Paul

Thanks Paul, have done that, will see what happens.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: p4p800 deluxe losing sata drives