SP2 install wanted to replace RAID driver, I said no, now BSOD 7B

[mct@pioneerprogramming.com]

The 2003 server has an old Adaptec 2010S RAID card with the most recent
Adaptec driver (dpti2o.sys) installed in it from July 2003. The driver is
WHQL. It's been running just fine the past 5 years, and I wanted to install
SP2 on it to get it up to date.

During SP2 setup it said something to the effect that it had a newer mass
storage driver for the RAID card that it wanted to use. I don't remember the
exact text of the message, thus I haven't been able to google for it again,
but at the time I was able to search for it and the recommendations I got
generally said not to let it change the driver. I said to keep the current
driver and SP2 finished and when it rebooted it came up just fine.

It ran fine for several weeks since, but when we ran Windows updates on it
last week it gave STOP 0x0000007B on startup. We rebooted it again and it
came up okay. However, when we went to install KB958644 this weekend, upon
reboot it did STOP 0x0000007B again, and this time when we rebooted it gave
the same BSOD for two more reboots before it came up again.

Now I'm scared to reboot the thing, even to run chkdsk. We're verifying our
backups and stuff of it right now and we're fast tracking the new server.

However, I want to know if anyone has a particular recommendation about the
RAID driver, because we no longer have any pre-SP2 backups and if we need to
restore the server I need to know if we could end up with the same problems
because Adaptec never updated the driver.

 

[Dave Patrick]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD 7B

I doubt if it is the driver as you said it's run fine for years. The
hardware itself may be failing. The disk manufacturer will have diagnostic
tools on their web site. This tool may help for disk controller diagnostics.

http://www.moojit.net/index.php?opt...&gid=13&orderby=dmdate_published&ascdesc=DESC

These may also help.

http://www.adaptec.com/en-US/downlo...roductId=ASR-2010S&dn=Adaptec+SCSI+RAID+2010S
http://www.adaptec.com/en-US/downlo...roductId=ASR-2010S&dn=Adaptec+SCSI+RAID+2010S


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"mct@pioneerprogramming.com" wrote:
> The 2003 server has an old Adaptec 2010S RAID card with the most recent
> Adaptec driver (dpti2o.sys) installed in it from July 2003. The driver is
> WHQL. It's been running just fine the past 5 years, and I wanted to
> install
> SP2 on it to get it up to date.
>
> During SP2 setup it said something to the effect that it had a newer mass
> storage driver for the RAID card that it wanted to use. I don't remember
> the
> exact text of the message, thus I haven't been able to google for it
> again,
> but at the time I was able to search for it and the recommendations I got
> generally said not to let it change the driver. I said to keep the current
> driver and SP2 finished and when it rebooted it came up just fine.
>
> It ran fine for several weeks since, but when we ran Windows updates on it
> last week it gave STOP 0x0000007B on startup. We rebooted it again and it
> came up okay. However, when we went to install KB958644 this weekend, upon
> reboot it did STOP 0x0000007B again, and this time when we rebooted it
> gave
> the same BSOD for two more reboots before it came up again.
>
> Now I'm scared to reboot the thing, even to run chkdsk. We're verifying
> our
> backups and stuff of it right now and we're fast tracking the new server.
>
> However, I want to know if anyone has a particular recommendation about
> the
> RAID driver, because we no longer have any pre-SP2 backups and if we need
> to
> restore the server I need to know if we could end up with the same
> problems
> because Adaptec never updated the driver.
>

 

[Thee Chicago Wolf]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD 7B

>The 2003 server has an old Adaptec 2010S RAID card with the most recent
>Adaptec driver (dpti2o.sys) installed in it from July 2003. The driver is
>WHQL. It's been running just fine the past 5 years, and I wanted to install
>SP2 on it to get it up to date.
>
>During SP2 setup it said something to the effect that it had a newer mass
>storage driver for the RAID card that it wanted to use. I don't remember the
>exact text of the message, thus I haven't been able to google for it again,
>but at the time I was able to search for it and the recommendations I got
>generally said not to let it change the driver. I said to keep the current
>driver and SP2 finished and when it rebooted it came up just fine.
>
>It ran fine for several weeks since, but when we ran Windows updates on it
>last week it gave STOP 0x0000007B on startup. We rebooted it again and it
>came up okay. However, when we went to install KB958644 this weekend, upon
>reboot it did STOP 0x0000007B again, and this time when we rebooted it gave
>the same BSOD for two more reboots before it came up again.
>
>Now I'm scared to reboot the thing, even to run chkdsk. We're verifying our
>backups and stuff of it right now and we're fast tracking the new server.
>
>However, I want to know if anyone has a particular recommendation about the
>RAID driver, because we no longer have any pre-SP2 backups and if we need to
>restore the server I need to know if we could end up with the same problems
>because Adaptec never updated the driver.

There'd be a pretty easy way to find out if it is the driver or not.
Especially so if it asked to replace the driver and you told it no and
now have a BSOD. This BSOD is on this driver, correct? You can likely
extract the driver you need from the SP2 CAB file, save it to USB
flash drive, floppy, CD-R, and boot your Server 2003 CD to console
mode and manually overwrite the one it wanted to with the SP2 version?
If it allows you to manually overwrite it while in Windows, you can
probably do that as well. I would back up or rename the original
driver file for safety purposes. It's likely that even though the
original driver that's been running fine for 5 years for you was ok,
perhaps this updated one fixed some issue the original didn't. When's
the last time you scheduled a defrag?

- Thee Chicago Wolf

 

[mct@pioneerprogramming.com]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD



"Dave Patrick" wrote:

> I doubt if it is the driver as you said it's run fine for years. The
> hardware itself may be failing. The disk manufacturer will have diagnostic
> tools on their web site. This tool may help for disk controller diagnostics.

Well, it could always be hardware problems, but STOP 7b is 99% caused by
corrupt NTFS on the system volume or the wrong storage driver installed for
the system volume. Considering how SP2 wanted to change the driver, I'm
thinking it's messing with the driver behind my back. I'm wondering:

Did Microsoft make storage-layer changes in SP2 that newer drivers are
needed to conform to, like with the CPU offload enhancements for NICs?

Did Microsoft actually make a working dpti2o driver part of the base Server
2003 install or a service pack since?

Is said driver compatible with the 2010S and its management software, given
that Adaptec hasn't updated either of them since before Server 2003 was RTM'd?

Is there a newer dpti2o driver out there which is known to work with the
2010S, but which Adaptec hasn't fixed their support website to point to?
Wouldn't be the first time...

The default option when SP2 asked me to change the driver was Yes, so I'm
willing to believe someone at Microsoft has vetted the Microsoft dpti2o
driver for SP2, but I'm not going to change it unless I get some guidance
first.

 

[Dave Patrick]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

The hardware manufacturer's do the driver development. Microsoft then gets
the drivers from the hardware manufacturer. The problem that you can run
into is the service pack and or update correctly identifying the hardware.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"mct@pioneerprogramming.com" wrote:
> Well, it could always be hardware problems, but STOP 7b is 99% caused by
> corrupt NTFS on the system volume or the wrong storage driver installed
> for
> the system volume. Considering how SP2 wanted to change the driver, I'm
> thinking it's messing with the driver behind my back. I'm wondering:
>
> Did Microsoft make storage-layer changes in SP2 that newer drivers are
> needed to conform to, like with the CPU offload enhancements for NICs?
>
> Did Microsoft actually make a working dpti2o driver part of the base
> Server
> 2003 install or a service pack since?
>
> Is said driver compatible with the 2010S and its management software,
> given
> that Adaptec hasn't updated either of them since before Server 2003 was
> RTM'd?
>
> Is there a newer dpti2o driver out there which is known to work with the
> 2010S, but which Adaptec hasn't fixed their support website to point to?
> Wouldn't be the first time...
>
> The default option when SP2 asked me to change the driver was Yes, so I'm
> willing to believe someone at Microsoft has vetted the Microsoft dpti2o
> driver for SP2, but I'm not going to change it unless I get some guidance
> first.
>

 

[mct@pioneerprogramming.com]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD



"Thee Chicago Wolf" wrote:

> There'd be a pretty easy way to find out if it is the driver or not.
> Especially so if it asked to replace the driver and you told it no and
> now have a BSOD. This BSOD is on this driver, correct? You can likely
> extract the driver you need from the SP2 CAB file, save it to USB
> flash drive, floppy, CD-R, and boot your Server 2003 CD to console
> mode and manually overwrite the one it wanted to with the SP2 version?

Well, I found the file in question. dpti2o.sys dated February 17, 2007. I
really don't want to just copy that file over, though, unless someone out
there can say it works with the 2010S. If someone has installed a RAID with a
2010S and installed Server 2003 on it without having to press F6, I'd be very
interested to hear about it.

> If it allows you to manually overwrite it while in Windows, you can
> probably do that as well. I would back up or rename the original
> driver file for safety purposes. It's likely that even though the
> original driver that's been running fine for 5 years for you was ok,
> perhaps this updated one fixed some issue the original didn't. When's
> the last time you scheduled a defrag?

I don't think this system has ever been defragged. I've never known STOP 7B
to result from slow disks, however.

 

[mct@pioneerprogramming.com]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD



"Dave Patrick" wrote:

> The hardware manufacturer's do the driver development. Microsoft then gets
> the drivers from the hardware manufacturer. The problem that you can run

The dpti2o file in the SP2 cab is 12K, the older driver from Adaptec's web
site is 20K. They had to have updated it at some point in the past, assuming
this version of dpti2o is meant to be used with the 2010S.

If this version supports the 2010S, someone out there has to know about it.
Has anyone managed to install Server 2003 SP2 on this card without pressing
F6?

If Adaptec dropped support for the 2010S in the SP2 version, then SP2 has no
business asking if it can replace the driver with an incompatible version.

I know I'm not the first one to run into this issue because I was able to
google the message I got at the time, but I haven't seen anything else online
about SP2-installed storage drivers causing STOP 7B, so I have to assume it
isn't generally a problem to install SP2's drivers, especially since the
default option is to replace the driver.

> into is the service pack and or update correctly identifying the hardware.

So you're thinking the SP2 installer might be misidentifying the 2010S?
Adaptec SCSI RAID cards are common. How can this be happening without causing
massive problems for companies with older servers, which certainly should be
showing up online?

 

[Dave Patrick]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

F6 is only needed when the controller driver isn't included in the
installation media and I couldn't find it here.
http://www.windowsservercatalog.com/default.aspx

No, I'm not saying anything of the like. Just that generally most people
turn down drivers from Windows Update for this reason.

I also agree that file system corruption is more likely here but the easiest
non-destructive thing to do is verify the hardware before you move on to
chkdsk which may attempt fix the damage at the expense of the operating
system (or other files).



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"mct@pioneerprogramming.com" wrote:
> The dpti2o file in the SP2 cab is 12K, the older driver from Adaptec's web
> site is 20K. They had to have updated it at some point in the past,
> assuming
> this version of dpti2o is meant to be used with the 2010S.
>
> If this version supports the 2010S, someone out there has to know about
> it.
> Has anyone managed to install Server 2003 SP2 on this card without
> pressing
> F6?
>
> If Adaptec dropped support for the 2010S in the SP2 version, then SP2 has
> no
> business asking if it can replace the driver with an incompatible version.
>
> I know I'm not the first one to run into this issue because I was able to
> google the message I got at the time, but I haven't seen anything else
> online
> about SP2-installed storage drivers causing STOP 7B, so I have to assume
> it
> isn't generally a problem to install SP2's drivers, especially since the
> default option is to replace the driver.
>
>> into is the service pack and or update correctly identifying the
>> hardware.
>
> So you're thinking the SP2 installer might be misidentifying the 2010S?
> Adaptec SCSI RAID cards are common. How can this be happening without
> causing
> massive problems for companies with older servers, which certainly should
> be
> showing up online?
>

 

[mct@pioneerprogramming.com]

RE: SP2 install wanted to replace RAID driver, I said no, now BSOD 7B

OK, more information. I compared the two versions of dpti2o.sys and found out
that the version with SP2 is indeed newer than the version on Adaptec's
website, and it looks like they last updated it with Server 2003 SP1,
actually.
Adaptec's site: dpti2o.sys file version 3.13
SP2 cab: dpti2o.sys file version 3.13-Sp1 RTC01

This tells me that I should be able to just change drivers in Device Manager
and select a generic Adaptec SCSI RAID miniport driver, but I pick "Don't
search, I will choose" and the only driver in there listed under Adaptec is
the currently installed driver. Anyone know what I can do to update the
driver?

 

[mct@pioneerprogramming.com]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD



"Dave Patrick" wrote:

> F6 is only needed when the controller driver isn't included in the
> installation media and I couldn't find it here.
> http://www.windowsservercatalog.com/default.aspx

Neat, I'll have to check that site out later.

> No, I'm not saying anything of the like. Just that generally most people
> turn down drivers from Windows Update for this reason.

Well, I found out that the SP2 cab driver is indeed newer, if I can find a
way to install it.

> I also agree that file system corruption is more likely here but the easiest
> non-destructive thing to do is verify the hardware before you move on to
> chkdsk which may attempt fix the damage at the expense of the operating
> system (or other files).

I really don't know what I can do to test this card, especially since those
Moojit programs are so expensive. Anyone know of a Linux utility to do it?

 

[Dave Patrick]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Does the adaptec storage manager tell you anything? The disk manufacturer's
tools?



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"mct@pioneerprogramming.com" wrote:
> Neat, I'll have to check that site out later.
>
>> No, I'm not saying anything of the like. Just that generally most people
>> turn down drivers from Windows Update for this reason.
>
> Well, I found out that the SP2 cab driver is indeed newer, if I can find a
> way to install it.
>
>> I also agree that file system corruption is more likely here but the
>> easiest
>> non-destructive thing to do is verify the hardware before you move on to
>> chkdsk which may attempt fix the damage at the expense of the operating
>> system (or other files).
>
> I really don't know what I can do to test this card, especially since
> those
> Moojit programs are so expensive. Anyone know of a Linux utility to do it?

 

[Thee Chicago Wolf]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD 7B

>OK, more information. I compared the two versions of dpti2o.sys and found out
>that the version with SP2 is indeed newer than the version on Adaptec's
>website, and it looks like they last updated it with Server 2003 SP1,
>actually.
>Adaptec's site: dpti2o.sys file version 3.13
>SP2 cab: dpti2o.sys file version 3.13-Sp1 RTC01
>
>This tells me that I should be able to just change drivers in Device Manager
>and select a generic Adaptec SCSI RAID miniport driver, but I pick "Don't
>search, I will choose" and the only driver in there listed under Adaptec is
>the currently installed driver. Anyone know what I can do to update the
>driver?

As I posted earlier...

You can likely extract the driver you need from the SP2 CAB file, save
it to USB flash drive, floppy, CD-R, and boot your Server 2003 CD to
console mode and manually overwrite the one it wanted to with the SP2
version? If it allows you to manually overwrite it while in Windows,
you can probably do that as well. I would back up or rename the
original driver file for safety purposes.

You can also extract it from the CAB, put the updated file in
C:\Windows\Driver Cache\i386. I imagine that if you replace it in safe
mode it will not complain if you overwrite the existing (old) driver.

- Thee Chicago Wolf

 

[Thee Chicago Wolf]

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

Re: SP2 install wanted to replace RAID driver, I said no, now BSOD

>I really don't know what I can do to test this card, especially since those
>Moojit programs are so expensive. Anyone know of a Linux utility to do it?

I forgot to ask, is the firmware on this card up to version 3b0a?

- Thee Chicago Wolf