Memory Class Setup ------------------------------------------------------------------------- Class Physmem Lockmem Swapmem ------------------------------------------------------------------------- System : 7762 MB 7762 MB 7762 MB Kernel : 7762 MB 7762 MB 7762 MB User : 7095 MB 6290 MB 6315 MB -------------------------------------------------------------------------
ktracer is off until requested. Installing Socket Protocol families AF_INET and AF_INET6 Kernel EVM initialized sec_init(): kernel RPC authentication/security initialization. secgss_init(): kernel RPCSEC_GSS security initialization. rpc_init(): kernel RPC initialization. rpcmod_install(): kernel RPC STREAMS module "rpcmod" installation. ...(driver_install) NOTICE: nfs_client_pv3_install(): nfs3 File system was registered at index 11. NOTICE: nfs_client_pv4_install(): nfs4 File system was registered at index 12. NOTICE: USB device attached. Identification String: Devices/Device/USB/Standard/hp/Multibay/0_a1 <2.1.3.10.1008.294.161> NOTICE: USB device attached. Identification String: Devices/MassStorage-SCSI/USB/BulkOnly/hp/Multibay/0_a1 <2.310.3.150.1008.294.161> NOTICE: USB device attached. Identification String: Devices/ScsiControllerAdaptor/USB/BulkOnly/hp/Multibay <2.1000.3.150.1008.294> NOTICE: USB device attached. Identification String: Devices/Device/USB/Standard/hp/Multibay/0_a1 <2.1.3.10.1008.294.161> NOTICE: USB device attached. Identification String: Devices/MassStorage-SCSI/USB/BulkOnly/hp/Multibay/0_a1 <2.310.3.150.1008.294.161> NOTICE: USB device attached. Identification String: Devices/ScsiControllerAdaptor/USB/BulkOnly/hp/Multibay <2.1000.3.150.1008.294> CISS: RAID SA controller on hardware path 0/6/0/0/0/0/4/0/0/0 is now online.
System Console is on the Built-In Serial Interface iether0: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/1/1/0 iether1: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/1/1/1 iether2: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0 iether3: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1 AF_INET socket/streams output daemon running, pid 34 afinet_prelink: module installed Starting the STREAMS daemons-phase 1 Swap device table: (start & size given in 512-byte blocks) entry 0 - auto-configured on root device; ignored - no room WARNING: No swap device configured, so dump cannot be defaulted to primary swap. WARNING: No dump devices are configured. Dump is disabled. Create STCP device files Starting the STREAMS daemons-phase 2 $Revision: vmunix: B.11.31_LR FLAVOR=perf nfsauth: lookupname: 2
The path in question is to 0/0/2 - this is the path to the USB subsystem, and not associated with your P400 RAID card - are you trying to install via vMedia? Maybe you are having network issues?
It is a new machine with no preloaded OS inside. I have already created RAID 1+0 in the P400 Array Configuration. and inside there I can also see the disk.
I'm installing from a typical DVD disk in the rx6600 dvdrom.
Then you may have a flaky DVD, DVD drive, or USB interface - do you have another piece of install media you can try?
Alternatively you could try doing the install thro the vMedia interface on the iLO (with the DVD in your desktop PC) - it will be slower, but might get you going...
I have tried swaping DVDROM, DVD Media, Harddisk, IO Backplane still no result.
I log a case with HP and they said something to do with USB1.1 and USB2.0. They came and install the HP-UX 11i v3 March 2009 and it works.
I question back HP that I have an identical server and it can able me to install HP-UX 11i v3 September 2008 release. They cannot give me an answer. lol
hmmm - are you sure both rx6600s had DVD-ROM drives? Are you sure the one that install failed on didn't have a DVD-RW drive?
The DVD-RW device is I think only a USB2.0 device which requires a USB2.0 stack which only appeard in the 0903 media, whereas the DVD-ROM is not as fussy
OK I just read a couple of internal case reviews which match your problem... basically the problem was a corner case in the USB1.1 driver which resulted in a timing issue. It meant that the problem was seen on only a very small number of USB based installs, and as we completely re-wrote the USB driver for 0903 anyway, the old driver had been obsoleted and the 0809 DVDs had already shipped, the code in the USB1.1 driver wasn't looked at...
There's some indication that some folks managed to get round the problem by re-scanning their hardware at the first Ignite install screen... but my advice would be to stick with 0903 now...
no, I'm just saying that for whatever reason (and I really have no idea - USB cable lengths, tiny differences in cable specs?) one system sees this unfortunate timing issue, and the other doesn't... spec-wise they may be completely identical - are they on the same firmware levels as well?
I've encountered the same problem yesterday on a rx2660 while testing a custom DVD with a Golden Image. The Ignite kernel on that DVD was not the latest available, I think it was the Sept. 2008 version. Updating Ignite to the March 2009 release and recreating the DVD fixed the problem.
Actually, I've finally been able to make it work after all. I got mistaken during my first test but that was because when I upaded Ignite, I only updated the 11.23 IINSTALL kernel and kept 11.31 at the Sept. 2008 release. I fixed it to have a March 2009 11.31 kernel, and it fixed the issue.
So I think this goes along with Duncan's previous post to the effect that this is a bug on the Sept. 2008 11.31 release.
