9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: smiley@zenzebra.mv.com (smiley at zenzebra.mv.com)
Subject: [9fans] New venti install won't boot after 05:00 crash
Date: Sat, 19 Mar 2011 14:47:48 +0000	[thread overview]
Message-ID: <867hbvkvzf.fsf@cmarib.ramside> (raw)
In-Reply-To: <864o6zur7k.fsf@cmarib.ramside> (smiley@zenzebra.mv.com's message of "Sat, 19 Mar 2011 14:20:47 +0000")

smiley at zenzebra.mv.com writes:

> My next step will be to attempt a fossil-only install.  If that doesn't
> generate these kinds of errors, at least we'll know the problem is
> venti's work.

Well, after zeroing the partition, I installed a fossil-only system.
Upon first boot, the system begins giving me similar i/o errors, and the
file system hangs.

This is odd, because I did "dd" reads and writes of the entire Plan 9
partition FROM the Plan 9 installer.  The partition can be read/written
from the installer, but not from the installed system.  So... what
difference between the install system and the installed system could be
responsible for this?  (Venti is no longer part of the equation.)

-- 
+---------------------------------------------------------------+
|E-Mail: smiley at zenzebra.mv.com             PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+



  parent reply	other threads:[~2011-03-19 14:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  0:58 smiley at zenzebra.mv.com
2011-03-18  3:03 ` John Floren
2011-03-18 13:26   ` smiley at zenzebra.mv.com
2011-03-18  3:22 ` ron minnich
2011-03-18  3:30   ` erik quanstrom
2011-03-18 15:47     ` smiley at zenzebra.mv.com
2011-03-18 16:12       ` Jacob Todd
2011-03-18 17:33         ` John Floren
2011-03-18 23:45           ` Steve Simon
2011-03-19  0:02             ` ron minnich
2011-03-19  1:04               ` erik quanstrom
2011-03-19  1:27                 ` erik quanstrom
2011-03-18 16:47       ` rod at hemiola.co.uk
2011-03-19  2:15         ` smiley at zenzebra.mv.com
2011-03-19  2:33           ` erik quanstrom
2011-03-19  2:47           ` cinap_lenrek at gmx.de
2011-03-19  2:53             ` erik quanstrom
2011-03-19  3:27               ` ron minnich
2011-03-19  4:17                 ` cinap_lenrek at gmx.de
2011-03-19  4:16               ` cinap_lenrek at gmx.de
2011-03-19 14:20               ` smiley at zenzebra.mv.com
2011-03-19 14:32                 ` erik quanstrom
2011-03-19 16:35                   ` cinap_lenrek at gmx.de
2011-03-19 20:29                     ` erik quanstrom
2011-03-19 14:47                 ` smiley at zenzebra.mv.com [this message]
2011-03-19 15:14                   ` erik quanstrom
2011-03-20 15:42                     ` smiley at zenzebra.mv.com
2011-03-20 16:57                       ` erik quanstrom
2011-03-20 17:12                         ` Lucio De Re
2011-03-20 17:55                           ` erik quanstrom
2011-03-20 18:09                             ` Lucio De Re
2011-03-21  3:48                             ` smiley at zenzebra.mv.com
2011-03-21  3:57                               ` erik quanstrom
2011-03-18 17:33       ` erik quanstrom

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=867hbvkvzf.fsf@cmarib.ramside \
    --to=smiley@zenzebra.mv.com \
    /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).