From: "Leslie Rhorer" <lrhorer@satx.rr.com>
To: 'Rudy Zijlstra' <rudy@grumpydevil.homelinux.org>
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: RE: Kernel 2.6.32-5-amd64 fails to boot.
Date: Wed, 2 Feb 2011 01:00:34 -0600 [thread overview]
Message-ID: <42.F7.13137.411094D4@cdptpa-omtalb.mail.rr.com> (raw)
In-Reply-To: <4D488D36.2000208@grumpydevil.homelinux.org>
> -----Original Message-----
> From: Rudy Zijlstra [mailto:rudy@grumpydevil.homelinux.org]
> Sent: Tuesday, February 01, 2011 4:46 PM
> To: lrhorer@satx.rr.com
> Cc: 'Linux RAID'
> Subject: Re: Kernel 2.6.32-5-amd64 fails to boot.
>
> On 02/01/2011 10:44 PM, Leslie Rhorer wrote:
> >> -----Original Message-----
> >> From: Rudy Zijlstra [mailto:rudy@grumpydevil.homelinux.org]
> >> Sent: Tuesday, February 01, 2011 3:02 PM
> >> To: lrhorer@satx.rr.com
> >> Cc: 'Linux RAID'
> >> Subject: Re: Kernel 2.6.32-5-amd64 fails to boot.
> >>
> >> On 02/01/2011 09:52 PM, Leslie Rhorer wrote:
> >>
> >>>> On 02/01/2011 09:23 PM, Leslie Rhorer wrote:
> >>>>
> >>>>
> >>>>
> >>>>> doesn't boot, either. It gives a bit more detail in the output, but
> >>>>>
> >>>>>
> >>>> nothing
> >>>>
> >>>>
> >>>>> illuminating. The old kernel (2.6.32-3-amd64) boots just fine.
> >>>>>
> >>>>>
> >>>>>
> >>>> Can you enable serial console and catch the console output that way?
> >>>>
> >>>>
> >>> Well, not easily. I don't have a serial terminal. I suppose I
> >>> could set something up. You're suggesting I poke around to see what
> md
> >>>
> >> is
> >>
> >>> reporting? Also, I'm not sure why - if the keyboard console is
> failing
> >>>
> >> -
> >>
> >>> the serial console would work better.
> >>>
> >>>
> >>>
> >>>
> >> 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.
next prev parent reply other threads:[~2011-02-02 7:00 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 [this message]
2011-02-02 11:00 ` Justin Piszcz
2011-02-02 11:32 ` CoolCold
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=42.F7.13137.411094D4@cdptpa-omtalb.mail.rr.com \
--to=lrhorer@satx.rr.com \
--cc=linux-raid@vger.kernel.org \
--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).