Problem with bootup

[will_s]

Not sure if its a Vista or motherboard problem. Have Vista running on a stripe Raid setup ( using Gigabyte Raid ) and have a esata drive on my normal sata controllers ( ICH9 ). Now when I start with my esata drive turned on it wont boot to the raid drives and I get a message "bootmgr not found" ( something like that ). So I turned the esata drive off and it boots ok and then I turn the esata back on and all is ok.

Its annoying so anyway to make sure the Raid is the 1st boot device always. Have looked in BIOS and it just shows hard drive

btw: am using the Gigasbyte raid instead of the Intel raid as I couldnt get Vista to find the drivers for the ICH9 on the Gigabyte setup CD ( found the gigabytes one ok ) and I dont have a floppy to use and follow their *&^% instructions.

 

[gerryf]

Not familiar with that motherboard, but you should be able to set the boot order in bios so that the esata drive is not the first boot device.
Not sure if its a Vista or motherboard problem. Have Vista running on a stripe Raid setup ( using Gigabyte Raid ) and have a esata drive on my normal sata controllers ( ICH9 ). Now when I start with my esata drive turned on it wont boot to the raid drives and I get a message "bootmgr not found" ( something like that ). So I turned the esata drive off and it boots ok and then I turn the esata back on and all is ok.

Its annoying so anyway to make sure the Raid is the 1st boot device always. Have looked in BIOS and it just shows hard drive

btw: am using the Gigasbyte raid instead of the Intel raid as I couldnt get Vista to find the drivers for the ICH9 on the Gigabyte setup CD ( found the gigabytes one ok ) and I dont have a floppy to use and follow their *&^% instructions.

 

[will_s]

problem is its not a true esata

its a add on bracket that connects to the onboard ICH9 sata controller
Not familiar with that motherboard, but you should be able to set the boot order in bios so that the esata drive is not the first boot device.
Not sure if its a Vista or motherboard problem. Have Vista running on a stripe Raid setup ( using Gigabyte Raid ) and have a esata drive on my normal sata controllers ( ICH9 ). Now when I start with my esata drive turned on it wont boot to the raid drives and I get a message "bootmgr not found" ( something like that ). So I turned the esata drive off and it boots ok and then I turn the esata back on and all is ok.

Its annoying so anyway to make sure the Raid is the 1st boot device always. Have looked in BIOS and it just shows hard drive

btw: am using the Gigasbyte raid instead of the Intel raid as I couldnt get Vista to find the drivers for the ICH9 on the Gigabyte setup CD ( found the gigabytes one ok ) and I dont have a floppy to use and follow their *&^% instructions.

 

[gerryf]

motherboard model please?

 

[will_s]

GA-X38-DQ6

motherboard model please?

 

[andy]

Not sure if its a Vista or motherboard problem. Have Vista running on a stripe Raid setup ( using Gigabyte Raid ) and have a esata drive on my normal sata controllers ( ICH9 ). Now when I start with my esata drive turned on it wont boot to the raid drives and I get a message "bootmgr not found" ( something like that ). So I turned the esata drive off and it boots ok and then I turn the esata back on and all is ok.

Its annoying so anyway to make sure the Raid is the 1st boot device always. Have looked in BIOS and it just shows hard drive

The boot drive is determined by the order of the drives in Hard Disk
Boot Priority.

btw: am using the Gigasbyte raid instead of the Intel raid as I couldnt get Vista to find the drivers for the ICH9 on the Gigabyte setup CD ( found the gigabytes one ok ) and I dont have a floppy to use and follow their *&^% instructions.

The problem is the whenever the bios detects a change in the hard disk
configuration, it reorders the drives in Hard Disk Boot Priority to a
default order.

 

[will_s]

The problem is the whenever the bios detects a change in the hard disk
configuration, it reorders the drives in Hard Disk Boot Priority to a
default order.

I thought something like that. Cant see anything in the Bios that will let
me change this.

Actually it may help me with something.......will put a stripped down
version ( from a local pc mag ) of Ubuntu on this drive and went i want to
play with it its just a matter of turning the esata drive on before booting

 

[andy]

I thought something like that. Cant see anything in the Bios that will let
me change this.

Actually it may help me with something.......will put a stripped down
version ( from a local pc mag ) of Ubuntu on this drive and went i want to
play with it its just a matter of turning the esata drive on before booting

You have to run the raid drives off of the Intel SATA controller. The
JMicron controller will always default to below the chipset SATA
controller in hard disk boot priority.

 

[will_s]

You have to run the raid drives off of the Intel SATA controller. The
JMicron controller will always default to below the chipset SATA
controller in hard disk boot priority.

Couldnt get the divers for the intel .....had instructions to make a floppy
for these but as I have no floppy these were useless. The drivers for the
JMicron ( gigatbyte ) are there on the Gigabyte CD but cant get the Intel
ones of the CD.

Anyway the esata dive is in a enclosure that has a switch on the back and
its only an arms reach to turn on or off