From: John Stalker <stalker@maths.tcd.ie>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: venti+fossil problems on new install
Date: Fri, 22 Sep 2006 18:30:35 +0100 [thread overview]
Message-ID: <200609221830.ab12841@salmon.maths.tcd.ie> (raw)
In-Reply-To: <16e0f375b802b8ac450364f77305ab7c@quanstro.net>
> 1. what were the results with dma on?
I first tried to install with dma on. I got errors
on disk writes and reads, though certainly not on all
of them. It seemed safer to start again with dma off.
> 2. how does fmtarenas fail? what is the error message?
fatal venti/fmtarenas error: can't initialize /dev/sdC0/arenas, writing block
0 failed: can't write partition='/dev/sdC0/arenas': i/o error
done with /dev/sdC0/arenas
fatal venti/fmtisect error: can't initialize /dev/sdC0/isect, writing block 0
failed: can't write partition='/dev/sdC0/isect': i/o error
done with /dev/sdC0/isect
There were errors formatting the indices and arenas.
> 3. how do you verify that the disk driver is hosed?
disk/fdisk claims it can't read the mbr:
The disk you selected HAS NO master boot record on its first sector.
(Perhaps it is a blank disk.)
You need a master boot record to use the disk.
Should we install a default master boot record?
Install mbr (y,n)[no default]:
The mbr was written earlier by disk/fdisk and is read by FreeBSD without
problems. It was read by disk/prep a few minutes before, also without
problems.
> i would try installing with just fossil on a laptop.
I may do that, but I am reluctant to continue without figuring out what
went wrong. From my point of view the error message above means at least
one of the following must be true:
1) my hard disk is bad, or
2) my bios is setting it up incorrectly on boot, or
3) there is a bug in the disk driver
Any of these would be bad and could turn around later and bite me in some
other, worse, way later. I would like to fix this while the problem is
repeatable and the consequences are not too scary.
> - erik
--
John Stalker
School of Mathematics
Trinity College Dublin
tel +353 1 896 1983
fax +353 1 896 2282
next prev parent reply other threads:[~2006-09-22 17:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 6:50 John Stalker
2006-09-21 8:13 ` erik quanstrom
2006-09-21 18:19 ` Lyndon Nerenberg
2006-09-21 18:25 ` erik quanstrom
2006-09-21 18:51 ` jmk
2006-09-21 20:27 ` C H Forsyth
2006-09-21 20:47 ` Charles Forsyth
2006-09-21 20:56 ` jmk
2006-09-21 21:08 ` Charles Forsyth
2006-09-21 21:50 ` erik quanstrom
2006-09-21 22:00 ` Charles Forsyth
2006-09-21 22:16 ` erik quanstrom
2006-09-21 22:31 ` Charles Forsyth
2006-09-21 22:31 ` jmk
2006-09-21 23:22 ` erik quanstrom
2006-09-21 23:28 ` geoff
2006-09-21 23:47 ` geoff
2006-09-22 0:05 ` erik quanstrom
2006-09-22 0:24 ` Russ Cox
2006-09-22 0:50 ` erik quanstrom
2006-09-22 1:25 ` jmk
2006-09-22 7:23 ` John Stalker
2006-09-22 11:23 ` erik quanstrom
2006-09-22 17:30 ` John Stalker [this message]
2006-09-22 17:45 ` erik quanstrom
2006-09-22 19:48 ` John Stalker
2006-09-22 20:09 ` erik quanstrom
2006-09-22 20:50 ` John Stalker
2006-09-22 21:06 ` erik quanstrom
2006-09-22 0:29 ` jmk
2006-09-21 23:52 ` erik quanstrom
2006-09-21 23:59 ` erik quanstrom
2006-09-22 0:50 ` geoff
2006-09-22 16:39 ` erik quanstrom
2006-09-23 5:24 Zoran Kolic
2006-09-23 6:51 ` John Stalker
2006-09-23 10:34 ` erik quanstrom
2006-09-23 15:04 ` Russ Cox
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=200609221830.ab12841@salmon.maths.tcd.ie \
--to=stalker@maths.tcd.ie \
--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).