From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] nvram
Date: Thu, 30 Jul 2009 14:45:12 -0400 [thread overview]
Message-ID: <39524e338f11b0a4ad1a069a4439f239@quanstro.net> (raw)
In-Reply-To: <75410f89120823d761141644cc47a480@quintile.net>
On Thu Jul 30 14:13:18 EDT 2009, steve@quintile.net wrote:
> no it doesn't, I had this a few days ago, moving disks about so
> nvram couldn't be found. I could still boot the system but I had to enter
> the nvram info from the keyboard, it did then try to write the data back
> which (of course) fails - perhaps it was this write to a dead disk that
> caused the boot process to die.
i hate to disagree. but i think you may have typed your
auth information incorrectly — that does cause a panic. but not having
a plan9.nvr or nvram partition does not. here's a demo i
just ran:
baxley# 9fat:
baxley# rm /n/9fat/plan9.nvr
baxley# echo reboot>/dev/reboot
[...]
2040M memory: 108M kernel data, 1931M user, 2556M swap
sdE0: LBA 3,931,200 sectors
SATADOM H Type rs1.a000 20090504AA0000000013 [newdrive]
readnvram: couldn't find nvram
can't read nvram: unknown device in # filename
authid: bootes
authdom: plan9.quanstro.net
secstore key:
password:
can't write key to nvram: unknown device in # filename
version...time...
nit: starting /bin/rc
baxley#
now if i mistype my auth information, i get
version...authpanic: boot process died: unknown
entication failed (auth_proxy rpc write: : bad key), trying mount anyways
boot: mount /: attach -- unknown user or failed authentication
dumpstack
unfortunately, at this point i'm stuck in a reboot loop and
i can only disconnect the offending media.
- erik
next prev parent reply other threads:[~2009-07-30 18:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 17:58 Lyndon Nerenberg
2009-07-28 18:08 ` erik quanstrom
2009-07-28 18:37 ` erik quanstrom
2009-07-29 13:43 ` Dan Cross
2009-07-29 13:48 ` erik quanstrom
2009-07-30 16:05 ` sqweek
2009-07-30 16:08 ` erik quanstrom
2009-07-30 16:22 ` sqweek
2009-07-30 17:58 ` erik quanstrom
2009-07-30 18:12 ` Steve Simon
2009-07-30 18:45 ` erik quanstrom [this message]
2009-07-28 21:59 ` Adriano Verardo
2009-07-28 18:09 ` ron minnich
2009-07-28 19:24 ` erik quanstrom
2009-07-28 22:38 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 14:48 Sergey Reva
2005-05-12 15:10 ` Ronald G. Minnich
2005-05-12 16:47 ` Skip Tavakkolian
2005-05-12 23:52 ` Dan Cross
2005-04-03 12:50 Sergey Reva
2005-04-03 13:39 ` Russ Cox
2005-04-03 14:44 ` Sergey Reva
2005-04-03 15:07 ` Russ Cox
2005-04-04 10:03 ` C H Forsyth
2005-04-03 16:47 ` Sergey Reva
2003-08-26 21:17 [9fans] NVRAM Kenji Arisawa
2003-08-26 22:22 ` zfolkerts
2003-08-26 22:37 ` Kenji Arisawa
2003-08-26 22:49 ` ron minnich
2003-08-26 23:06 ` Kenji Arisawa
2000-09-06 23:21 [9fans] nvram Russ Cox
2000-09-06 23:33 ` Boyd Roberts
2000-09-06 23:00 jmk
2000-09-06 23:05 ` Boyd Roberts
2000-09-06 13:24 [9fans] Re: Kernighan interview (w/ Plan 9 mention) forsyth
2000-09-06 22:47 ` [9fans] nvram Boyd Roberts
2000-09-06 22:52 ` Boyd Roberts
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=39524e338f11b0a4ad1a069a4439f239@quanstro.net \
--to=quanstro@quanstro.net \
--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).