Booting to alternate LUN failed in Solaris 11, why?

MichaelBalack
MichaelBalack used Ask the Experts™
on
This is using a SPARC server hardware. This is using Solaris 11, with 2 VMs (using ldm). We used fiber-optics network-based SAN Storage, create LUNs, and allocated for 1 or more for individual VMs. We are using "ldm" commands to manage these VMs. On one of this VM - mcsat1, there is only 1 LUN allocated for the rpool. Now, we wanted to add-in one more LUN to form the "storage pool" (mirrored). After that, we wanted to remove the original LUN and use only the new LUN. Please see attached document for steps we conduct.

c1d3s2 is the new disk added in and kept, and c1d2s0 is the old disk and supposed need to remove. After the detaching, we do the system reboot. However, we faced a problem here - system failed to reboot, with the reason being "boot disk can't find". In this case, we already change the "boot-disk" with command - "ldm set-variable boot-disk=IBM2SAN2 mcsat1".

In "ok" prompt, we typed "boot /virtual-devices@100/channel-devices@200/disk@3" with attempt to boot the system up via this new disk was successful. If you see the document, this IBM2SAN2 is actually refer to "/virtual-devices@100/channel-devices@200/disk@3", booting "IBM2SAN2" failed while "/virtual-devices@100/channel-devices@200/disk@3" passed, why?

Thanks in advance.
Replace-LUN---step-by-step.docx
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2014
Commented:
Changing which LUN it boots from under LDM will have no effect since LDM isn't loaded when the hardware boots. You have to change the hardware boot order under hardware. Whether it is real or virtual hardware it will still boot from the first LUN it sees if this is not set.

ok setenv boot-device device[n]

See SPARC: How to Change the Default Boot Device by Using the Boot PROM in the following document.
https://docs.oracle.com/cd/E26502_01/html/E28983/gkkvs.html

I have not read all your docx but setenv is not there so you haven't set the boot device.
MichaelBalackSenior System Engineer

Author

Commented:
Hi andyalder,

Thanks for the suggesting article and the opinion.

I roughly played around in this ok PROMPT environment. It looks like the boot-device is best to be defined as, /virtual-devices@100/channel-devices@200/disk@2, instead of originally just, IBM2SAN2.

The commands, "setenv boot-device /virtual-devices@100/channel-devices@200/disk@2", "printenv boot-device", "reset-all", and finally, "boot". System rebooting successfully.

I have a LUN replacement tomorrow. I will update you about the status.
MichaelBalackSenior System Engineer

Author

Commented:
Hi andyalder,

Yes, you are right.

I used the commands below and eventually LUN replaced can be boot without problem.

Type “init 0”, to boot to Boot PROM      

Type “setenv boot-device=/virtual-devices@100/channel-devices@200/disk@1”;
      Type “printenv boot-device”
      Type “reset-all”            * Save the updates
      Type “boot”
MichaelBalackSenior System Engineer

Author

Commented:
Thanks for expert - andyalder, in suggesting the article and pointed out the boot-device didn't updated. By using the commands recommended, the boot-device is updated and can be booting without a problem.

Really appreciated it.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial