HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Errors when installing a golden image using ignite
Operating System - HP-UX
1832978
Members
3113
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-21-2009 05:50 AM
01-21-2009 05:50 AM
Hi
We have a rx6600 server image which I'm trying to clone onto a new rx6600 ( recently brought hardware ) server. I have managed to start the ignite installation.. the clonig finishes... and when the server tries to reboot it fails with the following messages
gio: Error configuring root device using EFI hw paths
.
.
PERFMON: Unrecognized Itanium-? processor model [0x0000000000000020, 0x0000000000000001]!
.
.
System Panic:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000e89420 vfs_mountroot+0x1d0
0xe00000000123bd00 im_mountroot+0x60
0xe000000001674a10 DoCalllist+0x3a0
End of Stack Trace
linkstamp: Fri May 25 14:12:06 BST 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
I've seen some threads on the forum, however since the hardware I'm trying to clone is identical I do not understand why the cloning is complaining.
Thanks in advance for all your advice.
Regards
Kaushik
Complete Error messages below
==============================
(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.029
Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 131041 MB
loading section 0
........................................................... (complete)
loading section 1
..................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
..............
Launching /stand/vmunix
SIZE: Text:29805K + Data:10455K + BSS:17865K = Total:58126K
Console is on a Serial Device
Booting kernel...
Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 131041 MB 131041 MB 131041 MB
Kernel : 131041 MB 131041 MB 131041 MB
User : 125314 MB 109219 MB 109647 MB
-------------------------------------------------------------------------
Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_1
<2.1.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/hp/Unknown/0_1
<2.306.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Mouse/USB/hp/Unknown/0_1
<2.307.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Silitek/Keyboard/1_0
<2.1.3.1147.17.256>
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/Silitek/Keyboard/1_0
<2.306.3.1147.17.256>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_a1
<2.1.3.1008.294.161>
NOTICE: USB device attached. Identification String:
Devices/BulkScsiProtocol/USB/hp/Unknown/0_a1
<2.310.3.1008.294.161>
gio: Error configuring root device using EFI hw paths
System Console is on the Built-In Serial Interface
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
PCalling function e0000000010b8a60 for Shutdown State 8 type 0x2
Stored message buffer up to panic:
Pinned PDK malloc pool: base: 0xe000000101bab000 size=233812K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.
MFS is defined: base= 0xe000000101bab000 size= 1392 KB
Unpinned PDK malloc pool: base: 0xe000000110000000 size=1835008K
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
0 sba
0/0 lba
0/0/1/0 rmp3f01
0/0/1/1 rmp3f01
0/0/1/2 asio0
0/0/2/0 UsbOhci
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_1
<2.1.3.1008.4390.1>
0/0/2/0.0 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/hp/Unknown/0_1
<2.306.3.1008.4390.1>
0/0/2/0.0.0 UsbBootKeyboard
NOTICE: USB device attached. Identification String:
Devices/Mouse/USB/hp/Unknown/0_1
<2.307.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Silitek/Keyboard/1_0
<2.1.3.1147.17.256>
0/0/2/0.2 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/Silitek/Keyboard/1_0
<2.306.3.1147.17.256>
0/0/2/0.2.0 UsbBootKeyboard
0/0/2/1 UsbOhci
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_a1
<2.1.3.1008.294.161>
0/0/2/1.0 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BulkScsiProtocol/USB/hp/Unknown/0_a1
<2.310.3.1008.294.161>
0/0/2/1.0.0 UsbBulkOnlyMS
0/0/2/1.0.16 UsbScsiAdaptor
0/0/2/1.0.16.0 tgt
0/0/2/1.0.16.0.0 sdisk
0/0/2/1.0.16.7 tgt
0/0/2/1.0.16.7.0 sctl
0/0/2/2 UsbEhci
0/1 lba
0/2 lba
0/3 gh2p
0/3/0/0 PCItoPCI
0/4 lba
0/4/2/0 iether
0/4/2/1 iether
0/5 lba
0/6 gh2p
0/6/0/0 PCItoPCI
0/6/0/0/0/0 PCItoPCI
0/6/0/0/0/0/2/0 PCItoPCI
0/6/0/0/0/0/4/0 PCItoPCI
0/7 gh2p
0/7/0/0 PCItoPCI
120 processor
121 processor
122 processor
123 processor
124 processor
125 processor
126 processor
127 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
gio: Error configuring root device using EFI hw paths
System Console is on the Built-In Serial Interface
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
PERFMON: Unrecognized Itanium-? processor model [0x0000000000000020, 0x0000000000000001]!
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (BDRA).
WARNING: SWAP device 0xfffffffe is a non-LVM partition, disallowed on LVM disk.
WARNING: SWAP device 0xfffffffe has been deconfigured (set to 0xffffffff).
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend
System Panic:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000e89420 vfs_mountroot+0x1d0
0xe00000000123bd00 im_mountroot+0x60
0xe000000001674a10 DoCalllist+0x3a0
End of Stack Trace
linkstamp: Fri May 25 14:12:06 BST 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.
ERROR: No dump space is configured. Physical memory will not be dumped.
ERROR: Configured dump space is insufficient to hold dump metadata.
Physical memory will not be dumped.
We have a rx6600 server image which I'm trying to clone onto a new rx6600 ( recently brought hardware ) server. I have managed to start the ignite installation.. the clonig finishes... and when the server tries to reboot it fails with the following messages
gio: Error configuring root device using EFI hw paths
.
.
PERFMON: Unrecognized Itanium-? processor model [0x0000000000000020, 0x0000000000000001]!
.
.
System Panic:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000e89420 vfs_mountroot+0x1d0
0xe00000000123bd00 im_mountroot+0x60
0xe000000001674a10 DoCalllist+0x3a0
End of Stack Trace
linkstamp: Fri May 25 14:12:06 BST 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
I've seen some threads on the forum, however since the hardware I'm trying to clone is identical I do not understand why the cloning is complaining.
Thanks in advance for all your advice.
Regards
Kaushik
Complete Error messages below
==============================
(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.029
Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 131041 MB
loading section 0
........................................................... (complete)
loading section 1
..................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
..............
Launching /stand/vmunix
SIZE: Text:29805K + Data:10455K + BSS:17865K = Total:58126K
Console is on a Serial Device
Booting kernel...
Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 131041 MB 131041 MB 131041 MB
Kernel : 131041 MB 131041 MB 131041 MB
User : 125314 MB 109219 MB 109647 MB
-------------------------------------------------------------------------
Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_1
<2.1.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/hp/Unknown/0_1
<2.306.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Mouse/USB/hp/Unknown/0_1
<2.307.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Silitek/Keyboard/1_0
<2.1.3.1147.17.256>
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/Silitek/Keyboard/1_0
<2.306.3.1147.17.256>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_a1
<2.1.3.1008.294.161>
NOTICE: USB device attached. Identification String:
Devices/BulkScsiProtocol/USB/hp/Unknown/0_a1
<2.310.3.1008.294.161>
gio: Error configuring root device using EFI hw paths
System Console is on the Built-In Serial Interface
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
PCalling function e0000000010b8a60 for Shutdown State 8 type 0x2
Stored message buffer up to panic:
Pinned PDK malloc pool: base: 0xe000000101bab000 size=233812K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.
MFS is defined: base= 0xe000000101bab000 size= 1392 KB
Unpinned PDK malloc pool: base: 0xe000000110000000 size=1835008K
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
0 sba
0/0 lba
0/0/1/0 rmp3f01
0/0/1/1 rmp3f01
0/0/1/2 asio0
0/0/2/0 UsbOhci
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_1
<2.1.3.1008.4390.1>
0/0/2/0.0 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/hp/Unknown/0_1
<2.306.3.1008.4390.1>
0/0/2/0.0.0 UsbBootKeyboard
NOTICE: USB device attached. Identification String:
Devices/Mouse/USB/hp/Unknown/0_1
<2.307.3.1008.4390.1>
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Silitek/Keyboard/1_0
<2.1.3.1147.17.256>
0/0/2/0.2 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BootKeyboard/USB/Silitek/Keyboard/1_0
<2.306.3.1147.17.256>
0/0/2/0.2.0 UsbBootKeyboard
0/0/2/1 UsbOhci
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_a1
<2.1.3.1008.294.161>
0/0/2/1.0 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/BulkScsiProtocol/USB/hp/Unknown/0_a1
<2.310.3.1008.294.161>
0/0/2/1.0.0 UsbBulkOnlyMS
0/0/2/1.0.16 UsbScsiAdaptor
0/0/2/1.0.16.0 tgt
0/0/2/1.0.16.0.0 sdisk
0/0/2/1.0.16.7 tgt
0/0/2/1.0.16.7.0 sctl
0/0/2/2 UsbEhci
0/1 lba
0/2 lba
0/3 gh2p
0/3/0/0 PCItoPCI
0/4 lba
0/4/2/0 iether
0/4/2/1 iether
0/5 lba
0/6 gh2p
0/6/0/0 PCItoPCI
0/6/0/0/0/0 PCItoPCI
0/6/0/0/0/0/2/0 PCItoPCI
0/6/0/0/0/0/4/0 PCItoPCI
0/7 gh2p
0/7/0/0 PCItoPCI
120 processor
121 processor
122 processor
123 processor
124 processor
125 processor
126 processor
127 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
gio: Error configuring root device using EFI hw paths
System Console is on the Built-In Serial Interface
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
PERFMON: Unrecognized Itanium-? processor model [0x0000000000000020, 0x0000000000000001]!
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (BDRA).
WARNING: SWAP device 0xfffffffe is a non-LVM partition, disallowed on LVM disk.
WARNING: SWAP device 0xfffffffe has been deconfigured (set to 0xffffffff).
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend
System Panic:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000e89420 vfs_mountroot+0x1d0
0xe00000000123bd00 im_mountroot+0x60
0xe000000001674a10 DoCalllist+0x3a0
End of Stack Trace
linkstamp: Fri May 25 14:12:06 BST 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.
ERROR: No dump space is configured. Physical memory will not be dumped.
ERROR: Configured dump space is insufficient to hold dump metadata.
Physical memory will not be dumped.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2009 05:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2009 06:46 AM
01-21-2009 06:46 AM
Re: Errors when installing a golden image using ignite
Shalom,
Since the systems are essentially identical, I would rule out a hardware difference causing the problem.
The image itself could be bad. Do you have a different image you can test.
Disk configuration could be different. Is their an opportunity to go into the Ignite interface and modify disk configuration?
SEP
Since the systems are essentially identical, I would rule out a hardware difference causing the problem.
The image itself could be bad. Do you have a different image you can test.
Disk configuration could be different. Is their an opportunity to go into the Ignite interface and modify disk configuration?
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2009 05:57 AM
05-08-2009 05:57 AM
Re: Errors when installing a golden image using ignite
We had to rebuild it using the UNIX CDs.
For some reason, the firmware on the machine did not like the ignite image.
Thanks for all your valuable suggestions.
Regards
Kaushik
For some reason, the firmware on the machine did not like the ignite image.
Thanks for all your valuable suggestions.
Regards
Kaushik
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP