- 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 04:25 AM
тАО12-03-2009 04:25 AM
I have rx3600 attached with MSA30 via SCSI Cables. O/S is installed on MSA on DKA0 Disk. O/S is not loading and gives error
%SYSBOOT-F-LDFAIL, unable to load SYS$PUBLIC_VECTORS.EXE, status = 0000008C
There is a mirror disk DKD0, I boot the server from there using fs4: filesystem
through EFI Shell. Server booted successfully.
My Questions is that did both DKA0 and DKD0 are synchronized or not. If I boot the server from (DKA0 / fs0:) did it boot successfully or not. Mean, both DKA0 or DKD0 are synchronized now or not.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 05:17 AM
тАО12-03-2009 05:17 AM
Re: Shadowset Member Problem
%SYSTEM-F-DRVERR, fatal drive error
It appears that DKA0 is faulty. I would assume it has been dropped from the shadowset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 05:52 AM
тАО12-03-2009 05:52 AM
Re: Shadowset Member Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 05:55 AM
тАО12-03-2009 05:55 AM
Re: Shadowset Member Problem
My purpose is that, first i remove the DKA0 from the shadow set and the make it member of shadow set again, so that date from DKD0 copied to DKA0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:01 AM
тАО12-03-2009 07:01 AM
Re: Shadowset Member Problem
What do you mean by "There is a mirror disk DKD0"
Mirror usually means a controller based duplicate (raid 1). But you are also talking about shadowing, and that usually means host based synchronization of multiple disk copies.
I am a bit hesitant to make any recommendations, because the shadowing question you ask is pretty basic, and doing the wrong thing can do a lot of damage.
You need to provide more info, for example show the output of
$ show device /full dka0
$ show device /full dkd0
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:03 AM
тАО12-03-2009 07:03 AM
Solutionhttp://h71000.www7.hp.com/doc/732FINAL/DOCUMENTATION/PDF/aa-pvxmj-te.PDF
At its simplest (and barring cases where the disk error here is secondary to an error elsewhere in the configuration), you're going to replace the disk, MOUNT it into the shadowset, and wait for shadowing to copy the data over.
The basic command looks something like this:
MOUNT /CONFIRM /SYSTEM DSAu: /SHADOW=($n$DKA0) VolumeLabel
You'll need to customize that command to reflect your local system environment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:05 AM
тАО12-03-2009 07:05 AM
Re: Shadowset Member Problem
How current are your backups of your disks?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:14 AM
тАО12-03-2009 07:14 AM
Re: Shadowset Member Problem
My mistake, there is no hardware raid controller. this is host based synchronization or shadowing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:27 AM
тАО12-03-2009 07:27 AM
Re: Shadowset Member Problem
$ sho dev/ful sys$sysdevice
$ mcr sysgen show shadow_sys_disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 07:39 AM
тАО12-03-2009 07:39 AM
Re: Shadowset Member Problem
$ analyze/disk/shadow sys$sysdevice
to see if your disks are consistent.
See help analyze/disk/shadow for a more detailed description, and the shadowing manual (also you need the manual update from 8.2 new features or the HBMM patch for 7.3-2)
Shadowing is can be useful, but like fire, it can do a lot of damange if it isn't treated with respect. Getting a shadow copy with the wrong master member is non-recoverable (unless you have backups on some other media).