public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: subbie subbie <subbie_subbie@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: optional delay after partition detection at boot time
Date: Sun, 12 Jun 2005 12:27:26 +0200	[thread overview]
Message-ID: <20050612102726.GA8470@alpha.home.local> (raw)
In-Reply-To: <20050612101514.81433.qmail@web30707.mail.mud.yahoo.com>

On Sun, Jun 12, 2005 at 03:15:14AM -0700, subbie subbie wrote:
> Willy,
>  
>  This is for a one-time use option, when the the admin
> is having a hard time finding the root partition, let
> alone the device NAME to boot the system ... proc is
> not even mounted at that point yet.

There are two alternatives at boot :

  - either you know the root device, and everything is
    OK (mount /proc; cat /proc/partitions)

  - 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 can try booting ten times finding the correct scsi
> device and partition number, but that's hairy
> especially in situations where kernel config and BIOS
> settings affect device detection.

I too know that it's sometimes hard to read SCSI devices
names on screen during the boot, but I'm not sure that
introducing a delay will be more useful than the full
pause provided by the panic. I may be wrong, though.
 
> This is not for slowing everything down, let's say
> just until root is mounted from then on, as you say,
> dmesg and the system logs are available.

OK.

Regards,
willy


  reply	other threads:[~2005-06-12 10:27 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 [this message]
2005-06-12 10:32       ` Jan Engelhardt
2005-06-13  2:22       ` David Lang
2005-06-13  4:17         ` Willy Tarreau
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=20050612102726.GA8470@alpha.home.local \
    --to=willy@w.ods.org \
    --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