[indiana-discuss] disappearance of SUNWgnu-libiconv and other issues with 111a

[Matt Ingenthron]

Juergen Keil wrote:
> 2009/5/3 Matt Ingenthron <ingenthr at cep.net>:
>   
>> Matt Ingenthron wrote:
>>     
>>> Jürgen Keil wrote:
>>>       
>>>>> 1) Grub seems broken after the update.  The system boots to a "grub>"
>>>>> prompt.  Feeding it the equivalent of what is in the menu.lst it will boot,
>>>>> but after that boot invoking installgrub did not help with subsequent
>>>>> reboots.  The menu.lst is correct.  The most recent thing I've tried is
>>>>> doing a beadm activate old/new... we'll see if that fixes it.  This is
>>>>> somewhat concerning to me, as it would leave a lot of users stuck.
>>>>>
>>>>>           
>>>> Did you perhaps set compression = gzip for the rpool filesystem?
>>>>
>>>>         
>>> No.  Also, it still has that behavior after using beadm to activate
>>> another BE then going back.
>>>
>>> I've backed off to 2008.11 and now done a beadm activate change/change
>>> back.  We'll see if that has an effect.
>>>       
>> It did not.  Other than installgrub and beadm activate, what else should I
>> be doing from my 2008.11 install to get grub back in working order?
>>     
>
> Which grub bits did you install with installgrub?  Those from 2008.11?
>
>   

No, those from 111a.  I've not tried again with the ones from 2008.11

> Maybe you need to installgrub the newer grub bits from build 111a, to get
> the fix for 6774616 "GRUB/ZFS Error 16 (Inconsistent filesystem structure)
> due to lack of GANG Block support"
> http://bugs.opensolaris.org/view_bug.do?bug_id=6774616
>   

I'm intimately familiar with that bug, and I'm not seeing the error 16.  
I guess it could be just the menu.lst which is using gang blocks and not 
the boot-archive, but that'd be weird.

> This assumes the upgrade from 2008.11 to build 111a did not
> install the new grub bits, but the menu.lst file was rewritten
> and now uses those zfs gang blocks, and the old grub cannot
> read the file any more?   What kind of error is reported by the
> grub console when you try a "cat /boot/grub/menu.lst" ?
>   

No error.  I see the file on the screen.  This is, of course, after I've 
done the findroot.

>   
>> As I said earlier, the menu.lst appears correct and typing in the pertinent
>> lines at the "grub>" prompt will allow the system to boot.
>>