However the hosts never boot and hang on a kernel panic with a message of
RAMDISK: incomplete write (16777216 != 67108864)
VFS: Cannot open root device "(null}" or unknown-block(253,0)
Please append a correcnt "root=" boot option; here are the available
partitions
Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown-block(253,
…
Clearly I changed something that I did not mean to but I am not sure what
would cause this to suddenly occur, especially with a system that has built
before.
I have this issue on occasion if I change/modify the netboot kernel that sits in /tftpboot (or your equivalent directory). Try moving the kernel image files (usually in /tftpboot/boot) to tmp or something and try a clean build again.
···
From: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] On Behalf Of Terrence Martin
Sent: Friday, January 09, 2015 2:47 PM
To: foreman-users@googlegroups.com
Subject: [foreman-users] Kernel Panic on Kickstart, Please append a correct "root="
So I seem to have another broken part of foreman.
It may or may not be related, though I was able to successfully build hosts yesterday with foreman 1.7.0.
This morning I updated to foreman 1.7.1.
I then attempted to build a few new hosts via PXE.
However the hosts never boot and hang on a kernel panic with a message of
RAMDISK: incomplete write (16777216 != 67108864)
VFS: Cannot open root device “(null}” or unknown-block(253,0)
Please append a correcnt “root=” boot option; here are the available partitions
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(253,
…
Clearly I changed something that I did not mean to but I am not sure what would cause this to suddenly occur, especially with a system that has built before.
[1529] root@t2gw03 /var/lib/tftpboot/boot# l
total 38056
-rw-r–r--. 1 foreman-proxy foreman-proxy 34815427 Oct 24 07:12
CentOS-6.5-x86_64-initrd.img
-rw-r–r--. 1 foreman-proxy foreman-proxy 4152336 Oct 24 07:12
CentOS-6.5-x86_64-vmlinuz
[1529] root@t2gw03 /var/lib/tftpboot/boot#
As you can see they have not changed since October.
I did not build them per se, and to be honest, I am not sure what ended up
putting those there since I do not recall fiddling on October on those
files.
I will copy over a new updated kernel and see if that works any better.
Thanks,
Terrence
···
On Friday, January 9, 2015 at 3:09:49 PM UTC-8, adavis wrote:
>
> Hey Terrence,
>
>
>
> I have this issue on occasion if I change/modify the netboot kernel that
> sits in /tftpboot (or your equivalent directory). Try moving the kernel
> image files (usually in /tftpboot/boot) to tmp or something and try a clean
> build again.
>
>
>
>
>
> *Ashton Davis*, Senior Infrastructure Engineer
>
> ada...@ntent.com I (w) 760.930.7690 I (c) 619.512.3517
> I www.ntent.com
>
>
>
>
>
>
>
>
>
>
>
> *From:* forema...@googlegroups.com [mailto:
> forema...@googlegroups.com ] *On Behalf Of *Terrence Martin
> *Sent:* Friday, January 09, 2015 2:47 PM
> *To:* forema...@googlegroups.com
> *Subject:* [foreman-users] Kernel Panic on Kickstart, Please append a
> correct "root="
>
>
>
> So I seem to have another broken part of foreman.
>
> It may or may not be related, though I was able to successfully build
> hosts yesterday with foreman 1.7.0.
>
> This morning I updated to foreman 1.7.1.
>
> I then attempted to build a few new hosts via PXE.
>
> CentOS 6.5
> Default Kickstart (modified to install puppet 3.5.1)
> Kickstart default PXELinux
>
> However the hosts never boot and hang on a kernel panic with a message of
>
> RAMDISK: incomplete write (16777216 != 67108864)
> VFS: Cannot open root device "(null}" or unknown-block(253,0)
> Please append a correcnt "root=" boot option; here are the available
> partitions
> Kernel Panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(253,
> ...
>
>
> Clearly I changed something that I did not mean to but I am not sure what
> would cause this to suddenly occur, especially with a system that has built
> before.
>
> Terrence
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-user...@googlegroups.com .
> To post to this group, send email to forema...@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
Ok I grabbed the files from the latest CentOS and it seems to have done the
trick. Not sure what happened to the other files, they are different though
so maybe something happened during the foreman upgrade?
I could have been clearer, I apologize - I meant when a config changes in Foreman that would prompt it to try to redownload the kernel. If the kernel is different at source than it is locally, it can/will hose the local image.
···
From: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] On Behalf Of Terrence Martin
Sent: Friday, January 09, 2015 4:02 PM
To: foreman-users@googlegroups.com
Subject: Re: [foreman-users] Kernel Panic on Kickstart, Please append a correct "root="
Ok I grabbed the files from the latest CentOS and it seems to have done the trick. Not sure what happened to the other files, they are different though so maybe something happened during the foreman upgrade?
Thought I'd expand on this so people know what happens (Ashton is pretty
much correct, but there's some nuance). The Foreman UI will send a message
to the TFTP Proxy whenever a host is put in build mode to ensure the
kernel/initrd is present on the tftp server. That instruction is acted upon
by calling out to "wget -c", which will normally ignore an attempt to
download a file which is already present on the filesystem. However, in the
specific case of (a) the mirror supporting resuming partial downloads and
(b) the file on the mirror being bigger than the file on the disk, wget
will assume it's a partial download and get the remaing portion. Of course,
if it's bigger because there's a new point release of the file, that's
going to end in corruption.
TL;DR - you can mostly ignore the downloading behaviour, but if you get
weirdness, delete the files on the tftp server and toggle the build status
of your host to trigger a new download.
Greg
···
On 13 January 2015 at 18:58, Ashton Davis wrote:
I could have been clearer, I apologize - I meant when a config changes
in Foreman that would prompt it to try to redownload the kernel. If the
kernel is different at source than it is locally, it can/will hose the
local image.
