Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PXE Dispatcher for iPXE
2011-04-05, 22:51
Post: #5
RE: PXE Dispatcher for iPXE
(2011-04-05 20:22)mcb30 Wrote:  
(2011-04-05 18:34)robinsmidsrod Wrote:  
(2011-04-05 18:24)mcb30 Wrote:  You need something like
Code:
sanboot ${root-path} ||
to prevent the script from exiting immediately if the sanboot command fails.
Actually, I don't expect the sanboot command to return in this case, and as you can see, I drop to the shell if it actually returns.

The sanboot command will never return successfully. If it returns at all, it will return with a failure, which will terminate the script before reaching the "drop to shell" line. (See http://ipxe.org/scripting#error_handling).

This behaviour does seem a bit counter-intuitive. I'm not entirely sure what would be the best behaviour, but failure to actually connect to the SAN URL and failure to actually boot the SAN drive (e.g. missing boot sector) could be considered different.
Failing to connect to the iSCSI target would for me indicate a hard fail, and should throw an exception, but failure to boot the drive is a sort of soft fail, because the problem is with the contents of the drive, and not in communicating with it. I would consider the last one a case of success (in a way).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: PXE Dispatcher for iPXE - mcb30 - 2011-04-05, 18:24
RE: PXE Dispatcher for iPXE - mcb30 - 2011-04-05, 20:22
RE: PXE Dispatcher for iPXE - robinsmidsrod - 2011-04-05 22:51
RE: PXE Dispatcher for iPXE - mcb30 - 2011-04-06, 00:01
RE: PXE Dispatcher for iPXE - Sha0 - 2011-08-08, 15:46



User(s) browsing this thread: 2 Guest(s)