- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error on syslog
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
Discussions
Discussions
Discussions
Forums
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
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
тАО03-07-2002 08:24 AM
тАО03-07-2002 08:24 AM
what does means this error in syslog.log ?
Mar 7 12:01:41 MISRF01 vmunix: SRA[DPT,c0] (0/2/7/2.4) tgt 4 lun 0 bp 0x4c62f800 ioid 0x1006735 op 0x28 (Read (10)) error 0x70 (current) sense 0x2 (Not Ready) code 0x4 qual 0x2 (Logical Unit Not Ready, Initializing Command Required)
Mar 7 12:01:41 MISRF01 vmunix:
Mar 7 12:01:41 MISRF01 vmunix: SCSI: bp: 000000004c62f800
Mar 7 12:01:41 MISRF01 vmunix: dev: 1f014000
Mar 7 12:01:41 MISRF01 vmunix: cdb: 28 00 00 00 00 10 00 00 04 00
Mar 7 12:01:41 MISRF01 vmunix: residual: 800
Mar 7 12:01:41 MISRF01 vmunix: status: (02) Check Condition
Mar 7 12:01:41 MISRF01 vmunix: sense data: 70 00 02 00 00 00 00 0a 00 00 00 00 04 02 02 00
Mar 7 12:01:41 MISRF01 vmunix: 00 00
Mar 7 12:01:41 MISRF01 vmunix: sense key: (02) Not Ready
Mar 7 12:01:41 MISRF01 vmunix: additional sense code: (04)
Mar 7 12:01:41 MISRF01 vmunix: additional sense code qualifier: (02)
Mar 7 12:01:41 MISRF01 vmunix: SRA[DPT,c0] (0/2/7/2.4) tgt 4 lun 0 bp 0x9ecf9a8 ioid 0x1006736 op 0x28 (Read (10)) error 0x70 (current) sense 0x2 (Not Ready) code 0x4 qual 0x2 (Logical Unit Not Ready, Initializing Command Required)
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 08:29 AM
тАО03-07-2002 08:29 AM
Solutionrun ioscan -funC disk and look for the device attached to hardware address 0/2/7/2.4.
Do you have some external array attached?
GL,
C
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 08:32 AM
тАО03-07-2002 08:32 AM
Re: Error on syslog
This describes a SCSI error. Make sure that your hardware is ok.
Apply the latest patches to the system.
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 08:32 AM
тАО03-07-2002 08:32 AM
Re: Error on syslog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 08:34 AM
тАО03-07-2002 08:34 AM
Re: Error on syslog
you will need to match the device up with the info in th elog:
look at awhat is connected to this path:
0/2/7/2.4
or what device is at :
dev: 1f014000
1f=31 <-major number, and this is normally a disk
0
simplest would be to do ioscan and check there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 08:46 AM
тАО03-07-2002 08:46 AM