From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 13 May 2012 22:56:02 -0400
To: 9fans@9fans.net
Message-ID: <dd6c7e1fdef58a4233fb00e512440f3b@kw.quanstro.net>
In-Reply-To: <CAM8pOuMYGKSuSMUheyWqMXaf6pKwwkb+2bb5OkfGZSK2XcEVmQ@mail.gmail.c>
References: <CAM8pOuMtjDa0bW9D3jz2bCgvbXKKET_zwjMQyqMzwsgyznv2aw@mail.gmail.com>
	<052f3dd8836c23c101619c75a1beee1c@rei2.9hal>
	<CAM8pOuOm-OJ3A_V1jGQScf0Ec3ZLhhXjiO9zvwOhZVaJn_m8ag@mail.gmail.com>
	<CAM8pOuMYGKSuSMUheyWqMXaf6pKwwkb+2bb5OkfGZSK2XcEVmQ@mail.gmail.c>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] 'no fat' - boot failure
Topicbox-Message-UUID: 89cee1f4-ead7-11e9-9d60-3106f5b1d025

On Sun May 13 21:20:40 EDT 2012, burton.samograd@gmail.com wrote:
> Toggling the bootable flag on the plan9 partition did allow it to start booting.
> 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

i'm not sure of the lineage of the 9front driver, or what hardware you're using.
this sort of sounds like a hardware funny (which may be already fixed) or
puis (power-up in standby).  the output of the "pci" command, or lspci
on linux would be helpful.  if you could also get the output of "cat /dev/sdE5/ctl"
that would be good as well.

- erik