- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: After Virtual Connect configured cannot boot f...
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-12-2007 05:25 AM
тАО12-12-2007 05:25 AM
After Virtual Connect configured cannot boot from SAN.....
hpux 11i v3
Virtual Connect was configured on the blade enclosure.
When I power up the blade it tries the primary boot option but get this message:
Loading.: HP-UX Primary Boot: 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000
Load of HP-UX Primary Boot: 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000 failed: Not Found
Press any key to continue
Same result for the Secondary boot option.
I tried to boot from DVD and when I got to the place where you select the source and language.
It said that "Empty primary boot path reported by setboot: Promary bootpath"
See here:
Enter the index corresponding to the device to use
as the installation source, 'r' to rescan, or 'q' to reboot: 9
You selected: 0/0/2/0.0x0.0x10 disk USB_SCSI_Stack_Adaptor
Is this correct? ([y]/n):
NOTE: Empty primary boot path reported by setboot: Primary bootpath :
NOTE: Primary path not currently set to an existing disk device.
* Setting keyboard language.
Strange thing is, when I boot from the installation DVD and I get to the Install screen sees my 2 disks (LUNs).
Anyone know why this is happening?
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 05:53 AM
тАО12-12-2007 05:53 AM
Re: After Virtual Connect configured cannot boot from SAN.....
Looking at the WWNs above, I'm guessing that your storage is presented by an EVA of some sort, probably an Active/Passive version such as an EVA3000 or EVA5000.
Maybe the primary and secondary boot options are pointing at the passive controller.
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 06:24 AM
тАО12-12-2007 06:24 AM
Re: After Virtual Connect configured cannot boot from SAN.....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 06:28 AM
тАО12-12-2007 06:28 AM
Re: After Virtual Connect configured cannot boot from SAN.....
If it's an EVA4000 then it's Active/Active, so what I said previously probably isn't the problem...
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 06:56 AM
тАО12-12-2007 06:56 AM
Re: After Virtual Connect configured cannot boot from SAN.....
I've found the problem and need help finding a solution:
EFI has a primary boot path of 0/4/0/0/0/1.0x50001fe1500b0bbd.0x4001000000000000
I went into the installation process to have a look at what the server can see and now see that it currently sees 2 disks:
0/3/0/0/0/0.0x50001fe1500b0bbc.0x4001000000000000
0/3/0/0/0/0.0x50001fe1500b0bb8.0x4001000000000000
It used to connect through HBA2 cabled to the switch but now with Virtual Connect it connects through the first HBA (just on a different mezzanine in the blade).
How can I change the EFI primary boot path?