9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] I did bad things and 9front won't boot
Date: Wed, 20 Dec 2023 21:56:16 -0500	[thread overview]
Message-ID: <9C95756433D9BFC36E55357465F6A825@eigenstate.org> (raw)
In-Reply-To: <C8EAAA67-95BE-4B81-8CE8-4F45989BCEA4@o5r.ca>

At a guess, you tried to run something like:

        mount /dev/sdXX/cache

which will try to negotiate a version with your raw disk data,
and write a Tversion message to the first block of your disk.
You want to mount the 9p service which lives in /srv/cwfs.

You can probably either write it back manually, or using the
fs recovery console, documented (er, kinda) in fsconfig(8).

For reference, the fsconfig should look like:
        
        filsys main c(/dev/sdN0/fscache)(/dev/sdN0/fsworm)
        filsys dump o
        filsys other (/dev/sdN0/other)
        noauth
        newcache
        blocksize 16384
        daddrbits 64
        indirblks 4
        dirblks 6
        namelen 144
        cpu% read -c 1024 /dev/sdN0/fscache
        service cwfs
        filsys main c(/dev/sdN0/fscache)(/dev/sdN0/fsworm)
        filsys dump o
        filsys other (/dev/sdN0/other)
        noauth
        newcache
        blocksize 16384
        daddrbits 64
        indirblks 4
        dirblks 6
        namelen 144


Quoth o@o5r.ca <o@o5r.ca>:
> Hello,
> 
> I seem to have done incredibly stupid things to my 9front instance and now on boot I get "panic: unknown keyword in config block: <some character>", followed by a "mount: sys: write on closed pipe pc=0x2008c6" and "mount /srv/boot /root: mount 185: sys: write on closed pipe pc=0x2008c6”.
> 
> At this point I did try to drop into a shell, but I can’t figure out from there how I can mount my filesystem (that I can see in the list of things under /dev/sdE0/fsmain).
> 
> By now I’ve also figured out that the panic is happening “here”, in the mergeconf function:
> http://git.9front.org/plan9front/plan9front/858893ff8ff8d3abd06742276bcb794f3422bab8/sys/src/cmd/cwfs/config.c/f.html
> 
> Is there a way for me to rewrite the config block to sensible defaults by dropping into a shell and/or using a usb drive w/ 9front on it (as if doing an install) to just backstep whatever terrible thing I performed accidentally?
> 
> Thanks,
> 
> Olivier

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T110553196be52532-Mea1e17036a202917e1169d92
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2023-12-21  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  1:52 o
2023-12-21  2:47 ` qwx via 9fans
2023-12-21  2:56 ` ori [this message]
2023-12-21 11:00   ` Olivier Tremblay

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=9C95756433D9BFC36E55357465F6A825@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9fans@9fans.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).