[OmniOS-discuss] OmniOS r151022 is now out!

[Dominik Hassler]

Toomas,

using a (forced) installboot on both rpool mirror devices did the trick. 
Loader is now being used.

However there is another problem. I can boot w/o problems from the first 
device. But booting fails from the second device w/ the following message:

Can't find /boot/zfsloader

illumos/x86 boot
Default: disk-1:/boot/zfsloader
boot:


Debug info below:

$ sudo installboot -i /dev/rdsk/c10t5000CCA04103E095d0s0
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d

same on both devices


$ sudo format -> select disk -> fdisk
              Total disk size is 36481 cylinders
              Cylinder size is 16065 (512 byte) blocks

                                                Cylinders
       Partition   Status    Type          Start   End   Length    %
       =========   ======    ============  =====   ===   ======   ===
           1       Active    Solaris2          1  36480    36480    100

same on both devices


$ sudo prtvtoc /dev/rdsk/c10t5000CCA04103E095d0s2
* /dev/rdsk/c10t5000CCA04103E095d0s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      63 sectors/track
*     255 tracks/cylinder
*   16065 sectors/cylinder
*   36480 cylinders
*   36478 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*           0     16065     16064
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
        0      2    00      16065 586003005 586019069
        2      5    01          0 586051200 586051199
        8      1    01          0     16065     16064


same on both devices


boot: status
Default: disk-1:/boot/zfsloader
boot: statusdisk devices:
     disk0:   BIOS drive C ...
       disk0a: root
       disk0i: boot
     disk1:   BIOS drive D ...
       disk1s1: Solaris 2
         disk1s1a: root
         disk1s1i: boot
....
zfs devices:
   pool: rpool
bootfs: rpool/ROOT/omnios-r151022
config:

     NAME STATE
     rpool DEGRADED
       mirror DEGRADED
         c9t5000CCA04103E0B5d0s2 ONLINE
         c10t5000CCA04103E095d0s0 OFFLINE

illumos/x86 boot
Default: disk-1:/boot/zfsloader
boot:


Any hints on how to get the system boot from both rpool devices are 
highly appreciated.


Kind regards,
Dominik

On 05/15/2017 08:40 PM, Toomas Soome wrote:
>
>> On 15. mai 2017, at 21:06, Dan McDonald <danmcd at omniti.com> wrote:
>>
>>
>>> On May 15, 2017, at 12:49 PM, Dominik Hassler <hasslerd at gmx.li> wrote:
>>>
>>> Hey,
>>>
>>> after the upgrade, the boot loader is still GRUB.
>>>
>>> I did the upgrade according to the upgrade notes. Rebooted once, did a:
>>>
>>> $ sudo beadm activate omnios-r151022
>>> WARNING: menu.lst file /rpool/boot/menu.lst does not exist,
>>>        generating a new menu.lst file
>>> Activated successfully
>>>
>>> checked for a /etc/default/be file. there is none. Still the boot loader is GRUB instead of loader.
>>
>> Are you on a mirrored root pool?  It's possible the libbe code that installs loader doesn't do it to all disks in a mirrored pool...
>>
>> Worst-case scenario is to explicitly install it:
>>
>> 	foreach (drive)
>> 		installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/<drive>
>>
>> Dan
>>
>
> The problem you have is that beadm activate does not enforce MBR update in case of MBR+VTOC partitioning; you need to either run bootadm install-bootloader -Mfv or installboot -mv.
>
> Note that installboot and bootadm install-bootloader have slightly different flags; -v is good to have there, so you will see if the MBR was updated or not.
>
> The beadm activate and bootadm use the same mechanism to update the bootblocks on all pool member disks, bootadm does have extra flag to allow MBR update. installboot does only update specified disk.
>
> rgds,
> toomas
>