new to ipxe . uefi problem win sanboot
|
2018-07-03, 21:24
Post: #8
|
|||
|
|||
RE: new to ipxe . uefi problem win sanboot
(2018-07-03 21:07)vascomorais Wrote: it's just that i run hiren's boot and if i don't use -no-describe i can access the hiren's boot files inside the hiren's boot menu that is in the "usb" pen. While you have not started a OS the san device can be accessed via the virtual device that iPXE creates, this is also used in the early bootloader and "menu". But as soon as a kernel is loaded there is no way for that virtual device to persist, again this is why iBFT exists and why your usage of --no-device won't work. And even if you do have iBFT support at the iPXE level, not all OSes that is loaded from hirens support iSCSI, and as such not all things will work anyway. However, you have not yet provided what the error is that you get, without that there is no way for anyone to even try to help you with that particular part of your issue. Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
new to ipxe . uefi problem win sanboot - vascomorais - 2018-07-02, 01:11
RE: new to ipxe . uefi problem win sanboot - NiKiZe - 2018-07-02, 20:03
RE: new to ipxe . uefi problem win sanboot - vascomorais - 2018-07-02, 23:03
RE: new to ipxe . uefi problem win sanboot - NiKiZe - 2018-07-02, 23:53
RE: new to ipxe . uefi problem win sanboot - NiKiZe - 2018-07-03, 00:28
RE: new to ipxe . uefi problem win sanboot - vascomorais - 2018-07-03, 21:07
RE: new to ipxe . uefi problem win sanboot - NiKiZe - 2018-07-03 21:24
Best IPXE EFI Bootable file - vascomorais - 2018-07-02, 03:06
|
User(s) browsing this thread: 1 Guest(s)