3 Replies Latest reply on Nov 13, 2019 4:21 PM by Jens

    can't open boot device


      After patching on LDOM, restarted but Ldom not boot its showing


      (0) OK boot disk0


      Can't Open boot device

        • 1. Re: can't open boot device


          From post is not clear: Is problem LDOM  guest or control?

          1. Check what device was configured for boot:  

                     printenv boot-device

                     printenv diag-device

                     printenv diag-switch?


          2. Check what disks available for LDOM:



          3.  In case it guest   LDOM, check from configuration from Control LDOM

                     ldm list-bindings -e <LDOM_NAME>




          • 2. Re: can't open boot device
            Vishwanath B -Oracle

            Hello Team,


            Make sure back-end disk device is visible and showing up in the format output on the control domain.


            Check these outputs.


            ldm ls-services

            echo | format | grep -i c0t*d*



            Vishwanath B

            • 3. Re: can't open boot device

              As you try to boot from a 'disk0', you might check that as well.

              Here is some output from a logical domain with four disks attached. disk0 and disk1 form a mirrored rpool.

              {0} ok printenv boot-device

              boot-device =           /virtual-devices@100/channel-devices@200/disk@0:a /virtual-devices@100/channel-devices@200/disk@1:a disk net

              {0} ok devalias

              vdisks-2                 /virtual-devices@100/channel-devices@200/disk@3

              vdiskv-2                 /virtual-devices@100/channel-devices@200/disk@2

              vdisks-1                 /virtual-devices@100/channel-devices@200/disk@1

              vdiskv-1                 /virtual-devices@100/channel-devices@200/disk@0

              vnet0                    /virtual-devices@100/channel-devices@200/network@0

              net                      /virtual-devices@100/channel-devices@200/network@0

              disk                     /virtual-devices@100/channel-devices@200/disk@0

              virtual-console          /virtual-devices/console@1

              name                     aliases


              If disk0 is not defined, you might end up providing arguments to some boot target rather than selecting a boot device:


              {0} ok boot disk7

              Boot device: /virtual-devices@100/channel-devices@200/disk@0:a  File and args: disk7


              Can't open disk7



              The file just loaded does not appear to be executable.