[OpenIndiana-discuss] migrating from grub to loader on 2016.10

[Tim Mooney]

All-

One of the things that didn't happen when I updated my hipster install
to 2016.10 is that my machine didn't get converted from grub to loader.

Presumably, it's because of the last section here:

 	https://www.openindiana.org/2016/09/28/loader-integration/

I have mirrored ZFS root, and my two disks are formatted as such:

$ printf "0\npartition\nprint\n" | sudo format
[elided]

partition> Current partition table (original):
Total disk cylinders available: 60764 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
   0       root    wm       1 - 60763      930.94GB    (60763/0/0) 1952315190
   1 unassigned    wm       0                0         (0/0/0) 0
   2     backup    wu       0 - 60763      930.95GB    (60764/0/0) 1952347320
   3 unassigned    wm       0                0         (0/0/0) 0
   4 unassigned    wm       0                0         (0/0/0) 0
   5 unassigned    wm       0                0         (0/0/0) 0
   6 unassigned    wm       0                0         (0/0/0) 0
   7 unassigned    wm       0                0         (0/0/0) 0
   8       boot    wu       0 -     0       15.69MB    (1/0/0) 32130
   9 unassigned    wm       0                0         (0/0/0) 0

Same partition table for disk 1:

$ printf "0\npartition\nprint\n" | sudo format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
        0. c3t0d0 <DELL-PERC H310-2.12 cyl 60764 alt 2 hd 255 sec 126>
           /pci at 0,0/pci8086,3c08 at 3/pci1028,1f78 at 0/sd at 0,0
        1. c3t1d0 <DELL-PERCH310-2.12 cyl 60764 alt 2 hd 255 sec 126>
           /pci at 0,0/pci8086,3c08 at 3/pci1028,1f78 at 0/sd at 1,0
Specify disk (enter its number): selecting c3t1d0
[disk formatted]
/dev/dsk/c3t1d0s0 is part of active ZFS pool rpool. Please see zpool(1M).

[elided]

partition> Current partition table (original):
Total disk cylinders available: 60764 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
   0       root    wm       1 - 60763      930.94GB    (60763/0/0) 1952315190
   1 unassigned    wm       0                0         (0/0/0) 0
   2     backup    wu       0 - 60763      930.95GB    (60764/0/0) 1952347320
   3 unassigned    wm       0                0         (0/0/0) 0
   4 unassigned    wm       0                0         (0/0/0) 0
   5 unassigned    wm       0                0         (0/0/0) 0
   6 unassigned    wm       0                0         (0/0/0) 0
   7 unassigned    wm       0                0         (0/0/0) 0
   8       boot    wu       0 -     0       15.69MB    (1/0/0) 32130
   9 unassigned    wm       0                0         (0/0/0) 0



So.... for a mirrored rpool like mine, is switching to loader still
just as simple as the end of the article makes it seem?  Also, would
I install the loader boot block into s0, or s8?  Since *both* disks
are marked as bootable, do I run the command once for each disk?

I haven't had a single problem with 2016.10 in more than a week, so I
really don't see ever needing to go back to any of my old boot
environments.  I'm completely OK with the conversion to loader being
a one-way trip.

Tim
-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164