From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAM8pOuOm-OJ3A_V1jGQScf0Ec3ZLhhXjiO9zvwOhZVaJn_m8ag@mail.gmail.com>
References: <CAM8pOuMtjDa0bW9D3jz2bCgvbXKKET_zwjMQyqMzwsgyznv2aw@mail.gmail.com>
	<052f3dd8836c23c101619c75a1beee1c@rei2.9hal>
	<CAM8pOuOm-OJ3A_V1jGQScf0Ec3ZLhhXjiO9zvwOhZVaJn_m8ag@mail.gmail.com>
Date: Sun, 13 May 2012 19:19:12 -0600
Message-ID: <CAM8pOuMYGKSuSMUheyWqMXaf6pKwwkb+2bb5OkfGZSK2XcEVmQ@mail.gmail.com>
From: Burton Samograd <burton.samograd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] 'no fat' - boot failure
Topicbox-Message-UUID: 89c9a388-ead7-11e9-9d60-3106f5b1d025

Toggling the bootable flag on the plan9 partition did allow it to start boo=
ting.
It then looked to be iterating over the drives, where on my harddisks I got=
:

sdE0 <disk name/id>
bad disk
bad disk
bad disk
bad disk
bad disk
sdE5 <disk name/id>
bad disk
bad disk
bad disk
bad disk
bad disk

This happened for both of my SATA hard drives, the DVD got through
this stage fine.
It appeared to be reading the disks completely; my SSD took about a
minute to get
before it went to the next drive which was 2T and I didn't  bother
waiting around longer
than 5 minutes to see if it would complete.

I've had nothing but problems with this hardware anyways so I'm not
surprised that plan9 has a
hard time working on it.  I might try it on this hardware again, but
I've got another system coming
soon anyways that I'm pretty sure will work just fine.

I tried 9front because the standard distro had a problem with my
disks, or at least finding the
boot partition/floppy on the cd.  9front would boot fine as a
live/install cd so I thought I was in
the clear but unfortunately not.

--
Burton Samograd

On Sun, May 13, 2012 at 6:22 PM, Burton Samograd
<burton.samograd@gmail.com> wrote:
>> 9bootfat does its search by walking all partition table
>> entries (primary and secondary) on the bootdrive that
>> are marked as "active".
>
> Reading the grub docs, it sounds like an active partition is marked
> bootable and only one partition can be marked that way. =A0Currently my
> linux partition is marked bootable but I'm not sure if it needs to be
> since grub is installed in the MBR. =A0Any thoughts? =A0I might just try =
to
> set my plan9 partition bootable and see what happens; I'm sure i can fix
> things if I can't boot later.
>
> --
> Burton Samograd