Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2015-09-30, 15:33
Post: #2
I'm having the same problem and was actually just about to post a new thread about this. I'm attempting to install Windows 10. Here's what's happening:

- iPXE loads & hooks to my iSCSI target (which is tgtd running on linux server)
- WinPE boots
- I map a drive to a shared copy of the Windows 10 installation, as S:\
- Run S:\Setup.exe
- Setup runs, detects my iSCSI drive, and the first stage of the installation works fine.

When the first stage of Windows setup is complete, but before the first boot:

- I change my pxe script to use sanboot instead of sanhook

First boot:

- iPXE loads & boots my iSCSI target. The Windows 10 boot screen with the animated circles appears.
- About 5 seconds into the boot, my LEDs go dark on my network interface and never come back on.
- The Windows 10 boot screen still shows with the animated circles. This stays up for about 8 minutes or so, then I get the INACCESSIBLE_BOOT_DEVICE error.

I've tried both undionly.kpxe (chainloaded from dhcp) and ipxe.usb (from a usb stick) and I get the same results. I've also

The network adapter is a Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC.

Here's my iPXE boot script:

set net0/gateway # <-- I've tried this with and without, same results.
sanhook --drive 0x80 iscsi:wopr.localdomain:::1:iqn.2015-09.localdomain.wopr:win10.boot

It's almost like Windows is initializing the driver for the network card and it's killing the iSCSI connection, but that's just a guess. Anyone have any suggestions? I'm so close to getting this working!!!
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
INACCESSIBLE_BOOT_DEVICE - jia - 2015-09-30, 13:22
RE: INACCESSIBLE_BOOT_DEVICE - jkbrowne - 2015-09-30 15:33

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