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: Tue, 1 Feb 2011 14:52:22 -0600 [thread overview]
Message-ID: <1D.26.13137.882784D4@cdptpa-omtalb.mail.rr.com> (raw)
In-Reply-To: <4D487066.2010703@grumpydevil.homelinux.org>
> On 02/01/2011 09:23 PM, Leslie Rhorer wrote:
> > I have been attempting to upgrade a Debian "Squeeze" Linux box from
> > 2.6.32-3-amd64 to 2.6.32-5-amd64, but the upgrade is a non-starter.
> GRUB2
> > comes up just fine, but when I select the new kernel version, a number
> of
> > announcements flash by too fast to seen. I am not 100% certain, but I
> > believe the initrd starts to load OK. Some text flies by far too quickly
> to
> > be seen, but then an error pops up concerning an address space collision
> of
> > some PCI device. Then it shows three errors for RAID devices md1. md2,
> and
> > md3, saying they are already in use. Immediately thereafter the system
> shows
> > errors concerning the RAID targets being already in use, after which
> point
> > the system complains it can't mount / (md2), /dev, /sys, or /proc (in
> that
> > order) because the sources do not exist (if /dev/md2 does not exist, how
> can
> > it be busy?). Thereafter, of course, it fails to find init, since / is
> not
> > mounted. It then tries to run BusyBox, but Busybox complains:
> >
> > /bin/sh: can't access tty; job control turned off
> >
> > After that, it attempts to put up an initramfs prompt, but of course
> with no
> > tty access, it just hangs completely. Not surprisingly, recovery mode
> > 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.
> Cheers
>
> Rudy
> > Obviously there is a problem in the initramfs, probably with mdadm, but
> > what? What should I try to manipulate in the initrd so I can find out
> what
> > is failing?
> >
> > --
> > 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
> >
next prev parent reply other threads:[~2011-02-01 20:52 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 [this message]
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
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=1D.26.13137.882784D4@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).