On Tue, Aug 27, 2013 at 02:26:25PM -0700, Roderick A. Anderson wrote:
> On 08/27/2013 01:32 PM, Herbert Poetzl wrote:
>> On Tue, Aug 27, 2013 at 09:31:41PM +0200, Roman Pretory wrote:
>>> the same error after a fresh installed und updated system
>>> (Centos 6.4) without LVM.
>> And do you have a boot log to share with us? :)
> Does anyone have suggestions for the linux semi-admin on how
> to get CentOS to append to the boot.log file instead of
> overwrite it?
> I am having no success finding anything on how to do this.
I'm pretty sure that the boot.log is written when the
kernel has successfully started init and some script or
process on the root filesystem contacts the kernel and
copies the dmesg data to that file.
So in the case where the boot panics before init is
started (and has a working rootfs) no boot.log will be
written at all.
Nevertheless, there are some methods to get that boot
log from the initramfs, but it might need a few dirty
tricks or hacks :)
>>> -----Ursprüngliche Nachricht-----
>>> Von:Roderick A. Anderson<email@example.com>
>>> Gesendet:Di 27.08.2013 19:55
>>> Betreff:Re: AW: [vserver] Kernel panic - not syncing
>>> On 08/27/2013 10:33 AM, Roman Pretory wrote:
>>>> I have the same trouble.
>>>> I upgraded a centos 6.3 to 6.4 all latest
>>>> than I make that Kernelupdate and get the same msg.
>>>> the same with kernel-2.6.32-358.11.1.el6.vs22.214.171.124.29.6.31.x86_64.rpm
>>> Interesting! I have a CentOS 6.3 system that is working just fine. I
>>> will compare the two base systems, besides the kernel, looking for
>>> Thanks for the insight.
>>>> I buy now a ssd and set up a complete new system, ...
>>>> and if all wast, I have a old sync vom this repro with a working kernel.
>>>> -----Ursprüngliche Nachricht-----
>>>> *Von:* Roderick A. Anderson<firstname.lastname@example.org>
>>>> *Gesendet:* Mo 26.08.2013 20:26
>>>> *Betreff:* Re: [vserver] Kernel panic - not syncing
>>>> *An:* email@example.com;
>>>> On 08/24/2013 09:07 AM, Sergiusz Pawlowicz wrote:
>>>>> On Sat, Aug 24, 2013 at 5:00 PM, Herbert
>>>> Poetzl<firstname.lastname@example.org> wrote:
>>>>>> - bad initramfs (old initrd tools)
>>>>>> - driver for rootdev/rootfs missing
>>>>>> - device names changed (hda -> sda)
>>>>>> - incompatible hardware
>>>>> - lack of linux administrator
>>>> They have one but for $120/month what can you expect (I am mostly
>>>> retired and they provide me internet access and colo for a server).
>>>> Beside nearly every time I've build/re-built a LV system there have
>>>> no problems. I've got lazy about keeping up on changes at the system
>>>> level. I mostly use Linux now.
Received on Tue Aug 27 23:17:25 2013