asked on

An error was detected on device \Device\Harddisk... during a paging operation

I have a problem with SBS 2003 server (the server has 2 x RAID1; OS is installed on the first RAID1 that is build using Dell SAS/5i controller; on the second RAID1 that is built using Adaptec SerialATA HostRaid Controller 1220SA are installed all the applications, i.e. Exchange and also the shares).

At some point this error is being logged:

Event Type:      Error
Event Source:      adp3132
Event Category:      None
Event ID:      9
Date:            25/11/2008
Time:            03:00:34
User:            N/A
Computer:      NBS-LON02-S01
Description:
The device, \Device\Scsi\adp31321, did not respond within the timeout period.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 68 00 ......h.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 01 01 00 50 00 00 00 00 ...P....
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 0b 00 00 00 ........
0030: 00 00 00 00 07 00 00 00 ........

Then there a lot of these errors:

Event Type:      Warning
Event Source:      Disk
Event Category:      None
Event ID:      51
Date:            25/11/2008
Time:            03:00:52
User:            N/A
Computer:      NBS-LON02-S01
Description:
An error was detected on device \Device\Harddisk1 during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 ba 00 ..h...º.
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2d 01 00 00 0e 00 00 c0 -......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 68 8b 23 00 00 00 00 00 h‹#.....
0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
0038: 40 00 00 08 20 00 0b 00 @... ...
0040: 4e 20 0a 12 82 03 20 40 N ..‚. @
0048: 00 00 00 00 78 00 00 00 ....x...
0050: 00 00 00 00 f0 6b d8 88 ....ðkØˆ
0058: 00 00 00 00 58 9a 35 8a ....Xš5Š
0060: 50 f5 20 8b e7 cb ef 07 Põ ‹çËï.
0068: 2a 00 07 ef cb e7 00 00 *..ïËç..
0070: 03 00 00 00 00 00 00 00 ........
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

Eventually the server needs to be rebooted as it stops responding.

Your advice is highly appreciated.

Kind regards,

Jay

willettmeister

You will probably find this to be a controller problem. If you have a spare one slap it in and see what happens.

jbodys

ASKER

This is the spare one. I have already changed it.

jbodys

ASKER

I could change it again, but the last time I did that it turned out to be quite a hassle. I had to build a new RAID1 and restore the data from the backup. It took quite a while... Have you got a better idea of doing it?

ASKER CERTIFIED SOLUTION

willettmeister

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rowers

You can always try a chkdsk.
If the drive has a bad area it can hang the system like above.
If its worse then a reinstallation with a slow initialization should fix it ultimately.
Since you have swapped another controller into the system i would not suspect that its the culprit.
The only items left would be your drives or the data on the drives...

SimonShaw

I have exactly the same error with the same controller type, Adaptec 1220SA, on the same operating system - Windows Server 2003 (SBS in my case).
Another similarity is that it is the second RAID controller in the system, although mine is Fujitsu-Siemens (LSA controller) not Dell. This seems significant to me.
Since all these controllers are effectively software RAID (meaning that the driver does the mirroring or striping work, not a dedicated processor in the controller) it would seem to be some kind of software incompatibility between this Adaptec HostRAID driver and the Dell integrated RAID controller (or LSA controller in the Fujistu-Siemens in my case). Once the Adaptec driver suffers an error, the array becomes invisible or gets damaged.
So much for speculation.
Did you get round this problem, and if so how?
I am about to change to another type of controller and would like to know if that is likely to work.
TIA

gbb0330

I have exactly the same error with the same controller type, Adaptec 1220SA, on the same operating system - Windows Server 2003 Standard - used as a file server and wins server.
Another similarity is that it is the second RAID controller in the system, the other one is VT8237A SATA RAID built into a cheap ASUS mobo. RAID 1 on both controllers. OS is installed on the via raid, shared folders on the adaptec raid.

I replaced the controller, the memory and the power supply, ran chkdsk, and fix/verify on the adaptec array - still experiencing the same problem - computer freezes, sometimes i can even move the mouse.

any help will be greatly appreciated

ansto

I think you need to increase the timeout value for the controller from the windows default 10 second to 60 seconds. The Release notes mentions it. I have just tried it for SBS 2003, just had this timeout error:
---

----------------------------------------------------------------
8.2 Windows Specific Registry Parameters
NOTE: This setting applies to Windows Server 2003, Windows 2000, and Windows XP.
The only Windows-specific parameter that you can currently change is the
TimeOutValue. This registry option increases the timeout for all disk class
devices (in contrast to the driver-specific registry parameters that affect only
your HostRAID adapter).
The default TimeOutValue is 10 seconds. Follow these steps to increase this
value to 60 seconds:
1) Select Run from the Start button.
2) Browse to the folder containing above mentioned version of the HostRAID
driver, select the file "TIMEOUT.REG" and click OK.
Note: Changes made with the Registry Editor do not take effect until you reboot
your computer.

---
The registry key is actually:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk]
"TimeOutValue"=dword:0000003C