[ipxe-devel] sanboot error questions

Discussion Order stappers at stappers.nl
Tue Feb 12 16:06:41 UTC 2019


On Tue, Feb 12, 2019 at 04:58:07PM +0100, Christian Nilsson wrote:
> On Tue, 12 Feb 2019 at 15:33, Christian Rappo wrote:
> >
> > Trying to boot Windows Server 2019 Standard Core via IPXE using the following ISO: http://boot.ipxe.org/ipxe.iso.
> > Here is the situation:
> >
> > dhcp    (OK)
> > set keep-san 1    (OK)
> > sanhook --drive 0x80 iscsi:192.168.1.10:::1:iqn.2000-01.com.synology:Storage.Target-1.bd589bc392      (OK--->>Registered SAN device 0x80)
> > sanboot --filename \bootmgr  iscsi:192.168.1.10:::1:iqn.2000-01.com.synology:Storage.Target-1.bd589bc392   (KO--->>Could not open SAN device: Error 0x03232019)
> > sanboot --filename \bootmgr --no-describe --drive 0x80     (KO--->>Boot from SAN device 0x80 failed: Operation canceled:  http://ipxe.org/0b8080a0)
> >
> 
> Since you are not running in EFI mode, it makes little sense to use filename.
> iPXE tries to invoke BIOS to run the disk and the bootsector on the
> disk - and this fails.
> Does the disk have a valid bootsector?
> Could you tcpdump the iSCSI traffic and make sure it has valid data?
> 
> Your second sanboot command fails because the --drive is already taken
> which has some information at the error url that wasn't included:
> http://ipxe.org/03232019
> You are using --no-describe, this results in the iBFT not being filled
> in, which means that Windows won't be able to find the disk (there is
> lots of other magic here as well)
> I think you should try one sanboot, without any extra options other
> than only the SAN target, that should simplify things.
 

Result of that attempt






Hopefully readable in the discussion order



More information about the ipxe-devel mailing list