<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-forward-container">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I don't like replying to my own
email, but this issue is closed for me and an FYI to the next
newbie seem relevant...<br>
<br>
<br>
On 02/15/2013 08:20 PM, George VerDuin wrote:<br>
</div>
<blockquote cite="mid:511EDEF4.2050600@yahoo.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
<div class="moz-forward-container">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Greetings<br>
<br>
As a newbie I have reached the point of bombing out with my
first client. In FAI-Guide my failure is listed under section
5.7.1 as:<br>
<blockquote>Begin: Mounting root file system... ... <br>
Kernel panic - not syncing: Attempted to kill init!<br>
</blockquote>
with the suggestion "Check initrd ... for a missing driver."
[I paraphrased]. </div>
</blockquote>
The missing driver was a red herring, and a poor choice of debug
path on my part. The time spent in searching produced no result.
The real fix was:<br>
<ol>
<li>re-run fai-setup after installing an appropriate
/etc/fai/apt/sources.list. My reluctance to run setup again
cost considerable time repeating make-fai-nfsroot on the old
sources that were not OK. For my sanity, answering the
question: "WHEN to re-run setup" has gone up the priority
list.<br>
</li>
<li>manually edit /src/tftp/fai/pxelinux.cfg/C... after
switching from the "...default-pae" to the "...default"
version of the kernel. I'm sad to have not noticed this
detail while watching the fai client boot. Perhaps I should
have used "fai-chboot".<br>
</li>
<li>chmod go+r /srv/tftp/fai/vmlinuz... because tftpd was not
serving "root owned and not readable by others" files.
Perhaps it was given incorrect permissions by
make-fai-nfsroot? Or I run fai stuff as the wrong user?<br>
</li>
</ol>
Perhaps the most egregious error of mine was to not repair
make-fai-nfsroot completely prior to attempting to boot the fai
client for the first time. Impatient me... I've made so many
little changes since jan 24 that I now can't sort out the actual
single fix that would have avoided the panic.<br>
<br>
Cheers<br>
Geo<br>
<br>
</div>
<br>
</body>
</html>