9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Friedrich Psiorz <f.psiorz@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Root file system from usb-hdd on raspberry pi
Date: Tue, 26 Mar 2013 23:53:19 +0100	[thread overview]
Message-ID: <515226DF.1060500@gmx.de> (raw)
In-Reply-To: <5151C497.1090300@gmx.de>

Also, the disk still doesn't show up as sdB0 or sdXX or something like
that in /dev; still only sdU0.0
Do I have to do something to make sdB0/sdXX appear?

Am 26.03.2013 16:53, schrieb Friedrich Psiorz:
> No I get these errors when booting:
>
> can't update /dev/sdXX/data's devsd partition table for nvram: partition
> name already in use: "part nvram 63 64"
> can't update /dev/sdXX/data's devsd partition table for fossil:
> partition name already in use: "part fossil 64 99518702"
> can't update /dev/sdXX/data's devsd partition table for arenas:
> partition name already in use: "part arenas 99518702 597111894"
> can't update /dev/sdXX/data's devsd partition table for isect: partition
> name already in use: "part isect 597111894 621991554"
> can't update /dev/sdXX/data's devsd partition table for swap: partition
> name already in use: "part swap 621991554 623040130"
> can't update /dev/sdXX/data's devsd partition table for cache: partition
> name already in use: "part cache 623040130 625137282"
>
> the numbers are what's in the partition table +63
> they are the same, no matter if I set sdB0part to these numbers or the
> ones from the partition table
>
> Am 26.03.2013 15:35, schrieb erik quanstrom:
>> On Tue Mar 26 10:27:02 EDT 2013, f.psiorz@gmx.de wrote:
>>> Hmm, ok, I'm more confused now than before.
>>
>> sorry.  evidently i'm not good at explaining this.
>>
>>> do I have to put all partitions there? Or just the 'plan9' partition
>>> that fdisk created?
>>
>> put all the partitions in.  (but remember, there is no reason to use fdisk
>> partitions at all.)
>>
>>> Where do I set the environment variable? I tried adding
>>> sdB0parts='p1 0 38913'
>>> to cmdline.txt, but nothing happens.
>>
>> i misspelled it.  it should be "sdB0part".  no "s".  my bad.
>>
>> - erik
>>
>
>




  reply	other threads:[~2013-03-26 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 12:51 Friedrich Psiorz
2013-03-26 13:07 ` erik quanstrom
2013-03-26 13:47   ` Friedrich Psiorz
2013-03-26 13:56     ` erik quanstrom
2013-03-26 14:25       ` Friedrich Psiorz
2013-03-26 14:35         ` erik quanstrom
2013-03-26 15:53           ` Friedrich Psiorz
2013-03-26 22:53             ` Friedrich Psiorz [this message]
2013-03-27  7:59               ` David du Colombier
2013-03-27  9:18                 ` Friedrich Psiorz
2013-03-27 14:43                   ` Richard Miller
2013-03-27 17:37                     ` Richard Miller

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=515226DF.1060500@gmx.de \
    --to=f.psiorz@gmx.de \
    --cc=9fans@9fans.net \
    /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).