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:20:47 +0000 [thread overview]
Message-ID: <864o6zur7k.fsf@cmarib.ramside> (raw)
In-Reply-To: <f19cb1715f98ba181589cf00ca16aef4@brasstown.quanstro.net> (erik quanstrom's message of "Fri, 18 Mar 2011 22:53:32 -0400")
erik quanstrom <quanstro at quanstro.net> writes:
> On Fri Mar 18 22:48:04 EDT 2011, cinap_lenrek at gmx.de wrote:
>
>> check the output of cat /dev/sdC0/ctl for lba48always.
>>
>> i have it enabled on my t23 because i got i/o erros (on a particular
>> block number that i forgot... it was reproducable) if its off.
>
> i don't really think this is the problem, since a dd on the whole
> disk worked.
In the interest of full disclosure, that "dd" was done under Linux. It
was a "dd if=" rather than a "dd -if". However, I just re-ran the dd
from the Plan 9 installer, using the Plan 9 dd to read the entire
partition and zero the entire partition. Neither the read nor write
returned any errors. This is with NO lba48always in cat /dev/sdC0/ctl.
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.
Has anyone looked at the "prep" layout in the install transcript I
bastebin'd? Does it look sane?
I really wish I understood how these file servers worked... I would be
able to debug this by myself. Alas, Plan 9 is a network operating
system. So, I suppose it's only natural that troubleshooting be
networked, too. ;)
--
+---------------------------------------------------------------+
|E-Mail: smiley at zenzebra.mv.com PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-03-19 14:20 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 [this message]
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=864o6zur7k.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).