ADSM-L

Re: BSOD: STOP: 0x000000B8

2003-12-10 10:37:25
Subject: Re: BSOD: STOP: 0x000000B8
From: Greyling Leigh <LGreyling AT OMAM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 10 Dec 2003 17:36:28 +0200
HI Guys

Mark, did you ever get this problem solved, 'cuase I'm now sitting with a
similar problem?

When I attempt to read data of a cartridge with a bad block, the server goes
belly up.

I've upgrade from 5.1.5.0 to 5.1.8.0, along with the device driver. I'm sure
this problem only started after the drive firmware was upgraded to 36U3, as
we had no problem when we were on 35V0, in fact we upgraded to 35V0 to solve
an issue where we had numerous tapes being marked as having 1000's of bad
blocks, but after upgrading the firmware, the tapes were fine, with no
errors up 'til now.

3584 with 3 drives,
library firmware 3480,
drive firmware 36U3,
library driver 5.0.6.5,
Adsmscsi.sys 5.1.8.3,
Windows 2000 SP4

Leigh.

-----Original Message-----
From: Mark Bertrand [mailto:Mark.Bertrand AT USUNWIRED DOT COM]
Sent: 14 August 2003 21:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: BSOD: STOP: 0x000000B8


Anyone ever seen or have a solution for this?

Problem: TSM server is "blue screening" every couple of hours after a drive
replacement and firmware, software drivers updated for library and all
drives.

We are currently at IBM 3584 library with 6 drives, Library firmware v.
3300, drive firmware v. 36U3, drive software driver (ibmtape.sys) v.
5.0.5.4, library software driver (ibmchgr.sys) v. 5.0.5.4, Adsmscsi.sys
4.2.2.4, OS Windows 2000 v. 5.0(Build 2195: Service Pack 3), Storage
Management Server for Windows - Version 5, Release 1, Level 6.3

Microsoft Knowledge Base Article - 287582

SYMPTOMS
After you install Tivoli Storage Manager software on a computer that is
running Windows 2000 Server, you may receive the following blue screen error
message when you restart the computer:
STOP: 0x000000B8 (0x00000000,0x00000000,0x00000000,0x00000000)
ATTEMPTED_SWITCH_FROM_DPC

CAUSE
This issue can be caused by the Adsmscsi.sys driver in Storage Manager. If
you analyze the dumpfile, you see that the Tivoli Storage Manager driver is
calling KeDelayExecutionThread inside of a deferred procedure call (DPC).

RESOLUTION (gotta love this?)
To work around this issue, start the computer in Safe mode, which prevents
the driver from loading, and then disable the following Tivoli services:
*       TSM Scheduler
*       TSM Server1
*       ADSM Server
After you stop these services, restart the computer.

To resolve this issue, visit the following Tivoli Web site to obtain an
updated Windows 2000-compatible version of Storage Manager software:
<http://www.tivoli.com>

Any help is appreciated.
Thanks,
Mark Bertrand


This communication is subject to specific restrictions and disclaimers. Details 
are contained at the following link:
http://www.omam.com/OMAMSA_E-mail_Disclosure/

<Prev in Thread] Current Thread [Next in Thread>