- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- HSD30 mirrorset questions - OpenVMS errors and siz...
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
тАО07-07-2009 08:25 AM
тАО07-07-2009 08:25 AM
Question 1 - is there an easy way to determine which mirror set member was causing OpenVMS to report disk errors?
Question 2 - OpenVMS still shows the capacity of the disk as 2GB. From the controller the capacity of the mirror set is 2GB but each member shows as 4GB. How can I get the mirror set and OpenVMS to show 4GB. This is a 24x7 cluster so I'm looking for a way to do it without affecting the cluster operation; possibly restarting each controller (redundant pair) and then running analyze/disk on the cluster.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 09:13 AM
тАО07-07-2009 09:13 AM
SolutionQuestion 1 - The disk errors would have been logged in SYS$ERRORLOG:ERRLOG.SYS on the host. Use DECEvent or WSEA to analyze the error log from VMS.
On the HSD30 you can run FRU and SHOW LAST_FAILURE command to find the disk errors.
Question 2 - DO image backup the DUA device and dismount. On the HSD30 delete the unit, then delete the mirrorset, init the member drives and then create a new mirrorset and unit. Restore image backup to the "new" 4GB DUA device.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 09:32 AM
тАО07-07-2009 09:32 AM
Re: HSD30 mirrorset questions - OpenVMS errors and size
Sorry, I should have said the customer does not have DECEvent installed. They need something that may identify it in anal/error.
Russ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 09:50 AM
тАО07-07-2009 09:50 AM
Re: HSD30 mirrorset questions - OpenVMS errors and size
They'd have to install DECevent or move the error log to another system that can analyze it.
Probably much easier/faster to just use the FRU utility on the HSD30.
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 09:53 AM
тАО07-07-2009 09:53 AM
Re: HSD30 mirrorset questions - OpenVMS errors and size
Been trying FRU but don't seem to see anything relating to the device. I'll try it again after the next "error" ocurs.
Russ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 11:47 AM
тАО07-07-2009 11:47 AM
Re: HSD30 mirrorset questions - OpenVMS errors and size
Just realized I had a finger or a brain fault in my earlier posts. I meant to say use the FMU (Fault Management Utility) not FRUTIL (Field Replacement Utility).
Sorry about that. Sometimes you get what you pay for and then sometimes you don't ;)
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2009 03:48 PM
тАО07-07-2009 03:48 PM
Re: HSD30 mirrorset questions - OpenVMS errors and size
Don't feel bad, I can't type. I meant FMU,not FRU.
Russ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2009 04:17 AM
тАО07-09-2009 04:17 AM