9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Sun, 16 Dec 2007 09:22:00 -0500	[thread overview]
Message-ID: <538AA599-3025-4798-B4D8-0CFC69222E72@mac.com> (raw)
In-Reply-To: <2d9af96aa7323f20726b3fa58a715938@9netics.com>

I'm downloading the latest install disc right now, but how do I get a  
fossil onto the system? mount -m/n/myfossl /dev/sdC0/fossil?

On Dec 16, 2007, at 4:10 AM, Skip Tavakkolian wrote:

>> Hello. I got a strange cacheLocalAlloc function error consisting of
>> "get type 0 exp 0...type 40509443? exp 0". I did an fshalt and
>> restarted, but now I get
>>
>> 	user[none]: pietro
>> 	time...
>> 	fossil(#S/sdC0/fossil)...fsOpen error
>> 	fsOpen: fileRoot: corrupted file entry
>> 	fsys main open -V -c 3000: fsOpen: fileRoot: corrupted file entry
>> 	version...boot: mount /: fsys 'main' not open
>> 	panic: boot process died: unknown
>> 	panic: boot process died: unknown
>> 	dumpstack disabled
>> 	cpu0: exiting
>>
>> Note that the boot process died message comes twice. Every time I
>> subsequently try to start Plan 9, I get this error. What's going on,
>> and can I use the installer disk to fix it, and how?
>
> you should be able to boot from an install cd and then
> start another fossil for /dev/sdC0/fossil to see what's
> going on.
>


  reply	other threads:[~2007-12-16 14:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16  2:48 Pietro Gagliardi
2007-12-16  9:10 ` Skip Tavakkolian
2007-12-16 14:22   ` Pietro Gagliardi [this message]
2007-12-16 16:25     ` erik quanstrom
2007-12-16 16:54       ` Pietro Gagliardi
2007-12-16 17:25         ` erik quanstrom
2007-12-16 23:57           ` Pietro Gagliardi
2007-12-17  1:34           ` Pietro Gagliardi
2007-12-17  1:36             ` Pietro Gagliardi
2007-12-17  1:42               ` erik quanstrom
2007-12-17  1:57                 ` Pietro Gagliardi
2007-12-17 19:24                   ` john
2007-12-17 21:10                     ` Pietro Gagliardi
2007-12-18 18:13                       ` erik quanstrom
2007-12-18 18:19                         ` erik quanstrom
2007-12-19 21:02                 ` Pietro Gagliardi
2007-12-20  1:15                   ` Juan M. Mendez
2007-12-20  1:52                     ` Pietro Gagliardi
2007-12-20  2:02                       ` erik quanstrom
2007-12-20  2:10                         ` Pietro Gagliardi
2007-12-20 19:58                           ` Pietro Gagliardi
2007-12-22 22:29                             ` Pietro Gagliardi
2007-12-23  2:35                               ` Bakul Shah
2007-12-27 16:23                               ` Russ Cox
2007-12-29 16:33                                 ` Pietro Gagliardi
2007-12-29 19:06                                   ` Pietro Gagliardi
2008-01-01  1:37                                 ` Pietro Gagliardi
2008-01-11 20:01                                   ` Pietro Gagliardi
2008-01-11 20:47                                     ` Pietro Gagliardi
2008-01-11 22:29                                       ` Pietro Gagliardi

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=538AA599-3025-4798-B4D8-0CFC69222E72@mac.com \
    --to=pietro10@mac.com \
    --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).