Loading ...
Sorry, an error occurred while loading the content.

Re: [solarisx86] beadm(1M) breaks with root pool not named rpool

Expand Messages
  • Dave Miner
    ... Ah, that does explain it. The results determined by the findroot directive in legacy GRUB would have been overridden by the subsequent bootfs, but the new
    Message 1 of 4 , Nov 26, 2012
    • 0 Attachment
      On 11/21/12 10:47, John D Groenveld wrote:
      > In message <50ACEA27.70205@...
      > <mailto:50ACEA27.70205%40opensolaris.org>>, Dave Miner writes:
      > >Looks like something may have been mis-handled in the SRU back-port of
      > >the GRUB2 changes as all the mainline builds have worked fine (I
      > >specifically run one of my systems with such a config to try to ensure
      > >we catch these). I can see the reason for the traceback in the code,
      > >but don't see how it would end up with the wrong pool name offhand.
      >
      > beadm(1M) and friends apparently grokked it from legacy GRUB's
      > menu.lst:
      > # bootadm list-menu
      > the location of the boot loader configuration files is: /mpool/boot/grub
      > default 0
      > timeout 30
      > 0 s11-10
      >
      > # cat /mpool/boot/grub/menu.lst
      > splashimage /boot/grub/splash.xpm.gz
      > background 215ECA
      > timeout 30
      > default 0
      > #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
      > #---------------------END BOOTADM--------------------
      > title s11-10
      > findroot pool_rpool
      > bootfs mpool/ROOT/s11-10
      > kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS
      > module$ /platform/i86pc/$ISADIR/boot_archive
      >
      > I adjusted the findroot line to pool_mpool and beadm(1M)
      > worked.
      > Don't know how legacy GRUB was able to boot S11 (S11 Express)
      > with it broken for so long but that's probably an argument
      > for moving to GRUB2.
      >

      Ah, that does explain it. The results determined by the findroot
      directive in legacy GRUB would have been overridden by the subsequent
      bootfs, but the new logic seemingly doesn't replicate that exactly.

      Dave
    Your message has been successfully submitted and would be delivered to recipients shortly.