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
