View Single Post
  #10  
Old January 22nd 04, 04:30 AM
Danny Tay
external usenet poster
 
Posts: n/a
Default

Tim,

you hit the nail on the head.
I am now succesfull booting up from the RAID1 drive.
This was done like you suggested below opting to install Windows & then
install the Sil driver; rather than using the text based Recovery Console
(which does not correct the problem).
Other than provide the Sil drive floppy, I did not have to supply any other
driver disks (ie.e. Intel ICH5R, ect). Windows installer detected all other
installed drivers for video, Radi0, etc.

All works well now.

Thx for the suggestion.
Danny

"Tim" wrote in message ...
Danny,

Do the repair only - end to end.
IE insert the CD, select install windows and let it ask for the Sil

drivers
picking out the raid driver if there is more then one type - via F6 -

don't
forget your Intel ICH5R connected raid drivers too. It should come up and
say it has found an XP setup on your Sil connected discs and it will (if

it
finds them) ask if you want to do a repair. If it does this then things

are
going well. Select repair, let it finish, reboot and all should be OK

except
for service pack and updates.

After the repair you do not need to go into recovery console at all - you
*shouldn't* have to. But since I can't see over your shoulder it is

possible
that if the non raid driver somehow gets configured to start then XP

startup
could STOP - the driver may be set to start at boot and be marked as
critical. If this is the case it can be fixed but this requires changing
some registry settings.

FYI: The settings for a service under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\ service a

ErrorControl -
0 = Ignore,
1 = Normal, - Display a Warning
2 = Severe, - Causes a switch to Last Known Good
Startup restarts. If this fails, continue as

Normal
3 = Critical - as above, but if Last Known Good fails -- System Crash

Start:
0 = Boot = Before kernel, EG Disk Driver == use this.
1 = System = Started by IO Subsystem in Kernel EG Mouse
2 = Auto = Auto - when needed EG ParPort.sys
3 = On Demand - When Instructed by S/W or User (S/W).
4 = Disabled.

If you had both RAID and Non Raid drivers set to start, then second one is
likely to fail and if that is the Raid driver, your system won't start.
However you seem to be setting things right here. Maybe you just have a

file
missing or it needs to be Expand ed. (See Expand or Copy in the recovery
console).

If that doesn't clear things up I would consider a reinstall.

- Tim



"Danny Tay" wrote in message
u...
Tim,

I booted from the WinXP cdrom & used F6 to reinstall the Si3112R driver,
then I went into the XP Repair mode..
from the Text Console I disabled the Si3112.sys driver, but enabled the
Si3112R.sys driver. Note there is also a "SiFilter" driver for the

SATALINK
which was left enabled.

I exited from the recovery console & rebooted, but the same problem

persist.
I wonder whether loading the wrong driver in the 1st place has actually
damaged the "system"?

After this I disabled the SiFilter & still the problem persists.

I wonder whether my only option is to reinstall WinXP completely... & if

so
will this recognise the RAID1 given that the repair didn't help at all?

Danny

"Tim" wrote in message

...
Danny.

You said the SIL is your boot disc owner... disabling the Si3112

controller
will disable access to the boot disk which you no doubt know.

If you manually or otherwise put all the driver files back in place,

(IE
however you did the reinstall), you would need the driver enabled.

This
may
be all you need to do.

If you can't get that to go then I would:

Do a Windows XP Repair and load the original drivers you loaded with

your
current F6 bios using the F6 method....

This will not damage your system - you will need to reinstall all

service
packs and updates.

If you were to find the disc volume(s) are inaccessible then

unfortunately
that would be as the result of putting the wrong driver in. It would

really
have to be the really wrong driver tho.... Doesn't seem likely. Sil

would
have to make a big bulls up for that to happen and I am sure we would

have
heard about it many times before now if they had.

If an XP Repair doesn't get you there, then I would consider a

temporary
installation of XP on your Intel discs and load the drivers as you

find
you
need them to gain access to the Sil connected discs and either fix or
extract data, reformat, reinstall. If you are quesy about doing a

repair
or
fearful of damage to data, then you may wish to do this as Step 1...

and
do
a backup data backup if you do not have one currently.

Best of luck if you need any.

- Tim



"Danny Tay" wrote in message
u...
Tim,

The BIOS is F6 and everything was running perfectly until I made

that
one
change & one change only (i.e. to the Si3112 driver.). So I did not

make
any
change to the BIOS. It is in F6 version.

I used the WinXP Recovery Console during boot up to disable the

Si3112
driver & install the original Si3112R driver. The changes took place

but
on
reboot the same error occurs so not corection took place.

Danny

"Timothy Drouillard" wrote in message
...
What version of the BIOS are you using?

Did you by any chance decide to upgrade the BIOS at the same time

you
updated the driver?

Many of us (me included) ran into problems with our RAID setup's

when
we
tried BIOS versions F7 or F8. F6 works fine. I haven't had the

guts
to
try
F9 just yet.

"Danny Tay" wrote in message
u...
Hi Tim,

I have tried several times using he boot from "last known good"

but
it
doesn't work because basically it cannot see the RAID1 boot

disk.
So
I
have
to make it see the boot disk 1st.

Danny

"Tim" wrote in message
...
Try "Last Known Good" configuration during boot - F8 I think

at
boot
start.

A few seconds after each windows completes booting and windows

has
'stabilised' this system updates the last known good

configuration
in
the
registry. This has worked everytime I have used it for these

style
problems.

- Tim

"Danny TAY" wrote in message
om...
Hi,

I have a GA-8KNXP (Rev1.0) mobo with Intel 2.8GHz cpu, 1GB

RAM
&
WinXP
Pro.
There are 2 x 120GB Maxtor SATA Disks in RAID1 managed by

the
onboard
Silicon Image SI3112.
The RAID1 disk is also the boot disk.
There are also 2 x 120GB Maxtor SATA Disks in RAID0 manged

by
the
onboard IntelRAID.
The system was running well for the past few mth with the

device
drivers that came with the mobo (i.e. Intel 975 series

mohterboard
utlity cd (ver 1.1)).

However, last Dec-2003, I decided top download the 'latest'

Si3112
drivers from Gigabyte Mobo support website. There were

several
drivers
from that download zip & I must have installed the wrong

driver
(i.e.
Si3112 SATA 1.0.0.44) whereas I should probably have

installed
Si3112R
1.0.0.33.

As a result, when the computer bootsup, it fails to

recognise
the
RAID1 disks & so cannot boot up at all. Safe Mode does not

work.

Questions
=========
1. What is the correct version of SI3112 I should use?
2. How do I correct this problem given I cannot even boot up

from
the
PC? Can you provide a detailed step-by-step explanation? I

have
a
lot
of data on all the RAID1 & RAID0 disks & do not want to have

to
reformat the disks. Is there a simple way to reinstall the

correct
version of Si3112 driver?

Your urgent help is most appreciated.
p.s. - I am using a 2nd computer to send this post message.

Thanks
Danny TAY
email: