Booting P4P800 takes ages..

  • Thread starter Thread starter Toneburst
  • Start date Start date
T

Toneburst

Hi,

just finalized building my new computer. Have the P4P800 with 2.6 P4, 1GB
internal RAM. Bootdrive 40GB IDE0, Master. Two 80GB disk connected to RAID
(as stripe-set). One on RAID IDE0, other on RAID IDE1. Both jumpered as
master. Correct cables (80's) UDMA 5.
Wonder, wonder....it takes about 3 MINUTES (!!!) for the boot proces to
pass through the VIA RAID 'diskdetection' part. It does indicate the correct
disks after check, and boots pretty quick after this. RAID works fine under
XP.
Is this 3 minutes waiting time normal??? I have a P4B533-E in my other
machine with a RAID0 on Promise, and this takes about 10 seconds to pass
through booting.
Thx.

Jos.
 
just finalized building my new computer. Have the P4P800 with 2.6 P4, 1GB
internal RAM. Bootdrive 40GB IDE0, Master. Two 80GB disk connected to RAID
(as stripe-set). One on RAID IDE0, other on RAID IDE1. Both jumpered as
master. Correct cables (80's) UDMA 5.
Wonder, wonder....it takes about 3 MINUTES (!!!) for the boot proces to
pass through the VIA RAID 'diskdetection' part. It does indicate the correct
disks after check, and boots pretty quick after this. RAID works fine under
XP.
Is this 3 minutes waiting time normal??? I have a P4B533-E in my other
machine with a RAID0 on Promise, and this takes about 10 seconds to pass
through booting.
Click to expand...

Update to the latest BIOS, which includes the latest RAID controller BIOS.
It might fix it.
 
Hi,

I flashed to 1014, together with newest VIA Bios 2.1. Gues what. Takes just
as long to find the RAID BIOS detecting NO disks at all. In the mean time my
stripe set still works under XP.
So I removed all jumpers from the two disks: BINGO. Waiting time
disk-detection about 6 seconds. All works fine.
Guess VIA has it's own way of dealing with the old RAID standard about
'bootable sets' and BIOS on/off. I've seen a lot, but this is the weardiest
solution I've seen on RAID.
Nothing in any manual though.
Thx.

Jos.
 
check your drives for jumpers, make sure you have the jumpers removed if you
are using WD drives and on seperate cables....

Basically set them as a single drive no slave and run them on there own
cable

worked for me

Dave
 
Back
Top