- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: OVMS 8.4 PKB0 device error
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
04-05-2011 02:20 AM
04-05-2011 02:20 AM
OVMS 8.4 PKB0 device error
There is half tape blade in enclosure and on its right side there is one full blade BL860.
while booting OVMS we are observing message ,
%PKB0, pkm$map_mr: map register allocation failed!
%PKB0, pkm$initializing: pkm$map failed!
%PKB0, Failed to initialize port
And after booting we found that PKB0 is showing offline status.
As like name in Alpha system it should indicate Tape device as MKA or MKB or MKC or MKF etc. but it gives
message no such device availabe on $show device mk.
Tape blade checked with other slot with other BL860---it is getting detected on controller PKB0 and showing online status
$show dev PKB0 -----online
but on issuing commnad $show dev mk it says no such device available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-06-2011 12:23 AM
04-06-2011 12:23 AM
Re: OVMS 8.4 PKB0 device error
Have you tried moving the tape blade and swapping the server blades over, so that the blade that can't see PKB is in the slot where the blade could see it? If that works, I'd be starting to look for a hardware fault on the blade enclosure.
If it still doesn't work and you still get the errors, that might point to a blade hardware fault, a firmware fault, config issue etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-06-2011 12:50 AM
04-06-2011 12:50 AM
Re: OVMS 8.4 PKB0 device error
You should get a better response than from posting to this fine forum.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-06-2011 10:39 AM
04-06-2011 10:39 AM
Re: OVMS 8.4 PKB0 device error
The blade must have the passthru card installed in mezzanine #3
Tape devices show up as $2$MGA devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-21-2011 02:59 PM
09-21-2011 02:59 PM
Re: OVMS 8.4 PKB0 device error
Try update 5; I just went through the exact same thing and as soon as I got update 5 loaded, the error went away.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP