- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- RX2620 not detecting the tape drive in EFI BOOT MA...
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
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
тАО01-06-2008 10:38 AM
тАО01-06-2008 10:38 AM
RX2620 not detecting the tape drive in EFI BOOT MANAGER
I have two RX2620 connected to a DDS tape drive each. When booting up to the EFI BOOT MANAGER, RX2620 server A could easily enumerate the hardware address to the tape drive as a boot option, but RX2620 server B could not. The surprise is that RX2620 server B could detect its DDS tape drive during early boot prior to the EFI BOOT MANAGER screen and even after the operating system has booted with ioscan -fnC tape.At OS level we could even do a backup to the DDS tape drive.
What could have been wrong ? Please help.
Regards,
Berenger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 10:54 AM
тАО01-06-2008 10:54 AM
Re: RX2620 not detecting the tape drive in EFI BOOT MANAGER
Did you enable stape driver in kernel?
Best Regards
Murat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 10:57 AM
тАО01-06-2008 10:57 AM
Re: RX2620 not detecting the tape drive in EFI BOOT MANAGER
Can you please post the output of map.
rgds
DK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 11:03 AM
тАО01-06-2008 11:03 AM
Re: RX2620 not detecting the tape drive in EFI BOOT MANAGER
Check and compare
MP:CM> sysrev
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2008 01:39 PM
тАО01-06-2008 01:39 PM
Re: RX2620 not detecting the tape drive in EFI BOOT MANAGER
Sorry for my previous stupid response.
hp Integrity rx2620 System 04.10, BMC 04.01, and iLO MP E.03.28 Firmware Release
Added support for Tape Boot on U160 and U320 SCSI cards in combination with the HP-UX 11i v2 0606 Release.
By the way, following url has lates firmware
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=441910&prodTypeId=15351&prodSeriesId=447331&swLang=13&taskId=135&swEnvOID=54#290
System 04.27, BMC 04.04 and iLO MP E.03.30
You can check your firmware release with sysrev in CM menu like Torsten sayed
I hope it helps to you
Best Regards
Murat