mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Micha Nelissen <micha@neli.hopto.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Randy Dunlap <rdunlap@xenotime.net>, Jens Axboe <axboe@kernel.dk>,
	TejunHeo <tj@kernel.org>, lud <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: USB stick as root device does not work
Date: Mon, 23 May 2011 20:06:17 +0200	[thread overview]
Message-ID: <4DDAA219.2020507@neli.hopto.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1105231332090.2020-100000@iolanthe.rowland.org>

Hi all,

Alan Stern wrote:
> On Mon, 23 May 2011, Randy Dunlap wrote:
> Better to ask people familiar with the block layer (CC'ed).

I found out what happened: I use LILO, and lilo was not passing
root=/dev/sdb1 on the commandline, but root=811. However, I didn't see
that since on i386 that part had already scrolled off-screen. I found
out by accident, due to a user space program trying to parse that,
expecting a string, getting a number :-).

Using the following in my lilo.conf:

	append="root=/dev/sdb1 rootwait"
instead of
	root=/dev/sdb1

works perfectly. Maybe this information is useful for somebody else; I
did not find it using a quick google.

Thanks for your attention.

Micha


>> On Sun, 22 May 2011 16:13:17 +0200 Micha Nelissen wrote:
>>
>>> Hi,
>>>
>>> Using USB stick as root device does not work for me. I specify
>>> 'root=/dev/sdb1 rootwait' on the kernel commandline, but the kernel does
>>> not wait for the USB stick to be scanned and its partitions found. I
>>> have a harddisk which is /dev/sda, and this USB stick would be /dev/sdb.
>>>
>>> I think blk_lookup_devt returns the block device number even if it does
>>> not exist yet, and init/do_mounts.c:473 therefore skips waiting:
>>>
>>>         if ((ROOT_DEV == 0) && root_wait) {
>>>
>>> due to ROOT_DEV having become non-zero already.
>>>
>>> If I use the commandline: 'root=/dev/sdb1 rootdelay=5' then it does
>>> mount and boot properly. However, using rootwait seems safer and faster
>>> to me, that it's meant for this use case.
>>>
>>> Thanks for any pointers,
>>>
>>> Micha
>>> --
>> ---
>> ~Randy
>> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 
> 

      reply	other threads:[~2011-05-23 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22 14:13 Micha Nelissen
2011-05-23 17:14 ` Randy Dunlap
2011-05-23 17:33   ` Alan Stern
2011-05-23 18:06     ` Micha Nelissen [this message]

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=4DDAA219.2020507@neli.hopto.org \
    --to=micha@neli.hopto.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stern@rowland.harvard.edu \
    --cc=tj@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

all inboxes | Powered by JetHome®