Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 05:45 PM
11-26-2001 05:45 PM
I realised that there are some errors reflected on the syslog.log file showing 'SCSI:
Async
write error - dev: b 31 0x025000, errno: 5, resid:8192'.
This happens once on Nov 13 17:35:22
and did not encountered since then, please advise on the possible cause.
What is the meaning of the error?
Regards,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 06:09 PM
11-26-2001 06:09 PM
SolutionWhat's the device at c2t5d0?
run ioscan -fn and check whose device driver is c2t5d0
not sure what the problem is all about yet, but it could be due to a disocnnected or missing device (probably due to a system restart/power trip)
d_b
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 07:38 PM
11-26-2001 07:38 PM
Re: K400
Since it occurred a couple of weeks ago and only occurred once, there is no way to know if this was caused by someone changing cables while the system is running (never recommended!) or a transient power problem (someone kicked the power cable?).
It's a good idea to look for errors and warnings in syslog automatically everyday using a cron job.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 09:47 PM
11-26-2001 09:47 PM
Re: K400
To add on, you can test your harddisk's integrity with mstm/cstm or dd.
Example of using dd:
# dd if=/dev/dsk/c0t3d0 of=/dev/null bs=8192
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2001 11:56 PM
11-26-2001 11:56 PM