[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grub2 on power6 box.

From: Manoel Rebelo Abraches
Subject: Re: grub2 on power6 box.
Date: Fri, 30 Jul 2010 18:04:57 -0300

On Wed, 2010-07-28 at 10:45 -0400, Lennart Sorensen wrote:
> On Wed, Jul 28, 2010 at 05:27:33PM +0300, Vladimir 'φ-coder/phcoder' 
> Serbinenko wrote:
> > On 07/23/2010 11:02 PM, Lennart Sorensen wrote:
> > > So how would one explain to grub-install that it needs part_msdos when
> > > the partition tables that the md devices are running on are of type msdos?
> > > How would one make it automatically add the correct prefix (since it
> > > needs either (hd,msdos#)/boot/grub or (md0)/boot/grub or similar added
> > > instead of the default)?  And of course finally it would have to dd to
> > > the target device, rather than just create a file and try to make the
> > > firmware boot that file.  The boot device also has to be the full disk
> > > on the IBM, not a disk,partition,file combination.
> > >   
> > Normally it should be all autodetected. Could you file a bug report for
> > this? Could you tell the commands to reproduce it? I have a PPC box but
> > it has only one disk but a mdraid on partitions should do it.
> Well the problem appears to be that grub-install does this:
> # Then the partition map module.  In order to support partition-less media,
> # this command is allowed to fail (--target=fs already grants us that the
> # filesystem will be accessible).
> partmap_module=
> for x in `$grub_probe --target=partmap --device ${grub_device} 2> /dev/null`; 
> do
>    partmap_module="$partmap_module part_$x";
> done
> Unfortunately there is nothing that defines ${grub_device} in the script.
> If it used the target install device, it would in fact get the right
> result.
> Now of course another issue is that the script aborts if /boot/grub is
> not a seperate mount point.  Well on the IBM powerpc there is no reason
> to make it a seperate mount point since you can't boot from a partition
> with a filesystem anyhow.
OF can understand FAT12 filesystem. So the procedure is to mount a FAT12 
partition in /boot/grub and then run
grub-install (I have done this before and I boot trough the FAT12
partition). You could do something like:

boot hd:1,grub

> I am not sure how one would go about getting grub-install to figure out
> the grub name for the filesystem holding /boot/grub so that it can pass
> the prefix, since it could be (md0)/boot/grub or (md/0)/boot/grub
> So where is the bug track system?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]