public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: David Lang <dlang@digitalinsight.com>
Cc: subbie subbie <subbie_subbie@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: optional delay after partition detection at boot time
Date: Mon, 13 Jun 2005 06:17:05 +0200	[thread overview]
Message-ID: <20050613041705.GD8907@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.62.0506121919310.3896@qynat.qvtvafvgr.pbz>

On Sun, Jun 12, 2005 at 07:22:45PM -0700, David Lang wrote:
> On Sun, 12 Jun 2005, Willy Tarreau wrote:
> 
> > - you don't know the root device, so the kernel will
> >   panic at boot because it cannot find the root device.
> >   In this case, you have the partition list still on
> >   the screen as it's among the latest things in the
> >   boot order. And if your kernel reboots upon panic,
> >   just boot it with panic=30 so get 30 seconds to read
> >   the partition table.
> 
> I have one machine inmy lab that turns out to need to boot from /dev/sdq1
> 
> trust me, that partition info has LONG since scrolled off the screen by 
> the time it fails to mount and panics.

Interesting. How many total partitions do you have ? I ask this because
David Alan Gilbert proposed a patch to dump the partition list on the
screen upon panic. Perhaps it's larger than the screen in you case ? If
you have more than 25 partitions, to you think they can fit with 2 or 3
columns ?

> I ended up setting up a serial console to capture the boot to figure this 
> machine out, but that's a pretty extreme measure to have to go to.
> 
> David Lang
> 
> P.S. I had to do this after grub failed to mount by label (my guess is 
> that grub only looks at so many drives before giving up on finding the 
> label) so don't tell me that I should just use labels and then I wouldn't 
> have to worry about this type of thing

I wouldn't tell you that, I *hate* labels. It causes lots of problems
when you simply move some disks between machines.

Regards,
Willy


  reply	other threads:[~2005-06-13  4:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12  6:50 optional delay after partition detection at boot time subbie subbie
2005-06-12  7:10 ` Jan Engelhardt
2005-06-12  7:12 ` Willy Tarreau
2005-06-12 10:15   ` subbie subbie
2005-06-12 10:27     ` Willy Tarreau
2005-06-12 10:32       ` Jan Engelhardt
2005-06-13  2:22       ` David Lang
2005-06-13  4:17         ` Willy Tarreau [this message]
2005-06-13  7:02           ` David Lang
2005-06-12 10:27   ` Geert Uytterhoeven
2005-06-12 11:05     ` Dr. David Alan Gilbert
2005-06-12 11:16       ` Willy Tarreau
2005-06-12 12:54         ` Dr. David Alan Gilbert
2005-06-12 13:10           ` Andi Kleen
2005-06-12 13:17             ` Willy Tarreau
2005-06-13  1:46   ` Valdis.Kletnieks
2005-06-12 13:25 ` Jesper Juhl

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=20050613041705.GD8907@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=dlang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=subbie_subbie@yahoo.com \
    /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