9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] New venti install won't boot after 05:00 crash
Date: Fri, 18 Mar 2011 22:33:21 -0400	[thread overview]
Message-ID: <6b98ceff607b88f522142352d4cd493d@brasstown.quanstro.net> (raw)
In-Reply-To: <86ei634zzu.fsf@cmarib.ramside>

> erik quanstrom <quanstro at labs.coraid.com> writes:
> 
> > try a write test.  also, you may want to check out how venti/fossil
> > have repartitioned their play areas.  i believe i've seen them mess
> > up the size calculations.
> 
> I wiped the entire Plan 9 partition with "dd if=/dev/zero of=/dev/sda3",
> which completed without any errors.  I then booted the install CD and
> reinstalled.  (I'm getting pretty good at that ;) On the first boot, I
> let it sit unmolested.  When the system load trailed off, the screen
> began filling with write errors, and the filesystem hung, just like the
> previous two install attempts.

i have a very hard time believing that this can be
explained by a hardware problem.  i've seen a lot of
crazy disk behavior, but i have not seen lbas that
are writable only by dd, and not by other programs. :-)

i think this is our menu of believable options:

1.  ide driver problem
2.  venti problem
3.  fossil problem

the most likely problem is that venti, fossil or both
are writing outside their alloted partitions.  the 64-bit
question is, which partitions.  if the partition sizes you've
got don't look silly, it may be hard to track this down.

the easiest thing to do might be to try a fossil-only install.
it's not ideal, but maybe it's worth a shot.

- erik



  reply	other threads:[~2011-03-19  2:33 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 [this message]
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
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=6b98ceff607b88f522142352d4cd493d@brasstown.quanstro.net \
    --to=quanstro@quanstro.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).