9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john@jfloren.net (John Floren)
Subject: [9fans] New venti install won't boot after 05:00 crash
Date: Thu, 17 Mar 2011 20:03:03 -0700	[thread overview]
Message-ID: <AANLkTin8G_xsqAgx3ynsLXwzRKmmpvOmreHJN0OPPKkP@mail.gmail.com> (raw)
In-Reply-To: <86ipvhs0q9.fsf@cmarib.ramside>

After the initial install, did you reboot pretty soon? Venti wants to spend
some time writing an initial image after the first boot, it seems, and if
you interrupt that you're in trouble

On Mar 17, 2011 6:00 PM, <smiley at zenzebra.mv.com> wrote:
> Hi,
>
> Subsequent to some discussion on this list, I decided to try setting up
> a vent-backed fossil file system. I did this straight from the 4th
> Ed. install CD. The system booted from the HDD and seemed to start up
> and shut down fine. Then, one evening I used Acme to take some notes.
> At about 05:00, I was bragging to a buddy of mine how cool Plan 9 was.
> No sooner than I began to show him Acme's nifty chording, did the rio
> window began filling up with error messages about trouble writing to the
> hard drive. Although rio kept running, the file system hung. Not being
> able to recover the system, I rebooted it. Well, I tried to. The boot
> process didn't get very far. Ever since then, every time I try to boot
> it, the kernel panics. (Messages below.)
>
> If I knew anything about how the root filesystem was brought online
> during boot, I might be able to debug this myself. Alas, I have no idea
> which programs are generating which parts of this output, so I really
> have no angle from which to attack the problem. Any ideas? The P9
> partition is the third primary partition on the disk. I'm fairly sure
> the HDD is good, because I tested it before the install, and have
> installed and run Linux on the same HDD without incident. Although I
> started and shut down Plan 9 a number of times (just to test its range
> of motion), this crash occurred the first time I tried saving any data
> to the file system (a text file under /usr/glenda/).
>
> Any help would be much appreciated!
>
> Here's what the console shows (typed by hand, may be typos):
>
> root is from (tcp, local)[local!#S/sdC0/fossil]:
> user[none]: glenda
> time...
> venti...2011/0318 00:24:56 venti: conf.../boot/venti: mem 6,252,817 bcmem
12,505,634 icmem 18,758,451...httpd tcp!127.1!8000...init...icache
18,758,451 bytes = 293,101 entries; 4 scache
> sync...2011/0318 00:24:56 arenas00: indexing 45372 clumps...
> announce tcp!127.1!17034...serving.
> fossil(#S/sdC0/fossil)...fsys: dialing venti at tcp!127.1!17034
> /boot/fossil: labelUnpack: bad label: 0xcb 0xb2 0x3d22d532 0x8cacb517
0xfc0d00cb
> /boot/fossil: fsOpen error
> fsOpen: corrupted block label
> fsys main open -c 3000: fsOpen: corrupted block label
> fsys: 'main' not open
> fsys main snaptime -s 60 -a 0500 -t 2880: fsys 'main' not open
> version...boot: mount /: fsys: 'main' not open
> panic: boot process died: unknown
> panic: boot process died: unknown
> dumpstack disabled
> cpu0: exiting
>
> --
> +---------------------------------------------------------------+
> |E-Mail: smiley at zenzebra.mv.com PGP key ID: BC549F8B|
> |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
> +---------------------------------------------------------------+
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20110317/800f3485/attachment.html>


  reply	other threads:[~2011-03-18  3:03 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 [this message]
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
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=AANLkTin8G_xsqAgx3ynsLXwzRKmmpvOmreHJN0OPPKkP@mail.gmail.com \
    --to=john@jfloren.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).