Re: unable to boot Motorola Powerstack II
Last post here except one, due to my self-imposed ban asked by Fabio's
mediation attempt. I will restrain to private replies in the future, with the
exception of mails in this sub-thread, where i clearly can be helpful.
On Tue, Jan 02, 2007 at 01:30:44AM +0100, Matthias Koch-Schirrmeister wrote:
> Am Donnerstag, 21. Dezember 2006 18:21 schrieb Alex:
> > I can confirm the suggestion by Sven. The machine boots perfectly but
> > just not from anything else.
> Hi there,
> first of all, I wish everybody a happy new year 2007.
> OK, I've been able to boot now from a local tftp server as suggested. The
> system went into installation mode and so far everything seems to be OK.
> Anyway, it's still not booting after the installation is finished.
> Last output was something like: "You have chosen not to use a boot loader or a
> boot loader is not available for your system. Boot from /dev/sda1 and use
> root=/dev/sda3." (this is mounted to /).
> I am where I started, only that I have a possibly running system on the disk,
> but I can't get it going.
> On the boot prompt I entered (assuming that the kernel is located at /vmlinuz)
> boot /pci/scsi@2/disk@0,0:3,vmlinuz (/dev/sda3 for the root partition) and
> boot /pci/scsi@2/disk@0,0:1,vmlinuz (to honour the thing about "boot from
> Outputs are "Unable to access boot device", "could not load disk label" and
> the like.
The PReP boxes don't know how to access the inside of the partitions, and need
a PReP partition to boot from. Normally the installer should have done
prep-install, and not nobootloader, so i am wondering what happened here, can
you provide the /proc/cpuinfo of your machine ?
When you do the installation, can you go to console 2, and check with parted
/dev/sda that you have indeed a prep partition.
Then before rebooting, you go to console 2 again, and you check that the
vmlinuz kernel has indeed been created (use the real one, not the symlink),
and do :
dd if=/target/boot/vmlinuz-2.6.18-3-prep of=/dev/sda1
And you should be able to reboot, booting with boot disk or simply letting the
boot happen should be enough. It is probably that it will have the wrong
root, so you need to correct that at the prompt, but you can also modify your
/etc/initramfs-tools/initramfs.config, and add a (not documented i think)
ROOT= line, or use yaird.
Please consider filing a bug report against d-i about the fact that
prep-installer is not being run on your box, including the /proc/cpuinfo
> I admit that I'm a i386 sissy, clearly I'm doing something wrong here. Or
> maybe it's just a misunderstanding of the firmware syntax? Im really puzzled.
Nope, it is just that you need to boot from a PReP partition.