Hello

The storage.virtualdisk is related to virtual disk on storage controllers.

remoteimage -s should return a status of the remote image.

I think you should be able to boot from the remote image. You will need to configure the BIOS boot options. Our CMCs have a -e option on the remoteimage command that specifies it as the next boot device. You can check the documentation to see if that exists on the version of iDRAC you are using.

Thanks

I'm reasonably certain that I tried this multiple times and using various command sequences without success. But inspired by Daniel's comments, I tried again and this time it worked. The following commands seem to work properly using iDRAC8 on R230s and iDRAC7 on R520s; I presume they will also work on other systems with those iDRAC models.

racadm remoteimage -c -u xxx -p xxx -l xx.xx.xx.xx:/path/to/xxx.iso
racadm set iDRAC.VirtualMedia.BootOnce 1
racadm set iDRAC.ServerBoot.FirstBootDevice VCD-DVD
racadm serveraction powercycle

Of course, I need to leave the image connected during the boot, which is after my script terminates. That means I need to find a reliable, and preferably automatic, way to disconnect the image after I'm done using it. I'm still working that issue.

Note that the remoteimage command applied to an NFS share as shown above still requires the -u and -p options, though the server ignores them. Why does racadm require them?

---

@thalesifec wrote:

I'm reasonably certain that I tried this multiple times and using various command sequences without success. But inspired by Daniel's comments, I tried again and this time it worked. The following commands seem to work properly using iDRAC8 on R230s and iDRAC7 on R520s; I presume they will also work on other systems with those iDRAC models.

racadm remoteimage -c -u xxx -p xxx -l xx.xx.xx.xx:/path/to/xxx.iso
racadm set iDRAC.VirtualMedia.BootOnce 1
racadm set iDRAC.ServerBoot.FirstBootDevice VCD-DVD
racadm serveraction powercycle

Of course, I need to leave the image connected during the boot, which is after my script terminates. That means I need to find a reliable, and preferably automatic, way to disconnect the image after I'm done using it. I'm still working that issue.

Note that the remoteimage command applied to an NFS share as shown above still requires the -u and -p options, though the server ignores them. Why does racadm require them?

---

To disconnect the Remote File Share use the -d option to remoteimage:

racadm remoteimage -d

Note that neither the -u or the -p options are necessary with an NFS share.