From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] a problem I don't understand on a reinstall
Date: Thu, 16 Oct 2003 20:50:10 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0310162041390.5430-100000@maxroach.lanl.gov> (raw)
I had a T21, with partitions:
9fat
fs
swap
I booted the install cd, and using prepdisk I delete swap and fs, then
added
fossil
arenas0
arenas1
isect0
isect1
swap
Then I installed. Once done, it would not boot. Plan9.ini was rewritten by
the install, but set up with the local file system as local!#S/sdC0/fs,
not local!#S/sdC0/fossil.
Booted CD, ran 9fat:, changed it to fossil, instead of fs, it still
wouldn't boot. 9load complains that it can't find any partitions other
than 9fat.
reinstalled. No good. On the reinstall the 9fat was not updated, so still
had the identical plan9.ini.
Reinstalled, but this time using prep I deleted all partitions, including
9fat, then added them back, resizing them for good measure.
Still failed to boot, it's still trying to find 'fs', not 'fossil'.
ARG!
Found on booting cdrom to look around that 9fat, though resized, was
unchanged: plan9.ini was the same as before the delete all partitions,
reallocate all partitions step.
Well, what's going on here? how do I get this cd to wipe everything down
to completely clean state when it installs? Should I run fdisk/mbr from
the boot cd, then try it? It's as though too much state is being saved in
the boot info somewhere, across installs. Is it not setting up 9load
correctly? Is it not replacing 9load with a new one?
ron
next reply other threads:[~2003-10-17 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 2:50 ron minnich [this message]
2003-10-17 2:58 ` Russ Cox
2003-10-17 11:41 ` [9fans] My Eu paper, mark 2 John DeGood
2003-10-17 22:54 ` [9fans] a problem I don't understand on a reinstall ron minnich
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=Pine.LNX.4.44.0310162041390.5430-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).