9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bob <rpangrazio@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Intel Sata
Date: Wed, 19 Dec 2007 09:56:26 +0000	[thread overview]
Message-ID: <f41bf516-67bc-4d27-83e2-93bd3d61cac3@x69g2000hsx.googlegroups.com> (raw)
In-Reply-To: <d7b2b200-e9cf-49c0-b7f7-3fce7744dde5@l1g2000hsa.googlegroups.com>

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, quans...@quanstro.net (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.


  parent reply	other threads:[~2007-12-19  9:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14  9:46 [9fans] Building a Floppy Disk Bob
2007-12-14 13:46 ` erik quanstrom
2007-12-14 15:23 ` [9fans] " Bob
2007-12-14 15:54   ` erik quanstrom
2007-12-14 17:27   ` Russ Cox
2007-12-17 10:04   ` Bob
2007-12-17 12:54     ` erik quanstrom
2007-12-17 13:28     ` [9fans] Intel Sata Bob
2007-12-17 13:34       ` erik quanstrom
2007-12-18  9:42       ` [9fans] " Bob
2007-12-18 14:25         ` erik quanstrom
2007-12-19  9:56         ` Bob [this message]
2007-12-20  9:36         ` Bob
2007-12-20 13:11           ` erik quanstrom
2007-12-20 16:42           ` Bob
2007-12-20 18:37             ` 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=f41bf516-67bc-4d27-83e2-93bd3d61cac3@x69g2000hsx.googlegroups.com \
    --to=rpangrazio@gmail.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).