- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- K-Class SCSI Critical Error
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
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
тАО05-01-2001 10:17 AM
тАО05-01-2001 10:17 AM
I took HP/UX for Experienced Admins last month, but I am still learning.
My problem:
In the syslog yesterday I have a vmunix: SCSI request timeout. Critical error on 10_0.6.0. I think that is one of the internal 4GB Seagate OS disks.
There is an AutoRAID with all the slots filled with 9GB disks. The error is not on any of those disks.
Right now I do not know if the 2-4GB internal disks are mirrored. I do not think we have any type of HP support, but I need to find out how to purchase support from HP.
The syslog.log said to run a resdata command to find out the error. I have included that file in this message if anyone can look at it and point me in the right direction.
Thanks,
Tim Krego
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 12:26 PM
тАО05-01-2001 12:26 PM
SolutionI can't be sure but 10.0.6 is probably your boot disk so it is vital to get this fixed soon. Because it is a boot disk you will need to make sure you have a good backup before disk replacement.
1) ioscan -C disk -fn | lp
This will give you a list of attached disks
2) vgdisplay -v /dev/vg00
Look for the Physical Volumes sections:
If you have only 1 volume listed then you are not mirrored. If you have more than 1 then you MAY be mirrored. At this point also look
at the disk devices associated with vg00 and compare them to your ioscan listing. You should then be able to find 10.0.6 and know that it is in vg00. (If not then do a vgdisplay of vgxx until you find it. I think it's vg00).
3) If you found multiple physical volumes for vg00 then note the locigal volumes listed with the vgdisplay.
4) For each logical volume do an lvdisplay
e.g. lvdisplay /dev/vg00/lvol3
Look for Mirror Copies >= 1 and LV status = available/syncd. If both of these conditions are present for every logical volume then you
truly mirrored. I assume anyone who did this also took care of the mkboot stuff.
If you are mirrored then the replacement is really easy if not it could be an OS reload.
You can contact HP contracts at 1-800-386-1115 to see if you have a service agreement in force.
Good Luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 12:42 PM
тАО05-01-2001 12:42 PM
Re: K-Class SCSI Critical Error
I forgot to mention if this is the boot disk and especially if it's not mirrored, ckeck out the make_recovery command (part of Ignite-UX).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 12:52 PM
тАО05-01-2001 12:52 PM
Re: K-Class SCSI Critical Error
10/0.6.0 is the default address on the K460 for the boot drive. 10/0 says it is internal; 6.0 is the standard SCSI address for the boot disk (2.0 is the CD-ROM and 0.0 is the tape drive)
You don't happend to have a DLT drive on this bus do you? That happens to be a known cause of SCSI errors. Also, have you used XSTM to strip the drive and look at the error logs? This might give you some insight on whether this is a reoccuring phenomenon or a one time thing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 12:59 PM
тАО05-01-2001 12:59 PM
Re: K-Class SCSI Critical Error
There is a Quantum DLT connected to 10/0.4.0 that has been hooked up since Feb.
I do not know what XSTM is so I will have to look for that.
This is the only error in syslog.log since a reboot on 3/14/01.
Thanks
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 01:13 PM
тАО05-01-2001 01:13 PM
Re: K-Class SCSI Critical Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 01:21 PM
тАО05-01-2001 01:21 PM
Re: K-Class SCSI Critical Error
The tape drive is a DLT4000. I am not sure why it is hooked to that interface. I assume because we don't have another interface to hook it to.
The error happened at 2:00 EST yesterday so no backup was running at the time. The machine is at a remote location so I don't know if someone may have tripped over a cable, etc.
I use telnet to connect to the machine. I can't get Exceed to connect remotely, but that is another issue. I cannot run XSTM, but I did try to run MSTM but have some problems with the text display.
Since this is the first error I am hoping that it may be a fluke. HP support is supposed to call me tomorrow to purchase a contract. I am going to create another make_recovery tape now.
Thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 01:38 PM
тАО05-01-2001 01:38 PM
Re: K-Class SCSI Critical Error
To give you an example, two DLT 4000's shared a single SCSI card and backups were taking 12.5 hours. (KS989-650 3.75Gb RAM EMC disks) With the addition of another card dedicated to the DLT's the time dropped to 10.5 hours. Does this tell you something about the bandwidth saturation we were experiencing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2001 01:56 PM
тАО05-01-2001 01:56 PM