The device, \Device\Scsi\aac1, did not respond within the timeout period.

Hi Everyone,

One of my servers has crashed twice for pas two days, same time. In the logs it shows "The device, \Device\Scsi\aac1, did not respond within the timeout period"
The server is a HP Proliant Server and has Server 2003 with SP2 installed.
I ran the Proliant Integrated Management Log viewer and showed a Blue Screen Trap. The actual descriptions are:
Blue Screen Trap(BugCheck, STOP:0X00000077 (0x00000185, 0X00000185, 0X00000001, 0X0138E000))
Blue Screen Trap(BugCheck, STOP:0X0000007A ( (0xC02E686C, 0X00000185, 0XB9A1B8D7, 0X46F95860))

These are 2 separate errors, 1 each for the past 2 days.

Any help would be appreciated.

Kind Regards,
tiki1017
tiki1017Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DavidPresidentCommented:
This indicates timeouts due to deep recovery of disk drive. By any chance are these your basic desktop class drives ... or server / enterprise disks.

If desktop drives then you have a bunch of unrecovered or partially recoverable read errors, and that means that disks are probably due to be retired.

Look at RAID diagnostic logs for errors.
tiki1017Author Commented:
Hi dlethe,

Thanks for the prompt response. This is a server disk (SCSI) with 2 partitions (System and Data). Ill have alook at the Raid Logs and check what I can find.

Do you reckon it could also be a driver issue.
tiki1017Author Commented:
Hi dlethe,

On second thought the one I posted was the report given to me by the HP utility?
Is that the RAID diagnostic log? If not how to I run and generate the logs.
DavidPresidentCommented:
The HP utility knows what the physical disks are doing ... but be prepared for a drive failure and bad blocks, bad blocks on several drives, .. that sort of thing.  Unreadable data or lots of retries causing timeouts.  

Are these disks the HP drives, or some cheap desktop drives?  If they are the desktop drives the firmware is not correct (due to TLER timing), so now you are losing data.  

So official answer, is if these are desktop drives, replace all of them if you value your data and want to cure this.  They must have the proper firmware and be the correct type of disk for that controller.

If they are enterprise class disks, then this indicates (logs would confirm) at least one drive should be replaced.

A temporary treatment (AFTER YOU TAKE A FULL BACKUP) is to do the windows scan disk with the option to repair bad blocks.  This will force full read and make the raid controller repair any unreadable blocks. if it can't in time, then windows will probably let you know.  But this does have risk of causing a marginal disk to crash ... hence need to backup first.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tiki1017Author Commented:
Thanks dlethe! Information was very helpful
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.