Re: [9fans] something evil happening when partitioning a hdd with the plan9 installer

[John Soros <sorosj@gmail.com>]

Thanks, pavel.

On Mon, 9 Apr 2007 11:20:22 +0200
"Paweł Lasek" <pawel.lasek@gmail.com> wrote:

> On 4/9/07, John Soros <sorosj@gmail.com> wrote:
> 
> [cut]
> 
> In this case, I'd recommend repartitioning with plain linux fdisk and
> reserve a partition for plan9 using it (Set partition type to plan9,
> you can check the number using built-in help IIRC), then during plan9
> installation just choose that partition and tell plan9 fdisk to don't
> write anything.
Yes, this definitely got me closer. I didn't know linux fdisk knew about plan9 type partitions.

> 
> And somebody ought to make plan9 bootable from something other than
> primary partition (The same problem I have with Solaris 10. I could
> use those 70 GB of hdd in my school computer, but there are not enough
> primary partition numbers left for it's disklabel...)
> 
> 

This got me a bit closer to having plan9 work on my system, as I succeded in installing it without having my partitions played with, but then came the bootsetup step. Here, the first time I simply pressed ctrl-d and rebooted the computer, but it seems that step has to be finished in order to get a 9fat partition set up with 9load, plan9.ini and the kernel, so I booted up the CD and quickly went through the bootsetup phase, selecting plan9 boot method, and selecting not to install into the mbr.

Here, when I rebooted, again, my partition table was wrong, the extended partition got messed with somehow, and reached 1 cylinder outside the phisical limit. Of course this did not make my system unbootable, but it's still queer though, that that last bootsetup phase, which shouldn't have messed with my partition table (I did not even install to the mbr), changed my extended partition.

Also, I still can not boot plan9 from grub for some odd reason. I tells me it can't bot the system.
Plan9 is on the /dev/sda1 partition, and here is how I am trying to boot it in grub:

root (hd0,0)
chainloader +1
boot

I also tried putting rootnoverify instead of root, but it doesn't work either, and I also tried the makeactive option after root (hd0,0), but again, no avail.
Thanks for the replies!
Johnny