- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Could not find Q_BOOT device
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
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
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-14-2015 06:30 AM
01-14-2015 06:30 AM
Could not find Q_BOOT device
Guys,
two days before I could not believe my eyes - some very old error message rose up from the land of the dead again:
Boot File Name: /opt/ignite/boot/nbp.efi
Boot File Size: 31232
Downloading NBP file...
Succeed to download NBP file.
......
* Preparing to execute init...
======= 01/14/15 09:27:28 EST HP-UX Installation Initialization.
@(#)Ignite-UX Revision C.7.12.519
@(#)ignite/launch (opt) Revision:
/branches/IUX_RA1103/ignite/src@82875 Last Modified: 2011-01-20
21:10:40 +0530 (Thu, 20 Jan 2011)
* Configuring RAM filesystems...
* Scanning system for IO devices...
* Boot device is:
WARNING: Could not find Q_BOOT device. Cannot determine what the boot device
was.
WARNING: Could not find source device in ioscan output. You must select from
the list of devices below to use for the source device:
index HW-path Class description
0) 0/0/0/1/0/0/4 usb HP_UHCI_Virtual_Controller
1) 0/0/0/2/0/0/0 ext_bus PCIe_SAS_SmartArray_P410i_RAID_Controller
2) 0/0/0/2/0/0/0.0x0.0x1000000c0000000 disk HP_EH0300FBQDD
3) 0/0/0/2/0/0/0.0x0.0x1010000c0000000 disk HP_EH0300FBQDD
4) 0/0/0/5/0/0/0 fc HP_451871-B21_8Gb_Dual_Port_PCIe_Fibre_Channel_Mezzanine_(FC_Port_1)
5) 0/0/0/5/0/0/1 fc HP_451871-B21_8Gb_Dual_Port_PCIe_Fibre_Channel_Mezzanine_(FC_Port_2)
6) 0/0/0/29/0 usb Intel_UHCI_Controller
7) 0/0/0/29/1 usb Intel_UHCI_Controller
8) 0/0/0/29/7 usb Intel_EHCI_64-bit_Controller
9) 0/0/0/30/0/4/0 graphics PCI_Display_(1002515e)
10) 0/120 processor Processor
11) 0/122 processor Processor
12) 0/124 processor Processor
13) 0/126 processor Processor
14) 0/128 processor Processor
15) 0/130 processor Processor
16) 0/132 processor Processor
17) 0/134 processor Processor
18) 1/0/0/2/0/0/0 ext_bus PCIe_SAS_SmartArray_P410i_RAID_Controller
19) 1/0/0/5/0/0/0 fc HP_451871-B21_8Gb_Dual_Port_PCIe_Fibre_Channel_Mezzanine_(FC_Port_1)
20) 1/0/0/5/0/0/1 fc HP_451871-B21_8Gb_Dual_Port_PCIe_Fibre_Channel_Mezzanine_(FC_Port_2)
21) 1/120 processor Processor
22) 1/122 processor Processor
23) 1/124 processor Processor
24) 1/126 processor Processor
25) 1/128 processor Processor
26) 1/130 processor Processor
27) 1/132 processor Processor
28) 1/134 processor Processor
29) 64000/0x0/0x0 escsi_ctlr USB_Mass_Storage_Virt_Ctlr
Enter the index corresponding to the device to use
as the installation source, 'r' to rescan, or 'q' to reboot:
Background: I am trying to install the new BL870c i4 machine via Ignite from Ignite_Server C.7.12.519.
The machine nicely communicates via TFTP, it contacts Ignite_Server, downloads install image for 11v3, however, when trying to use associated network card again, it is not able to find it. Rescan of course does not help.
Have anybody of you, guys, have stumbled upon such an issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2015 06:40 AM - edited 01-14-2015 06:47 AM
01-14-2015 06:40 AM - edited 01-14-2015 06:47 AM
Re: Could not find Q_BOOT device
Ignite too old?
https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB
current version is 7.18!
Maybe this can help too:
http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c02793471
What is the OS version do you want to install?
Must be 2012.09 or newer, AFAIR.
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-14-2015 07:20 AM
01-14-2015 07:20 AM
Re: Could not find Q_BOOT device
Hi,
yes, the Ignite is quite old, however I have been trying other troubleshootings around as the Ignite resides on production server :-)
I have checked the advisory earlier - I do not have the problem with DVD. I am trying to install HP-UX 11v3 March2014 release, via the network. One i4 machine has been installed via local virtual DVD mount - it is OK, however, I need to have solved this problem for the future possible restores via Ignite (net_recovery).
Anyway, update of the Ignite is an option. AFAIK the newest version of the Ignite has to be accompanied with PAX-Enh utilities, which I am not yet familiar with....As PAX-Enh deals with ACLs, any thing one has to bear in mind?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2015 07:34 AM - edited 01-14-2015 07:35 AM
01-14-2015 07:34 AM - edited 01-14-2015 07:35 AM
Re: Could not find Q_BOOT device
OK, installation is one point, proove ignite to work is another.
I successfully installed several such blades like this:
Install the first blade and configure, insert another pair of disks in a free blade, create a logical drive and clone the OS via drd clone. This takes around 15 minutes or less. Then take these disks to the next blade, start in single user and and run set_parms initial. Works great. Once done, you could test making an ignite backup of a blade and restore it.
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-14-2015 07:43 AM
01-14-2015 07:43 AM
Re: Could not find Q_BOOT device
Additional advise:
Switch the smart array controller to RAID mode and install the OS onto a logical drive.
Otherwise the disk replacement will be a pain once a disk will fail.
;-)
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-14-2015 08:07 AM
01-14-2015 08:07 AM
Re: Could not find Q_BOOT device
That's a nice trick, thanks ;-) . However I cannot go physically to the DC to do the exchanges of the blades....so I have to remain at "remote admin" place, ya know.
I will try to update Ignite.....
Anyway, I have found the doc which is dealing with pretty the same issue, however in HPVM, when it is caused by too low a memory. Perhaps Ignite, or EFI cannot assign more memory than 2GB during the process. I have investigated the possibility how to specify how much mem should EFI/Ignite use for the client, but I was not able to find....