Hi all, Andrew, just to double check, try to boot from local HDD, mount your iSCSI target & try to access it to make sure it is a well formatted valid image, not in RAW format.
It happened to me once, I was trying to boot over AoE & had the same issue you are facing, I booted from local HDD & mounted my target just to find out it was in the RAW format, I created that image with fdisk & dd from a live CD, but the HDD I was creating from had a "dirty" partition table & unallocated space which mislead fdisk into giving me wrong numbers & dd created a wrong image. If you find out your target is in the RAW format then, reformat it & use a backup & restore tool, like Macrium reflect backup free edition, to create a backup of the disk you'd want to image then, restore that backup to your SAN target, just like a normal disk, don't forget to detach the local disk before rebooting from SAN. Good luck ! TheMadOne. --- En date de : Mer 24.11.10, gpxe-requ...@etherboot.org <gpxe-requ...@etherboot.org> a écrit : De: gpxe-requ...@etherboot.org <gpxe-requ...@etherboot.org> Objet: gPXE Digest, Vol 14, Issue 42 À: gpxe@etherboot.org Date: Mercredi 24 novembre 2010, 18h00 Send gPXE mailing list submissions to gpxe@etherboot.org To subscribe or unsubscribe via the World Wide Web, visit http://etherboot.org/mailman/listinfo/gpxe or, via email, send a message with subject or body 'help' to gpxe-requ...@etherboot.org You can reach the person managing the list at gpxe-ow...@etherboot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of gPXE digest..." Today's Topics: 1. remote booting on HP hardware results in blinking cursor (Andrew Dwyer) 2. Re: remote booting on HP hardware results in blinking cursor (mwhel...@gmail.com) 3. using gPXE as boot rom for virtualbox (James Richardson) 4. Re: remote booting on HP hardware results in blinking cursor (Andrew Bobulsky) ---------------------------------------------------------------------- Message: 1 Date: Wed, 24 Nov 2010 06:54:53 +0000 (UTC) From: Andrew Dwyer <andrew.dw...@dsto.defence.gov.au> Subject: [gPXE] remote booting on HP hardware results in blinking cursor To: gpxe@etherboot.org Message-ID: <loom.20101124t073348...@post.gmane.org> Content-Type: text/plain; charset=utf-8 Hi all, I?m trying to use gpxe to remote boot Windows 7 and Ubuntu over iSCSI on my desktop machine. I?ve tried other operating systems and setup methods too (direct and indirect installation). The problem is that once I?ve installed the OS and attempt to boot it nothing happens. When it comes to installing Windows 7 using the ?keep-san? method, the installer doesn?t even list the iSCSI target. The commands I run at the gpxe console to boot an installed OS are: dhcp net0 sanboot iscsi:SERVERNAME::::iqn.2010-11.foo:bar The result: Registered as BIOS drive 0x80 Booting from BIOS drive 0x80 "cursor blinks but nothing else happens" I?m guessing my hardware isn?t compatible somehow because I?ve installed the same OSs to different machines without a problem. The desktop machine is a HP Z400 package system. Both the motherboard and BIOS are HP. The network card I?m using is a 3Com 3C905C-TXM because gpxe wouldn?t even recognise the onboard one. Has anyone else experienced this problem? Anyone had any experience remote booting with HP hardware? Any advice would be much appreciated! Thanks Andrew ------------------------------ Message: 2 Date: Wed, 24 Nov 2010 07:06:39 +0000 From: mwhel...@gmail.com Subject: Re: [gPXE] remote booting on HP hardware results in blinking cursor To: gPXE@etherboot.org Message-ID: <005045015960725fe00495c72...@google.com> Content-Type: text/plain; charset="iso-8859-1" Andrew, This is what I use: My iSCSI target requires that I enter an initiator name. dhcp net0 set keep-san 1 set initiator-iqn INITIATORNAME sanboot iscsi:SERVERNAME::::TARGETNAME Best, Matt On Nov 24, 2010 12:54am, Andrew Dwyer <andrew.dw...@dsto.defence.gov.au> wrote: > Hi all, > I'm trying to use gpxe to remote boot Windows 7 and Ubuntu over iSCSI on > my > desktop machine. I've tried other operating systems and setup methods too > (direct and indirect installation). The problem is that once I've > installed the > OS and attempt to boot it nothing happens. When it comes to installing > Windows > 7 using the 'keep-san' method, the installer doesn't even list the iSCSI > target. > The commands I run at the gpxe console to boot an installed OS are: > dhcp net0 > sanboot iscsi:SERVERNAME::::iqn.2010-11.foo:bar > The result: > Registered as BIOS drive 0x80 > Booting from BIOS drive 0x80 > "cursor blinks but nothing else happens" > I'm guessing my hardware isn't compatible somehow because I've installed > the > same OSs to different machines without a problem. The desktop machine is > a HP > Z400 package system. Both the motherboard and BIOS are HP. The network > card > I'm using is a 3Com 3C905C-TXM because gpxe wouldn't even recognise the > onboard > one. > Has anyone else experienced this problem? Anyone had any experience remote > booting with HP hardware? Any advice would be much appreciated! > Thanks > Andrew > _______________________________________________ > gPXE mailing list > gPXE@etherboot.org > http://etherboot.org/mailman/listinfo/gpxe -------------- next part -------------- An HTML attachment was scrubbed... URL: http://etherboot.org/pipermail/gpxe/attachments/20101124/939cfbef/attachment-0001.html ------------------------------ Message: 3 Date: Wed, 24 Nov 2010 09:01:27 -0500 From: James Richardson <ja...@jamesr.biz> Subject: [gPXE] using gPXE as boot rom for virtualbox To: gPXE@etherboot.org Message-ID: <20101124140127.gb32...@dune.lan0> Content-Type: text/plain; charset=us-ascii Hello list, I have been trying (unsuccessfully) to have virtualbox boot with gpxe. I followed the steps on the wiki at http://www.etherboot.org/wiki/romburning/vbox without success. I was able to build the image and pad it to a 4k boundary. The original image was 58368, I padded to 61440 bytes. When I try to load the image in virtualbox, I get the following message: FATAL: Could not read from the boot medium! System halted. I am using virtualbox on a windows 7 host. I built the image on a Debian 64 bit system, using the code I checked out from git. I am wondering if anyone can help me out here. My workaround: I downloaded a gpxe floppy image. Virtualbox seems to work from the floppy image, but I would prefer not to have to use this step. Thank, James -- ------------------------------ Message: 4 Date: Wed, 24 Nov 2010 10:50:53 -0500 From: Andrew Bobulsky <rule...@gmail.com> Subject: Re: [gPXE] remote booting on HP hardware results in blinking cursor To: "'Andrew Dwyer'" <andrew.dw...@dsto.defence.gov.au>, <gpxe@etherboot.org> Message-ID: <026d01cb8bef$610b0d70$232128...@gmail.com> Content-Type: text/plain; charset="utf-8" Hello Andrew, Based on information I read at HP and then here http://www.broadcom.com/collateral/pg/5764M-PG100-R.pdf , it looks like your Z400 has a LOM NIC with PCI VENdor and DEVice ID's of 14E4 and 1684. I'm not sure if there are any Broadcom drivers currently in gPXE, but if there are, does anyone know which one[s] if any might be worth trying? -------- If you're using keep-san against an unformatted iSCSI target and booting a Windows 7 install disk, unless the NIC driver isn't present or some other software issue is preventing iSCSI connections, the target should show up as a disk in the system. Not being able to install to it can happen, but that's a different issue with different causes, naturally ;-) After gPXE attaches and then boots the SAN disk, if you're getting a blinking cursor, that could point to any myriad of errors (for what it's worth, I've noticed that the Windows Boot Manager MBR prints "SRLBCG" and then blanks the screen). It could be helpful to troubleshoot by using a diagnostic MBR or something, but that's a little beyond the scope of this email. I usually troubleshoot errors that you're experiencing by trying a different NIC. Sometimes the UNDI driver, if that's what you're using, doesn't play nice with all NICs. A few questions though for myself or others to help you troubleshoot: What iSCSI target are you using? What method are you using to boot gPXE? Have you tried any other NICs? Cheers, Andrew Bobulsky -----Original Message----- From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of Andrew Dwyer Sent: Wednesday, November 24, 2010 1:55 AM To: gpxe@etherboot.org Subject: [gPXE] remote booting on HP hardware results in blinking cursor Hi all, I?m trying to use gpxe to remote boot Windows 7 and Ubuntu over iSCSI on my desktop machine. I?ve tried other operating systems and setup methods too (direct and indirect installation). The problem is that once I?ve installed the OS and attempt to boot it nothing happens. When it comes to installing Windows 7 using the ?keep-san? method, the installer doesn?t even list the iSCSI target. The commands I run at the gpxe console to boot an installed OS are: dhcp net0 sanboot iscsi:SERVERNAME::::iqn.2010-11.foo:bar The result: Registered as BIOS drive 0x80 Booting from BIOS drive 0x80 "cursor blinks but nothing else happens" I?m guessing my hardware isn?t compatible somehow because I?ve installed the same OSs to different machines without a problem. The desktop machine is a HP Z400 package system. Both the motherboard and BIOS are HP. The network card I?m using is a 3Com 3C905C-TXM because gpxe wouldn?t even recognise the onboard one. Has anyone else experienced this problem? Anyone had any experience remote booting with HP hardware? Any advice would be much appreciated! Thanks Andrew _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe ------------------------------ _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe End of gPXE Digest, Vol 14, Issue 42 ************************************
_______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
