6086 add install bootblock option for bootadm

Review Request #79 - Created July 26, 2015 and submitted

Information
Toomas Soome
illumos-gate
6086
78, 80
85, 89, 90
b5cd118...
Reviewers
general
6086 add install bootblock option for bootadm
  1. no output from defaults. this is because the grub capfiles check does not provide any verbose messages - perhaps should add some?

root@testoi:~# bootadm install-bootloader -v
root@testoi:~#

  1. this is normal installgrub output with version check disabled. the default locations are used for stage files. note: this is whole disk setup, so libbe is enforcing MBR update. note: -F in installgrub is in fact useless as our grub does not use embedded versioning, but included anyhow for sake of completeness.

root@testoi:~# bootadm install-bootloader -vf
Command: "/sbin/installgrub -F -m -f //boot/grub/stage1 //boot/grub/stage2 /dev/rdsk/c3t3d0s0"
Output:
stage2 written to partition 0, 289 sectors starting at 1024 (abs 1280)
stage1 written to partition 0 sector 0 (abs 256)
stage1 written to master boot sector

  1. install to pool "tank" using current root as source for stage files
    root@testoi:/# bootadm install-bootloader -v -P tank -R /
    Command: "/sbin/installgrub -m -f //boot/grub/stage1 //boot/grub/stage2 /dev/rdsk/c3t5d0s0"
    Output:
    stage2 written to partition 0, 289 sectors starting at 1024 (abs 1280)
    stage1 written to partition 0 sector 0 (abs 256)
    stage1 written to master boot sector

  2. mount previous BE to /a and use it as altroot
    root@testoi:/# beadm mount openindiana-1 /a
    Mounted successfully on: '/a'
    root@testoi:/# bootadm install-bootloader -v -P tank -R /a
    Command: "/sbin/installgrub -m -f /a/boot/grub/stage1 /a/boot/grub/stage2 /dev/rdsk/c3t5d0s0"
    Output:
    stage2 written to partition 0, 289 sectors starting at 1024 (abs 1280)
    stage1 written to partition 0 sector 0 (abs 256)
    stage1 written to master boot sector

  3. specify only pool
    root@testoi:~# bootadm install-bootloader -v -P tank
    Command: "/sbin/installgrub -m -f /tmp/.be.ZfaGnc/boot/grub/stage1 /tmp/.be.ZfaGnc/boot/grub/stage2 /dev/rdsk/c3t5d0s0"
    Output:
    stage2 written to partition 0, 289 sectors starting at 1024 (abs 1280)
    stage1 written to partition 0 sector 0 (abs 256)
    stage1 written to master boot sector

  4. ok, those tests show tempnames for mountpoints, is it actually correbt mountpoint? one way to make sure would to run for example with truss, but for this test I incremented version in BE capability file
    root@testoi:~# beadm mount tank-1 /a
    Mounted successfully on: '/a'
    root@testoi:~# vi /a/boot/grub/capability
    root@testoi:~# grep VERSION /a/boot/grub/capability
    VERSION=26
    root@testoi:~# grep VERSION /tank/boot/grub/capability
    VERSION=25
    root@testoi:~# beadm umount /a
    Unmounted successfully
    root@testoi:~# bootadm install-bootloader -v -P tank
    Command: "/sbin/installgrub -m -f /tmp/.be.kjaqqc/boot/grub/stage1 /tmp/.be.kjaqqc/boot/grub/stage2 /dev/rdsk/c3t5d0s0"
    Output:
    stage2 written to partition 0, 289 sectors starting at 1024 (abs 1280)
    stage1 written to partition 0 sector 0 (abs 256)
    stage1 written to master boot sector
    root@testoi:~# grep VERSION /tank/boot/grub/capability
    VERSION=26

Issues

  • 0
  • 12
  • 0
  • 12
Description From Last Updated
Toomas Soome
Toomas Soome
Adam Števko
Josef Sipek
Toomas Soome
Josef Sipek
Robert Mustacchi
Toomas Soome
Toomas Soome
Toomas Soome
Toomas Soome
Igor Kozhukhov
Josef Sipek
Toomas Soome
Josef Sipek
Adam Števko
Toomas Soome
Review request changed

Status: Closed (submitted)

Loading...