Sybase死掉了，打印下面日志，请问各位高手是什么问题

[andyboy]

00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: write error on virtual disk 6 block 288:
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: write error on virtual disk 4 block 18156:
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: write error on virtual disk 4 block 6116:
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: write error on virtual disk 4 block 15780:
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: read error on virtual disk 0 block 800:
00:00000:00000:2003/12/26 02:59:07.79 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00009:2003/12/26 02:59:07.79 server
Error 823 encountered .
00:00000:00009:2003/12/26 02:59:07.79 server Original error was 823, severity 24, state 2
00:00000:00009:2003/12/26 02:59:07.79 kernel ************************************
00:00000:00009:2003/12/26 02:59:07.79 kernel curdb = 1 pstat = 0x4200 lasterror = 823
00:00000:00009:2003/12/26 02:59:07.79 kernel preverror = 0 transtate = 1
00:00000:00009:2003/12/26 02:59:07.79 kernel curcmd = 0 program =
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00AFD54D os_get_cur_stk_desc+ 0x13a (0x0226E9E4, 0x77E7F0B4, 0x77E717E8, 0xFFFFFFFF)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00AFD54D os_get_cur_stk_desc+ 0x13a (0x0226E9E4, 0x0226E79C, 0x0000270F, 0x00000002)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00AD67AA pcstkwalk+ 0x204 (0x00180018, 0x00000002, 0x0000270F, 0x00000000)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00AD6434 ucstkgentrace+ 0x224 (0x00180018, 0x00000001, 0x2002FE26, 0x00000000)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00A902AB ucbacktrace+ 0xab (0x00000000, 0xFFFFFFFF, 0x0226FDB4, 0x00466A81)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00407322 terminate_process+ 0xbdc (0x00000000, 0x00000000, 0x00000000, 0x00000000)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x0046A924 close_network+ 0xc (0x00000337, 0x00000018, 0x00000002, 0x0226FE18)
00:00000:00009:2003/12/26 02:59:08.06 kernel [Handler pc: 0x00466260 ex_stop_recursion installed by the following function:-]
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00466A81 ex_doprint+ 0x137 (0x00000337, 0x00000018, 0x00000002, 0x0226FE18)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x00466943 ex_print+ 0x7e (0x00000008, 0x00000017, 0x00000018, 0x00000002)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x0046A5AF hdl_backout_msg+ 0x24 (0x00000008, 0x00000017, 0x00000018, 0x00000002)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x0046A50B ex_raise+ 0x2b3 (0x227C4658, 0x2002FE26, 0x00000000, 0x0226FEBC)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x004DE0EC buf__writewait+ 0x252 (0x00000007, 0x209D496C, 0x209D496C, 0x2002FBD8)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x005101C4 hk__bufwritewait+ 0xf1 (0x00000000, 0x00000007, 0x00000000, 0x00000001)
00:00000:00009:2003/12/26 02:59:08.06 kernel pc: 0x0050EACF hk__wash_end_cycle+ 0x30 (0x200CC580, 0x00000000, 0x200CC580, 0x209D496C)
00:00000:00009:2003/12/26 02:59:08.06 kernel [Handler pc: 0x0046A58B hdl_backout_msg installed by the following function:-]
00:00000:00009:2003/12/26 02:59:08.07 kernel pc: 0x0050E7E4 hk__wash_main+ 0x382 (0x00000000, 0x00000000, 0x00000000, 0x2155F3FC)
00:00000:00009:2003/12/26 02:59:08.07 kernel pc: 0x0050E45E hk_wash_proc+ 0x15f (0x2155F3FC, 0x00000000, 0x00000000, 0x2155F3FC)
00:00000:00009:2003/12/26 02:59:08.10 kernel pc: 0x00A85957 kpntwrapper+ 0x84 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
00:00000:00009:2003/12/26 02:59:08.10 kernel pc: 0x77E6987C KERNEL32.dll (0x00000000, 0x00000000, 0x00000000, 0x00000000)
00:00000:00009:2003/12/26 02:59:08.10 kernel end of stack trace, spid 9, kpid 1572888, suid 0
00:00000:00009:2003/12/26 02:59:08.10 server Restarted process 'HK WASH'.
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: write error on virtual disk 4 block 15844:
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: write error on virtual disk 4 block 6184:
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: write error on virtual disk 4 block 6308:
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: read error on virtual disk 0 block 800:
00:00000:00000:2003/12/26 02:59:08.10 kernel sddone: Windows NT system error 21: Not ready.
00:00000:00033:2003/12/26 02:59:08.10 server

[zyhlhx]

估计是 需要升级（打补丁）了

[zyhlhx]

或者硬件问题

[charity]

好象是硬件问题

[hobbylu]

你的硬件有问题，或者盘坏掉，或者盘没有连接好

[xyzhh]

应该是操作系统级的问题，不能读写，可能使评判的问题，或者是有病毒了

[xyzhh]

可能是硬盘的问题，或者是有病毒了。^_^!

[dushilangzi]

硬盘空间不够了

[wanyong1980]

硬盘的问题，估计是坏了或电源有问题，检查一下吧

[yhbttfile]

这应该是磁盘错误导致。可能是由于磁盘有坏道了。
下面是SYBASE的错误信息：
Error 823
Severity 24
Message text
I/O error detected during %S_MSG for %S_BUF.
Note This error may be caused by a hardware problem.
Explanation This error occurs when Adaptive Server encounters an I/O error on a read or
write request made to a Sybase device. It usually means you have disk
problems. The parameters in the error message refer to internal Sybase
structures and do not often help determine which device is involved. However,
additional kernel messages in Adaptive Server's error log recorded before the
823 error should indicate which device is involved.
Causes of the 823 error can include the following:
• If the sum of vstart and size exceeds the device size. This can happen on
AIX Systems but is also possible on other UNIX platforms if sysusages or
sysdevices have been manually altered.
• When using UNIX files as devices, if the filesystem is full but the device
appears to have space as tracked by sysusages and sysdevices. This raises
the 823 error during create database or alter database.
CHAPTER 1 Error Message Writeups
227
Action Check the accessibility and condition of the device in question. Once you have
identified and corrected the problem, execute the dbcc checkdb and dbcc
checkalloc commands to ensure that no other damage was caused by the bad
device.
SunOS 5.x (Sun Solaris 2.x)
The 823 error can also appear if the Sun operating system is not configured
correctly for asynchronous I/O.
Adaptive Servers running on Sun machines can use asynchronous I/O on raw
partitions without any special kernel enhancements such as the MtXinu DBM
or Sun DBE. An Adaptive Server running on a SunOS 4.1 or later operating
system attempts to do asynchronous I/O on raw partitions. Successful use of
asynchronous I/O requires that the UNIX kernel be configured to support it.
Two options must be included in the Sun operating system kernel configuration
file when the kernel is built. These are:
options LWP # kernel threads
options ASYNCHIO # asynch I/O (requires LWP)
You can find examples of how to set these options in the original GENERIC
configuration file usually found in /sys/{sun3, sun4}/conf. The exact location of
these files may vary. Do not comment out these options.
An improperly configured kernel causes Adaptive Server to fail the first time it
attempts to do I/O to a raw partition. For example, if your master device is on
a raw partition, and you attempt to start Adaptive Server with that master
device, Adaptive Server displays the following message:
kernel: read error on virtual disk 0 block 28
kernel: invalid argument
server: Failure to open master database for the first time
server: Error 823, Severity 24, State 1
If the master device is located on a UNIX file for which standard disk I/O rather
than asynchronous I/O is used, Adaptive Server starts even if the Sun kernel is
not configured for asynchronous I/O. However, if you attempt a disk init
command on a raw partition, it fails with a 5115 error. Refer to Error 5115 for
more information.
AIX Systems Only
Error 823 may occur if the disk device is run under the Logical Volume
Manager (LVM) , vstart is equal to 2 and the size is not shortened by 2. vstart
needs to be equal to 2 because the first AIX block (1 AIX block equals 2 Sybase
pages) has to be available for the LVM control block (LVCB).
Error 834
228
Version in which this
error is raised
All versions