[gPXE] NEW Could not initialise iSCSI device: Input/Output error
I got my Gigabit Intel NICs today. I followed the instructions on the wiki for flashing gPXE to the NIC's ROM. Worked like a charm. CTRL-B dhcp net0 192.168.1.109 Perfect! sanboot iscsi:192.168.1.222iqn.toshiba:E521 ...Input/Output Error. Same thing I was getting with the Broadcom BCM4401, but without the weird driver usage anomaly. If I mis-spell it intentionally, it tells me the target doesn't exist. So the Input/Output error seems to imply that it is communicating, merely refusing to use it. I tried pxebs. It always tells me the server type is invalid. However, in Windows XP, I can fire up my Microsoft iSCSI Initiator, connect, format, and use this iSCSI drive just fine. Flawless functionality. I'm about to conclude that gPXE is an utterly failed project that simply doesn't work. I tried just firing up the Windows 7 Ultimate x86/x64 Intall DVD, becasue I have read all over the interwebz that it supports iSCSI; this is apparently not true. There is no option for iSCSI discovery. ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] SANBOOT failed Input/Output Error
On Wed, 2010-10-06 at 11:43 +0800, Guo-Fu Tseng wrote: > On Mon, 4 Oct 2010 23:46:27 -0400, Michael A. Collins wrote > > This is offically driving me mad! I just setup a iSCSI-SCST box with > > the put_page patches applied and verified that it works by installing > > Fedora 13 from a box to a target. Now when I go to boot the dang > > thing it doesn't seem to want to. my iqn is right and whether I type > > it in from the gPXE command-line or set it with option 17, the result > > is the same. I can see the box connect to my target, but after a few > > back and forths I get the following in my target logs: iscsi-scst: > > __iscsi_state_change:437:***ERROR***: Connection with initiator > > iqn.2000-09.org.etherboot:UNKNOWN unexpectedly closed! > > > > This is the only error message that I can make out. I tried capturing > > the traffic at the target box, but that's even more confusing. The > > last few packets were the following: target -> client : SCSI: Data In > > LUN: 0x00 (Read Capacity(10) Response Data) client -> target : [PSH, ACK] > > client -> target : [FIN, PSH, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > > > So, my question is what the heck is going on here. Obviously, the > > target must be working or I wouldn't have been able to install the > > client box in the first place. The partition is bootable and there, > > checked by mounting locally and verifying with fdisk and lvm. Where > > can I start looking from the gPXE side, is there a way to dump a bunch > > of iscsi logs to the screen during sanboot? I want to make sure that > > I'm troubleshooting the right piece. Any help would be great! I have > > attached a capture file and an exerpt from my target logs. Mike > Hi Mike: > This issue looks familiar to me. > It seems related to the TCP stack fix I worked on before. > Could you see if this branch solve the problem: > git clone -b tcpfix2 git://git.etherboot.org/scm/people/cooldavid/gpxe.git > > Guo-Fu Tseng > No change. Still recieving the same error. Mike ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] install win 7 to SAN - boot fail
Hello Bin, This issue happens with many BIOSes out there. Basically (and I don't completely understand it myself) it considers gPXE's handing back of the boot process to be a failure and just wants you to reboot. which can be aggravating :-P Anyway, you basically need to attempt a (failed) sanboot as you have here, but after that you need to load the next step in the process (Windows PE) in the context of what gPXE can launch. Several methods are covered here: http://etherboot.org/wiki/sanboot/win2k8_iscsi_install#alternative_method_us ing_winpe If you can load WinPE from the network, that would be the simplest method (but not the easiest, in my experience), but the PXELINUX method mentioned below that would probably give you the least headache as far as installation goes. Either way, best of luck to you. Regards, Andrew Bobulsky From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of Bin Sent: Wednesday, October 06, 2010 10:15 AM To: gpxe@etherboot.org Subject: [gPXE] install win 7 to SAN - boot fail I think someone had the same issue in July but I can't find any solutions so far. I have two mahines with the same issue. One is nvidia Nforce 730i Motherboard (and Nvidia NIC/BootAgent), the other is realtek NIC. I am using UNDI only 1.0.1. The chain loading works fine and gpxe got all the infomation. Howerver, the computer refused to boot from next source(CDROM). Instead I only got the option of "PRESS A KEY TO REBOOT". Here is one sample output. DHCP (net XX:XX:XX:XX:XX) ... ok Registered as BIOS drive 0x00 Booting from BIOS drive 0x00 Boot falied Preserving connection to SAN DISK Could not boot from iscsi:192.168.x.xpc01 Operation cancelled 0xb08080a0 PRESS A KEY TO REBOOT Thanks, ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
[gPXE] install win 7 to SAN - boot fail
I think someone had the same issue in July but I can't find any solutions so far. I have two mahines with the same issue. One is nvidia Nforce 730i Motherboard (and Nvidia NIC/BootAgent), the other is realtek NIC. I am using UNDI only 1.0.1. The chain loading works fine and gpxe got all the infomation. Howerver, the computer refused to boot from next source(CDROM). Instead I only got the option of "PRESS A KEY TO REBOOT". Here is one sample output. DHCP (net XX:XX:XX:XX:XX) ... ok Registered as BIOS drive 0x00 Booting from BIOS drive 0x00 Boot falied Preserving connection to SAN DISK Could not boot from iscsi:192.168.x.xpc01 Operation cancelled 0xb08080a0 PRESS A KEY TO REBOOT Thanks, ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] chainloading gPXE from an existing PXE ROM HANGED
Hello Muhammad, I ran into the same issue as you a while back. The trick was to put in a php statement to change the MIME type to text/plain. I don't know it off the top of my head though. Once you do that, it should work. Alternatively, if you don't have any need for scripting logic, you can always use plain HTML with a text/plain mime type too. Best Regards, Andrew Bobulsky On Oct 6, 2010, at 9:09 AM, Muhammad Ammar wrote: Hi, gPXE 1.0.1 Following are contents of boot.php Regards, On Wed, Oct 6, 2010 at 3:27 PM, Thomas Miletich wrote: > Hello, > please specify which version of gPXE you're using and please provide > sample output of the boot.php script. > > Thomas > > On Tue, Oct 5, 2010 at 1:19 PM, Muhammad Ammar wrote: > > Hi All, > > > > Currently i have a PXELINUX/TFTP deployment environment and everything is > > working well except the slow kernel image download using TFTP. > > I have followed the instructions > > at > http://www.etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration#gotchas_and_issues_encountered > . > > But pxelinux menu( /tftpboot/pxelinux.cfg/default) is not loading now. > > gPXE stack is loaded successfully. > > Following are the last two lines from gPXE output > > Booting from filename "http://192.168.1.200/gpxe/boot.php"; > > http://192.168.1.200/gpxe/boot.php.. ok > > There is no progress after this. > > What i am doing wrong? > > Regards, > > ___ > > gPXE mailing list > > gPXE@etherboot.org > > http://etherboot.org/mailman/listinfo/gpxe > > > > > ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] chainloading gPXE from an existing PXE ROM HANGED
Good day Muhammad, Which filename are you passing out in your DHCP options? Can you navigate to http://192.168.1.200/gpxe/boot.php in a web browser on some other computer and save the file and examine it to ensure that it contains these two lines?: #!gpxe chain pxelinux.0 Also, can you press Control-B to get a gPXE CLI and try the following two commands to find out if they work?: dhcp net0 chain pxelinux.0 - Shao Miller ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] chainloading gPXE from an existing PXE ROM HANGED
Hi, gPXE 1.0.1 Following are contents of boot.php Regards, On Wed, Oct 6, 2010 at 3:27 PM, Thomas Miletich wrote: > Hello, > please specify which version of gPXE you're using and please provide > sample output of the boot.php script. > > Thomas > > On Tue, Oct 5, 2010 at 1:19 PM, Muhammad Ammar wrote: > > Hi All, > > > > Currently i have a PXELINUX/TFTP deployment environment and everything is > > working well except the slow kernel image download using TFTP. > > I have followed the instructions > > at > http://www.etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration#gotchas_and_issues_encountered > . > > But pxelinux menu( /tftpboot/pxelinux.cfg/default) is not loading now. > > gPXE stack is loaded successfully. > > Following are the last two lines from gPXE output > > Booting from filename "http://192.168.1.200/gpxe/boot.php"; > > http://192.168.1.200/gpxe/boot.php.. ok > > There is no progress after this. > > What i am doing wrong? > > Regards, > > ___ > > gPXE mailing list > > gPXE@etherboot.org > > http://etherboot.org/mailman/listinfo/gpxe > > > > > ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] Oddball results
On Sun, Oct 3, 2010 at 18:01, Dustin Eward wrote: > >> Dell Dimension E521? On the US support site, I see 1.1.11 (released >> on 2007-09-04) is the latest. I don't see anything in the notes for >> this machine but sometimes they update the PXE code without any notes. > > I am using the version, the PXE in it is 100% fail. > >> > left the "Phoenix BIOS" boot-up identifier. It shows for only a split >> > second, but I could probably figure out the REAL motherboard MFR and >> > part/model number if I rebooted a lot... I'll have to get back to you >> > because I can't do that right this moment. >> >> I've seen a few systems in the last 2+ years that do this (showing >> signs of the underlying BIOS) but not many. > > Yeah, and DELL missing that one... They usually go out of their way to > hide/cripple everything. It was one of their rare AMD machines from a few > years ago, I'm guessing they just weren't putting much effort into it. > >> > experiment, but I got impatient. >> >> From what I've seen, I have the impression that Intel has generally >> been very good for both PXE and Linux. > > I got that impression, so I spent the money instead of continuing to hammer > on this embedded BCM4401. The gPXE b44 .usb image off of ROM-o-Matic doesn't > even recognize it. Neitehr do the UNDI/UNDIONLY. But, the 'all drivers' > loads the UNDI and it pulls DHCP... Meh, bought the Intel cards. I have a Dell laptop with a BCM4401 LoM (14e4:170c 1028:0188). It's an Inspiron 6000 with an Intel Pentium M running BIOS A09 (2005-09-28; latest). This machine appears to be fine with a PXE boot (at least with PXELINUX). This is the versioning information I was looking for off of yours: Broadcom UNDI, PE-2.1 (build 082) v2.0.4 Copyright (C) 2000-2003 Broadcom Corporation Copyright (C) 1997-2000 Intel Corporation All rights reserved. Intel Base-Code, PXE-2.1 (build 082j) Copyright (C) 1997-2000 Intel Corporation -- -Gene ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] SANBOOT failed Input/Output Error
On Wed, 2010-10-06 at 11:43 +0800, Guo-Fu Tseng wrote: > On Mon, 4 Oct 2010 23:46:27 -0400, Michael A. Collins wrote > > This is offically driving me mad! I just setup a iSCSI-SCST box with > > the put_page patches applied and verified that it works by installing > > Fedora 13 from a box to a target. Now when I go to boot the dang > > thing it doesn't seem to want to. my iqn is right and whether I type > > it in from the gPXE command-line or set it with option 17, the result > > is the same. I can see the box connect to my target, but after a few > > back and forths I get the following in my target logs: iscsi-scst: > > __iscsi_state_change:437:***ERROR***: Connection with initiator > > iqn.2000-09.org.etherboot:UNKNOWN unexpectedly closed! > > > > This is the only error message that I can make out. I tried capturing > > the traffic at the target box, but that's even more confusing. The > > last few packets were the following: target -> client : SCSI: Data In > > LUN: 0x00 (Read Capacity(10) Response Data) client -> target : [PSH, ACK] > > client -> target : [FIN, PSH, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > target -> client : [FIN, ACK] > > > > So, my question is what the heck is going on here. Obviously, the > > target must be working or I wouldn't have been able to install the > > client box in the first place. The partition is bootable and there, > > checked by mounting locally and verifying with fdisk and lvm. Where > > can I start looking from the gPXE side, is there a way to dump a bunch > > of iscsi logs to the screen during sanboot? I want to make sure that > > I'm troubleshooting the right piece. Any help would be great! I have > > attached a capture file and an exerpt from my target logs. Mike > Hi Mike: > This issue looks familiar to me. > It seems related to the TCP stack fix I worked on before. > Could you see if this branch solve the problem: > git clone -b tcpfix2 git://git.etherboot.org/scm/people/cooldavid/gpxe.git > > Guo-Fu Tseng > Will give it a try tonight and see what happens. Mike ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
Re: [gPXE] chainloading gPXE from an existing PXE ROM HANGED
Hello, please specify which version of gPXE you're using and please provide sample output of the boot.php script. Thomas On Tue, Oct 5, 2010 at 1:19 PM, Muhammad Ammar wrote: > Hi All, > > Currently i have a PXELINUX/TFTP deployment environment and everything is > working well except the slow kernel image download using TFTP. > I have followed the instructions > at http://www.etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration#gotchas_and_issues_encountered. > But pxelinux menu( /tftpboot/pxelinux.cfg/default) is not loading now. > gPXE stack is loaded successfully. > Following are the last two lines from gPXE output > Booting from filename "http://192.168.1.200/gpxe/boot.php"; > http://192.168.1.200/gpxe/boot.php.. ok > There is no progress after this. > What i am doing wrong? > Regards, > ___ > gPXE mailing list > gPXE@etherboot.org > http://etherboot.org/mailman/listinfo/gpxe > > ___ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
