Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Intel i350 Windows 7 BSOD 0x74
2013-11-28, 04:09 (This post was last modified: 2013-11-28 09:30 by robinsmidsrod.)
Post: #2
RE: Intel i350 BSOD 0x74
I manged to solve this by using another NIC in the machine. We have the Intel 520 DA2 in these machines as well which works fine for this. It definitely seems like it's hardware/driver related in this case.

Using the ipxe.pxe kernel driver version of iPXE, the x520 enumerates as eth0. So enabling PXE boot on the 1G interface (i350) allows you to pull the ipxe image down and the machine will continue to sanboot from the x520 after this (if this enumeration doesn't happen in this order you could write a script to do this, rather than having to flash the x520s).

Just a note. During an initial test, we tried to install with the option routers option set in both "if" statements (for the 1G and 10G card) but Windows would return the error "Cannot install Windows to this disk". Placing it only in the 10G option removes this confusion and allows Windows to install.

The following is configured in our DHCP conf (the 10G and 1G are on separate VLANs in this case which is why Windows got confused, change as appropriate):

Code:
option space ipxe;
option ipxe.keep-san code 8 = unsigned integer 8;
option ipxe-encap-opts code 175 = encapsulate ipxe;
option ipxe.bus-id code 177 = string;
option iscsi-initiator-iqn code 203 = string;
option ipxe.skip-san-boot code 9 = unsigned integer 8;

group { # id="10G"
    option routers X.X.X.X; #Router IP
    next-server X.X.X.X; #TFTP Server
    host machineXX {
        #option ipxe.skip-san-boot 1; #Uncomment this when installing.
        option ipxe.keep-san 1;
        fixed-address machineXX;
        hardware ethernet XX:XX:XX:XX:XX:XX;
        option host-name "machineXX";
        option root-path "iscsi:X.X.X.X::::iqn.2013-11.blah.blah:machineXX.boot";
        if exists user-class and option user-class = "iPXE" {
            filename "";
            option routers X.X.X.X; #IP of iSCSI Target
        } else {
            filename = "ipxe.pxe";
        }
    }

group { # id="Netboot-1G"
    next-server X.X.X.X; #TFTP Server
    option routers X.X.X.X; #Router IP
    host machineXX-netboot {
        fixed-address machineXX;
        option host-name "machineXX-netboot";
        hardware ethernet XX:XX:XX:XX:XX:XX;
        if exists user-class and option user-class = "iPXE" {
            filename "";
        } else {
            filename = "ipxe.pxe";
        }
    }

I would like to try at a later stage when time permits to debug iPXE.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Intel i350 BSOD 0x74 - bleckers - 2013-11-28 04:09
RE: Intel i350 BSOD 0x74 - bleckers - 2013-11-28, 10:27



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