Re: Kernel 2.6.32-5-amd64 fails to boot.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 2, 2011 at 2:00 PM, Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> 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@xxxxxxxxx/eth0,514@xxxxxxxxx/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@xxxxxxxxxx/eth0,514@xxxxxxxx/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@xxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux