linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CoolCold <coolthecold@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Leslie Rhorer <lrhorer@satx.rr.com>,
	Rudy Zijlstra <rudy@grumpydevil.homelinux.org>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Kernel 2.6.32-5-amd64 fails to boot.
Date: Wed, 2 Feb 2011 14:32:05 +0300	[thread overview]
Message-ID: <AANLkTimaz7epg+u9cKAYm_LB-jJn0YyU5hRZvdNHFVS1@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102020557270.21703@p34.internal.lan>

On Wed, Feb 2, 2011 at 2:00 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
> On Wed, 2 Feb 2011, Leslie Rhorer wrote:
>
>>>>> Serial console can be captured to a file and then the output analysed.
>>>>> So you can read afterwards the messages that are flying past.
>>>>>
>>>>> What i do in such case, is that i take serial connector from a laptop,
>>>>> and run a terminal emulater like minicom. And capture it to a file so i
>>>>> can analyse what has been happening.
>>>>>
>>>>        Yeah, I don't think there is anything pertinent prior to the md
>>>> failures, but it might be worth a shot.  I don't have a laptop, but I do
>>>> have another server sitting right below the one in question.  The main
>>>> problem is, neither one has a serial port.
>>>>
>>>>
>>> Network console? I could tell you how to setup serial console, but i've
>>> never done the network console
>>
>>        Me either.  I tired to do a Google search, but I think the words
>> "network", "console", and "boot" are too common to return practical
>> results,
>> even when combined with "initrd".  I waded through a ton of results, but
>> couldn't find a tutorial on how to enable a network console in the initrd.
>
> Hi,
>
> Check the network console documentation in the kernel.  Essentially, in
> LILO, run:
>
> append="netconsole=4444@192.0.0.1/eth0,514@192.0.0.2/00:60:2D:CD:2A:B7"
>                             ^^ src                  ^^dest / ^dest mac addr
>
> On the remote host, run syslogd -r (to accespt remote syslogging)
>
> This *is* clearly documented here in the kernel docs:
> linux/Documentation/networking/netconsole.txt
>
> Re:
>
> It takes a string configuration parameter "netconsole" in the
> following format:
>
>  netconsole=[src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr]
>
>   where
>        src-port      source for UDP packets (defaults to 6665)
>        src-ip        source IP to use (interface address)
>        dev           network interface (eth0)
>        tgt-port      port for logging agent (6666)
>        tgt-ip        IP address for logging agent
>        tgt-macaddr   ethernet MAC address for logging agent (broadcast)
>
> Examples:
>
> Justin.
As for me, when i've tryed to use netconsole on debian, i've needed to
add such lines into /etc/initramfs-tools/modules
8139too
8139cp
netconsole netconsole=4444@87.118.x.y/eth0,514@95.x.x.x/00:18:74:z:z:z

and do "update-initramfs -u -k `uname -r`" then
where 8139too are my NIC modules - can be obtained with lspci -k and
00:18:74:z:z:z was mac of the gateway. Worked on .18, but not on .32
kernel, though..

> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-02-02 11:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 20:23 Kernel 2.6.32-5-amd64 fails to boot Leslie Rhorer
2011-02-01 20:43 ` Rudy Zijlstra
2011-02-01 20:52   ` Leslie Rhorer
2011-02-01 21:02     ` Rudy Zijlstra
2011-02-01 21:44       ` Leslie Rhorer
2011-02-01 22:46         ` Rudy Zijlstra
2011-02-02  7:00           ` Leslie Rhorer
2011-02-02 11:00             ` Justin Piszcz
2011-02-02 11:32               ` CoolCold [this message]
2011-02-02 17:00               ` Leslie Rhorer
2011-02-02 20:20 ` Leslie Rhorer
2011-02-03  3:27   ` Leslie Rhorer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimaz7epg+u9cKAYm_LB-jJn0YyU5hRZvdNHFVS1@mail.gmail.com \
    --to=coolthecold@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    --cc=rudy@grumpydevil.homelinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).