Hello ,
I’m trying to install SLES11 SP3 in Moonshot platform m300 catridge. But PXE installation fails with error code “Could not find the SUSE Linux Enterprise Server 11 Repository”
I have followed the procedure mentioned below , but i feel that it still fails to load n/w driver.
Installation procedure : http://drivers.suse.com/hp/HP-ProLiant-Moonshot/m300/sle-11-sp3-x86_64/1.0/install-readme.html
-Suresh
Hi Suresh,
how have you configured the client’s network parameters - via DHCP? Can you confirm that the installation source server is reachable under the given “name” by the client - if you specified a server DNS name, does your PXE client resolve the name?
You might want to monitor ICMP reachability of your PXE client during boot - i.e. by pinging it.
How do you try to access the installation media, via HTTP? Can you verify from the server logs that at least a connection attempt was made?
Regards,
Jens
Hi Jens,
Yes, i’m using DHCP for network communication and http for file access.
Here my PXE configuration looks good, as the server is a able to boot using the ISO image,but i’m getting while trying to access the install media which happen after completing the initial boot.
-Suresh
Hi Suresh,
[QUOTE=sureshpanicker;19441]Hi Jens,
Yes, i’m using DHCP for network communication and http for file access.
Here my PXE configuration looks good, as the server is a able to boot using the ISO image,but i’m getting while trying to access the install media which happen after completing the initial boot.
-Suresh[/QUOTE]
ah, ok, now I understand. I haven’t had to deal with that hardware yet, so I don’t know what to look for exactly - but you might want to check the installation logs (under /var/log/YaST2, i.e. y2log) for hints on the driver configuration. Another thing to check is whether (driver) RPMs form that extra disk are actually installed and which driver is being used (if at all) by your network interface.
Regards,
Jens
Thanks a lot Jens for your quick response,
Is there any way to load n/w driver manually during PXE boot if we could attach an iso image to ILO ?
-Suresh
Hi Suresh,
Is there any way to load n/w driver manually during PXE boot if we could attach an iso image to ILO ?
we’ve been using PXE for autoyast installations, where we could run our own scripts to handle additional installation tasks. You would not even need ILO, as you could simply put the files onto the (http) server and transfer them using standard autoyast mechanisms.
Regards,
Jens
sureshpanicker Wrote in message:
[color=blue]
Yes, i’m using DHCP for network communication and http for file access.
Here my PXE configuration looks good, as the server is a able to boot
using the ISO image,but i’m getting while trying to access the install
media which happen after completing the initial boot.[/color]
Given the error I’m thinking the network driver is loading but
possibly the NIC/switchport isn’t initialising - try adding
“netwait=30” (or 60) to your pxelinux.cfg file.
Simon
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://www.piaohong.tk/newsgroup
Hello Simon,
i tried that option, still its showing the error, i tried to continue by accepting that error and selected, options manually. unfortunately that also ended with error “No n/w module loaded”
-Suresh
[QUOTE=sureshpanicker;19435]Hello ,
I’m trying to install SLES11 SP3 in Moonshot platform m300 catridge. But PXE installation fails with error code “Could not find the SUSE Linux Enterprise Server 11 Repository”
I have followed the procedure mentioned below , but i feel that it still fails to load n/w driver.
Installation procedure : http://drivers.suse.com/hp/HP-ProLiant-Moonshot/m300/sle-11-sp3-x86_64/1.0/install-readme.html
-Suresh[/QUOTE]
Hi Suresh
HP-Proliant-Moonshot m300 requires the use of a kISO which includes the correct NIC drivers for SLES 11 SP3 installation.
This is available at http://drivers.suse.com/hp/HP-ProLiant-Moonshot/m300/sle-11-sp3-x86_64/1.0/
HereÂs PXE configuration entry which demonstrates using the kISO:
label SLES-11-SP3-^kISO-x86_64-Gemini
kernel SLES-11-SP3-x86_64/kISO-m300/linux
append initrd=SLES-11-SP3-x86_64/kISO-m300/initrd install=http://YourServerAddress/SLES-11-SP3-x86_64/disc1 console=ttyS0,9600 autoyast=http://YourServerAddress/answers/SLES11-SP2-x86_64_Atom.xml addon=http://YourServerAddress/kISO-m300_SLES-11-SP3-x86_64/disc1
HereÂs the addon parameter points to an HTTP-accessible extracted copy of the kISO file.
HP
Hello,
I have gone through this steps , but still i’m facing same trouble.
I have opened a HPRC case and shared all requested logs to them , waiting for an update.
-Suresh
Hello All,
This issue has been resolved by using an initrd file which is shared by HPRC team.
Thanks to all for your great assistance in this topic.
-Suresh