SCSI controller went bad, replaced with different one

[Brazen]

We had a SCSI controller go bad in a server, so we replaced it with a new one (different model) but now it is blue screening on boot up with INACCESSIBLE BOOT DEVICE at the top. I'm guessing maybe it needs drivers for the new SCSI controller? Anybody know how I can get drivers onto the system?

 

[imported_dakota81]

It's not so much that it needs drivers for the new controller, rather the system needs the drivers for the old controller removed, that's the hangup. If I knew how to do it, I'd explain it, but unfortunately I don't know how to remove the drivers if it's not able to boot into Windows.

 

[Brazen]

well I gave up. I've booted to an ide drive and am copying off the data and re-installing the system.

 

[Smilin]

Bummer.

There are quite a few things you can do to correct a Stop 0x0000007B. There is even a really good chance that a repair install would have fixed it.

Dakota is right too. The old drivers attempting to start as well as any filter drivers are partially causing the 7B. During the course of a repair install when you reach GUI mode setup you can Shift-F10 for a command prompt, bring up regedit and hack the old drivers out.

Don't give up so easy next time

 

[redbeard1]

If the old card still works with no drives hooked up to it, install it back and have the hard drives hooked to the new card. If this works, it should boot, let you install the new driver, and then allow removal of the old card.

 

[Smilin]

mmm, doesn't really work that way.

 

[Brazen]

Originally posted by: Smilin
Bummer.

There are quite a few things you can do to correct a Stop 0x0000007B. There is even a really good chance that a repair install would have fixed it.

Dakota is right too. The old drivers attempting to start as well as any filter drivers are partially causing the 7B. During the course of a repair install when you reach GUI mode setup you can Shift-F10 for a command prompt, bring up regedit and hack the old drivers out.

Don't give up so easy next time

Oh well, it sounds good, but too late. I tried googling around and didn't find any info. I was in a bit of a hurry, and employees were ready to break my door down if I didn't get the data shares back up right away.

 

[Smilin]

employees were ready to break my door down if I didn't get the data shares back up right away.

Then you did the right thing. Gotta do what you gotta do.

 

[redbeard1]

Originally posted by: Smilin
mmm, doesn't really work that way.

What he already had done was out of sequence to the proper way to have done it.

I've moved windows installations on the same computer from ide to ide raid, ide to scsi and scsi to ide successfully. The first step is to install the new card first, get the drivers installed so windows recognizes it and then move the install to the new controller. It has been my experience that as long the new device is installed and detected properly before any move is attempted, the procedure works. I'm sure this won't work all of the time, but it can be done.

 

[bsobel]

Originally posted by: dakota81
It's not so much that it needs drivers for the new controller, rather the system needs the drivers for the old controller removed, that's the hangup. If I knew how to do it, I'd explain it, but unfortunately I don't know how to remove the drivers if it's not able to boot into Windows.

The old drivers should do no harm, he's missing drivers for the new card.
Bill

 

[Brazen]

Originally posted by: redbeard1

Originally posted by: Smilin
mmm, doesn't really work that way.

What he already had done was out of sequence to the proper way to have done it.

I've moved windows installations on the same computer from ide to ide raid, ide to scsi and scsi to ide successfully. The first step is to install the new card first, get the drivers installed so windows recognizes it and then move the install to the new controller. It has been my experience that as long the new device is installed and detected properly before any move is attempted, the procedure works. I'm sure this won't work all of the time, but it can be done.

That is all fine and dandy, but how am I going to install drivers onto a system drive that I can not boot to? I know the "proper" sequence for a PLANNED move to a new controller card, however you don't have much choice when the old controller unexpectedly dies, now do ya?