<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jeremy,<br>
<br>
I had a very similar problem. <br>
<br>
What got me working is for the kernel line add ksdevice=link.<br>
<br>
Cam<br>
<br>
<br>
<div class="moz-cite-prefix">On 22/09/14 04:00 PM, Jeremy Mordkoff
wrote:<br>
</div>
<blockquote cite="mid:1411416012630.82428@riftio.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 09/22/2014 03:08 PM, Alan
Evangelista wrote:<br>
</div>
<blockquote type="cite">On 09/22/2014 03:31 PM, Jeremy Mordkoff
wrote: <br>
<blockquote type="cite"><br>
I have cobbler up and running and I've installed to my first
system at least a dozen times. The first system had two CPUs
and 16 GB RAM.
<br>
<br>
<br>
Now I'm trying a mass deployment. These new systems all have
1 CPU and 8 GB RAM.
<br>
<br>
<br>
The install fails on the new systems. I compared the output
from cobbler system report for the two systems and except for
the obvious differences in names and addressing, everything
else is the same.
<br>
<br>
<br>
It drops down into an emergency shell right after <br>
<br>
Warning: Could not boot <br>
<br>
Warning: /dev/root does not exist <br>
<br>
<br>
</blockquote>
<br>
You can use the same profile for all systems, you just need one
Cobbler system object for each system.
<br>
You must fill network data in each Cobbler system object. <br>
<br>
What Linux distribution are you trying to install? I suppose you
are not providing
<br>
system network setup in kernel options, in which case the
installation kernel will
<br>
use DHCP to setup network. I have already seen this
non-intuitive error message <br>
in RHEL/Fedora installations, its root cause is that DHCP was
unable to get network
<br>
information from DHCP server after netbooting and before
starting OS installation.
<br>
<br>
</blockquote>
Fedora 20<br>
I have a new profile for the new system. <br>
I do believe this is a DHCP issue, but I cannot determine why this
system is behaving differently than the first one. The two are the
same except the second unit does not have the second CPU populated
and it only has 8 GB ram...neither of which I would think would
affect the network. <br>
<br>
DHCP clearly is working because the PXE boot client was able to
get an address. So why can't linux?
<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cobbler mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cobbler@lists.fedorahosted.org">cobbler@lists.fedorahosted.org</a>
<a class="moz-txt-link-freetext" href="https://lists.fedorahosted.org/mailman/listinfo/cobbler">https://lists.fedorahosted.org/mailman/listinfo/cobbler</a>
</pre>
</blockquote>
<br>
</body>
</html>