From: Jon Smirl <jonsmirl@gmail.com>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: current linus bk, error mounting root
Date: Thu, 10 Mar 2005 09:58:10 -0500 [thread overview]
Message-ID: <9e4733910503100658ff440e3@mail.gmail.com> (raw)
In-Reply-To: <20050310075049.GA30243@suse.de>
LABEL=/ / ext3 defaults 1 1
label / is on /dev/sda6
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2
This is what is left on the screen when the boot fails. There is a
another line about failed to mount root machine halted.
I am still broken with using the Linus bk tree as of when I wrote this
mail. That should be all of bk6 plus anything that came in this
morning.
On Thu, 10 Mar 2005 08:50:53 +0100, Jens Axboe <axboe@suse.de> wrote:
> On Wed, Mar 09 2005, Jon Smirl wrote:
> > On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <axboe@suse.de> wrote:
> > > probably not worth the bother, looks like barrier problems. get the
> > > serial console running instead and send the full output, I'll take a
> > > look in the morning.
> >
> > serial console boot output attached.
>
> Hmm ok, nothing of interest there. What does the mount error 6 and 2
> from your original mail mean? I need some more info on what fails
> specifically. What mount options are used? What partition is mounted (is
> it md or hdaX)?
>
> I'm not sure -bk5 had the follow up fix patch for the barrier rework,
> you should probably just retry with -bk6 first.
>
> --
> Jens Axboe
>
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-10 14:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:03 current linus bk, error mounting root Jon Smirl
2005-03-09 17:16 ` Jeff Garzik
2005-03-09 18:23 ` Jon Smirl
2005-03-09 20:28 ` Jeff Garzik
2005-03-09 20:31 ` Jeff Garzik
2005-03-09 20:51 ` Jon Smirl
2005-03-09 21:09 ` Jens Axboe
2005-03-10 1:16 ` Jon Smirl
2005-03-10 7:50 ` Jens Axboe
2005-03-10 14:58 ` Jon Smirl [this message]
2005-03-10 15:31 ` Jens Axboe
2005-03-10 15:45 ` Jon Smirl
2005-03-10 15:48 ` Jens Axboe
2005-03-10 15:59 ` Jon Smirl
2005-03-10 16:01 ` Jens Axboe
2005-03-10 16:18 ` Jon Smirl
2005-03-10 16:29 ` Jens Axboe
2005-03-10 18:40 ` Jon Smirl
2005-03-10 18:52 ` Jon Smirl
2005-03-11 3:11 ` Matt Mackall
2005-03-11 3:18 ` Jon Smirl
2005-03-15 15:39 ` Jon Smirl
2005-03-15 15:47 ` Jens Axboe
2005-03-09 20:34 ` Steven Cole
[not found] ` <20050321154131.30616ed0.akpm@osdl.org>
[not found] ` <9e473391050321155735fc506d@mail.gmail.com>
2005-03-22 0:19 ` Andrew Morton
2005-03-22 0:38 ` Greg KH
2005-03-22 0:43 ` Andrew Morton
2005-03-22 0:49 ` Greg KH
2005-03-22 0:57 ` Jon Smirl
2005-03-22 4:02 ` Greg KH
2005-03-22 1:13 ` Jon Smirl
2005-03-22 0:53 ` Jon Smirl
2005-03-22 4:03 ` Greg KH
2005-03-22 0:47 ` Jon Smirl
2005-03-22 1:14 ` Kyle Moffett
2005-03-22 4:02 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 13:15 Alexander E. Patrakov
2005-03-12 19:56 ` Jon Smirl
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=9e4733910503100658ff440e3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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