- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Shadowset Member Problem
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
тАО12-03-2009 10:37 AM
тАО12-03-2009 10:37 AM
Shadowset Member Problem
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1391059
I successfully dismount the DKA0: disk and make it shadow set member again. Now the copying is in progress.
The problem is that, Error Count are continuously increasing. Can you please guide me that why are these error occurring, and how to overcome them.
See the attached document for the "sh dev d" command output, errors are mark in red.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 10:44 AM
тАО12-03-2009 10:44 AM
Re: Shadowset Member Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 11:12 AM
тАО12-03-2009 11:12 AM
Re: Shadowset Member Problem
there is some hardware problem in the SCSI path to DKA0 or on the DKA0 disk itself. This hardware problem was also the cause for the error (0x8C = DRVERR) you've shown in your previous post (when trying to boot from DKA0).
On OpenVMS I64, you can only use SEA (System Event Analyzer, part of the WEBES tool set) for ERRLOG.SYS analysis. If you have an OpenVMS Alpha system, you could copy the ERRLOG.SYS file to that node and use DECevent ($ DIAGNOSE command).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 11:23 AM
тАО12-03-2009 11:23 AM
Re: Shadowset Member Problem
Your SCSI bus is mis-terminated, your disk(s) is/are bad, your controller has failed, or some other low-level or hardware issue has arisen here.
If you've simply tried swapping the old disk back into this rx3600 series OpenVMS I64 box (as could be inferred from your notes), that's not a good strategy. And you do now know that there are problems with the disk or with the bus or with the controller here. Or with the server.
Depending on the specific details of the error(s) arising here, simply continuing to run this configuration could risk your data.
What follows is a write-up on the error analysis tools, but (bluntly) this is where you get your service provider spun up and moving first and foremost, and investigate details later...
http://labs.hoffmanlabs.com/node/295
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 12:45 PM
тАО12-03-2009 12:45 PM
Re: Shadowset Member Problem
You might like to bear in mind the recommendation that members of a system disk shadow set have different unit IDs (LUNs) unless you're doing dump off system disk. Having both disks with the same Unit ID can lead to the system not knowing what disk it is meant to be writing the crash dump to and potentially writing over it.
This won;t cause the problem that you have here, but it may cause others.
Steve