9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Boot problem
Date: Thu, 22 Nov 2001 13:28:45 -0500	[thread overview]
Message-ID: <20011122183448.E49EC199E7@mail.cse.psu.edu> (raw)

wrenwrite failed: i/o error means that kfs (the on-disk
file system) is trying to write a disk block and getting
an error for whatever reason.  kfs isn't actually started
until after you type the user name, so it could well
be that it's not making any progress whatsoever.

if you've used plan 9 before (on another machine), you
might try:
	1. boot the install floppy
	2. instead of typing at the menus, draw a new window.
	3. run "disk/fdisk -p /dev/sdC0/data >/dev/sdC0/ctl"
		this sets up /dev/sdC0/dos, /dev/sdC0/plan9, etc.
	4. run "disk/prep -p /dev/sdC0/plan9 >/dev/sdC0/ctl"
		this sets up the partitions inside the plan9
		partition: /dev/sdC0/fs, /dev/sdC0/9fat, etc.
	5. run "disk/kfs -f /dev/sdC0/fs"
		this starts kfs
	6. run "mount /srv/kfs /n/kfs"
	7. poke around in /n/kfs

my bet is that you won't get to step 7, but knowing exactly
what happens will help.  it's easier to debug kfs problems if
you have a full window system at your disposal as well as the
ability to type commands.

russ


             reply	other threads:[~2001-11-22 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 18:28 Russ Cox [this message]
2001-11-23 15:57 ` Christian Grothaus
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10 15:09 [9fans] boot problem Thomas Marcks v W
2005-06-10  4:30 ` David Leimbach
2005-06-11  7:53   ` Thomas Marcks v W
2001-11-22 18:40 [9fans] Boot problem Russ Cox
2001-11-22 17:38 Christian Grothaus
2001-11-22  9:55 Christian Grothaus

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=20011122183448.E49EC199E7@mail.cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --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).