Well I checked the motherboard, sdE0 is what my drive should be. So
there must be something wrong with the install if it won't recognize
the filesystem. It recognizes it in VMWare, so I am confused. I guess
I will keep on plugging away.

Thanks
Bob


On Dec 18, 9:29 am, [EMAIL PROTECTED] (erik quanstrom) wrote:
> wearing dunce cap ...  unfortunately the 9load format and kernel format
> are different and i confused them.  so modulo a missing 'S' (typo?), your 
> initial
> guess was correct:
>         local!#S/sdE0/fossil
> you can use the silkscreen on the motherboard to eliminate the guessing about
> which port your hard drive is plugged into.
>
> there are many other problems you could have.  can you boot from the live
> cd and poke around to see what's available on your hard drive?  once you
> get booted, you can open a new window, bind devsd (don't know if
> the livecd does this)
>         bind -a '#S' /dev
> recognize the partitions
>         cd /dev/sdE[whatever]
>         disk/fdisk -p data>ctl
>         test -f plan9 && disk/prep -p plan9>ctl
> you should then be able to use fossil/conf and other programs to inspect
> your installation.  9fat: will mount 9fat on /n/9fat.
>
> these manual pages
>         boot(8)
>         dossrv(4)
>         fossil(4)
>         prep(8)
>         plan9.ini(8)
> might be useful (http://plan9.bell-labs.com/sys/man/)
>
> - erik
>
> > > > kernel prints a message detailing the sata port. 9load says its #S/
> > > > sdE0, but when I try to tell the kernel the root fs is local!#/sdE0!
> > > > fossil the kernel panics because it can't connect to the given server.
>
> > > > Any ideas?
>
> > > great.
>
> > > souldn't that be "local!sdE0!fossil"?
>
> > > - erik
>
> > Well I tried local!sdE0!fossil and local!sdE0!fs to no avail. I also
> > tried sdE1 sdE2 and sdE3, since it says I have four sata ports I am
> > assuming sdE3 would be the highest drive. I'll keep trying other
> > things and let you know
>
> > I really appreciate all the help. I hope I can repay the list with
> > some good information.

Reply via email to