From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <2b6b8ea49323771ca2e1ecd39f31ad43@quanstro.net>
References: <140e7ec30907300905p387e3403me05bd8168279a723@mail.gmail.com>
	<2b6b8ea49323771ca2e1ecd39f31ad43@quanstro.net>
Date: Fri, 31 Jul 2009 00:22:45 +0800
Message-ID: <140e7ec30907300922s282cb811y24dc419133582dc0@mail.gmail.com>
From: sqweek <sqweek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] nvram
Topicbox-Message-UUID: 331eaf9e-ead5-11e9-9d60-3106f5b1d025

2009/7/31 erik quanstrom <quanstro@quanstro.net>:
>> =C2=A0Speaking of, I had a disk in my server die recently, and eventuall=
y
>> it affected the nvram partition. So of course, when I booted up it
>> couldn't read it and prompted me for the auth credentials, then tried
>> to write back to nvram, got an i/o error and rebooted.
>> =C2=A0The reboot could have been caused by some other problem shortly af=
ter
>> (the motherboard seems to have given up on me also), but it raised the
>> question - does an unsuccesful write to nvram halt the boot process?
>
> no. =C2=A0it happens to me all the time. =C2=A0(when there is no
> place to write nvram, as when no disk is partitioned.)

 OK, but you won't hit an error in that case either. I was wondering
whether the i/o problem was tripping it up.
-sqweek