etherboot-discuss Mailing List for Etherboot (Page 3)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-discuss — General Etherboot Discussion
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(54) |
Apr
(94) |
May
(199) |
Jun
(152) |
Jul
(92) |
Aug
(88) |
Sep
(114) |
Oct
(31) |
Nov
(50) |
Dec
(59) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(56) |
Feb
(35) |
Mar
(106) |
Apr
(33) |
May
(22) |
Jun
(5) |
Jul
(14) |
Aug
(32) |
Sep
(74) |
Oct
(38) |
Nov
(36) |
Dec
(12) |
| 2008 |
Jan
(79) |
Feb
(42) |
Mar
(53) |
Apr
(57) |
May
(63) |
Jun
(33) |
Jul
(35) |
Aug
(61) |
Sep
(161) |
Oct
(161) |
Nov
(55) |
Dec
(71) |
| 2009 |
Jan
(68) |
Feb
(79) |
Mar
(142) |
Apr
(92) |
May
(79) |
Jun
(71) |
Jul
(97) |
Aug
(118) |
Sep
(108) |
Oct
(83) |
Nov
(42) |
Dec
(43) |
| 2010 |
Jan
(23) |
Feb
(3) |
Mar
(18) |
Apr
(10) |
May
(12) |
Jun
(12) |
Jul
(5) |
Aug
|
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(9) |
| 2011 |
Jan
(2) |
Feb
(13) |
Mar
(25) |
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2012 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Michael H. <iti...@gm...> - 2011-03-06 20:19:56
|
Hi Mahboob, Windows 7 has a hard time figuring out its disk architecture. There is a registry key you can delete, or run Fogprep.exe from the Fog Project installation package. A google search should point you in the right direction. Mike On Mar 6, 2011 2:03 PM, "Mahboob AliKhan" <Mah...@ri...> wrote: > I had a question about windows 7 sanboot and would appreciate some help. > > So, when I try sanbooting windows 7, i noticed that it by default makes 2 partitions while installing. the first one is some 100 MB, that it uses for some configuration files and 12 Gb for other installation files. Now after I installed the windows 7 on to the local disk, i wanted to copy the image from local disk to my iscsi target. So, when i do fdisk -l on my local machine, it shows 2 partitions, so i did a dd command which starts from first cylinder and goes on till the last cylinder, in short, I am copying the whole thing ( 2 partitions) as one big Lun ( one partition). Now whats happening becuase of this is that, when I try to boot my laptop with this LUN, it starts fine, then it says bad hard disk and reboots again. > > So, can some one please explain me, how i can copy the windows 7 image to a target with avoiding this issue. > > btw, I have tried installing it directly to an iscsi target and it works fine, but my use case requires me to copy it to the local machine and then copying it over. > > Thanks > Mahboob > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss |
|
From: Mahboob A. <Mah...@ri...> - 2011-03-06 20:01:44
|
I had a question about windows 7 sanboot and would appreciate some help. So, when I try sanbooting windows 7, i noticed that it by default makes 2 partitions while installing. the first one is some 100 MB, that it uses for some configuration files and 12 Gb for other installation files. Now after I installed the windows 7 on to the local disk, i wanted to copy the image from local disk to my iscsi target. So, when i do fdisk -l on my local machine, it shows 2 partitions, so i did a dd command which starts from first cylinder and goes on till the last cylinder, in short, I am copying the whole thing ( 2 partitions) as one big Lun ( one partition). Now whats happening becuase of this is that, when I try to boot my laptop with this LUN, it starts fine, then it says bad hard disk and reboots again. So, can some one please explain me, how i can copy the windows 7 image to a target with avoiding this issue. btw, I have tried installing it directly to an iscsi target and it works fine, but my use case requires me to copy it to the local machine and then copying it over. Thanks Mahboob |
|
From: Joseph L. C. <jc...@ac...> - 2011-03-06 04:44:19
|
>Thanks for the quick response, but i am still not clear on how I am getting >an ip address on the server after reboot, you mean the ks=http://x.x.x.x line >is going to be applied to my server? or do I need to have a kickstart server on >my network and that line points to it? A "kickstart server " is really glorified speak, a host with an http server would suffice. Have a read on the rhel docs about ks installations: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch-kickstart2.html A working example I last used was: title CentOS Anaconda Install root (hd0,0) kernel /vmlinuz ip=dhcp ksdevice=eth0 ks=http://host.domain.com/foo.cfg vnc vncpassword=SuperSecret initrd /initrd.img By now you should have the hang of it, you specify the ip and many other params for that matter on the kernel line... Once the kernel and initrd are loaded into memory, you can actually wipe and reconfigure the block devices so there really is no limitation to what can be in the ks file. Good luck, jlc Ps. http://www.etherboot.org/wiki/mailinglists |
|
From: Joseph L. C. <jc...@ac...> - 2011-03-06 03:26:36
|
>I have been tasked with migrating a number of fedora 6 servers to centos 5.5. >The problem is I don't have any console access, usb key, cdrom or floppy. >So my question is, can still remotely install centos 5.5 on these servers using >gPXE without any of these options available? > >Thanks in advance, You don't need gPXE, you can add a grub entry that points to the kernel and initial ramdisk from the iso that you copy into /boot. Finally, add a ` ks=http://...` and possibly a `vnc vncpassword=...` to the kernel line in the grub stanza, set it to default, then reboot. Make sure you get it right:) I do this all the time in this scenario, it works fine. jlc |
|
From: Curtis K. <cur...@gm...> - 2011-03-06 03:04:54
|
Hi, I have been tasked with migrating a number of fedora 6 servers to centos 5.5. The problem is I don't have any console access, usb key, cdrom or floppy. So my question is, can still remotely install centos 5.5 on these servers using gPXE without any of these options available? Thanks in advance, Curtis |
|
From: David W. <dav...@gm...> - 2011-03-03 09:35:54
|
I'm having an issue with a Windows 7 SP1 (x86) installation that I installed directly to an iSCSI target. The system has three NICs in it but it appears that Windows has developed an unhealthy attachment to the one it used during install. gPXE/Etherboot will use any of the cards to boot up, but once Windows gets to the part where it should take over the system just reboots. The system works fine otherwise, but this prevents me from teaming/bonding the cards, replacing a bad card, or setting up any kind of fault tolerance. On a related note, what is the recommended way to get more bandwidth to the iSCSI target using gPXE and Windows 7? MPIO and MCS appear to be disabled and/or unsupported. Any advice you can offer is greatly appreciated. Thanks, David Woodward |
|
From: Paco B. <fbe...@ni...> - 2011-02-23 11:05:42
|
Hi, I'm new to this list. I have a short question about the project; does the code include support for IPv6? If not, I would appreciate if you could guide me to the source code, so that I could see how much effort would be needed to adapt it to IPv6. Thanks! Best regards, Paco Bernabé ============================================ F.J. Bernabé Pellicer Nikhef, Dutch National Institute for Sub-atomic Physics Group Computer Technology Room: H154 Phone: +31 20 592 2267 Science Park 105 1098 XG Amsterdam The Netherlands |
|
From: <eri...@te...> - 2011-02-16 18:05:32
|
Hello: I recently downloaded the gpxe 1.0.1+ .iso using the "all drivers" option from the rom-o-matic site but, I don't think the image at the top of the git tree supports my Intel nic (82566DM-2)? Running "ifstat eth0" from gpxe cmd line returns "eth0: no such interface" All cables are properly connected and, "dhcp any" returns "ok" Do you have a version of gpxe that works with my nic? I would be happy to test a new version for you! Thank you for your help, Erin |
|
From: Mahboob A. <Mah...@ri...> - 2011-02-10 18:20:08
|
Thanks once again for your help, I will it out. Thanks Mahboob -----Original Message----- From: Andrew Bobulsky [mailto:ru...@gm...] Sent: Thursday, February 10, 2011 7:05 AM To: Mahboob AliKhan Cc: eth...@li... Subject: Re: [Etherboot-discuss] Question about san boot - iscsi initiator Hello again Mahboob, You can do this fairly easily. The way I've set the initiator IQN was through the use of a script. If you drop to the gPXE command line and type "config" to enter the configuration menu, you'll see all the variables listed there, and one of them should be "initiator-iqn." By default, the initiator IQN is configured to what you're seeing there, as "iqn.2000-09.org.etherboot:UNKNOWN" You can set it to anything you like by specifying the value for it from the command line or through a script. Using "desktop.rulerof.com" as an example, you could do: > set initiator-iqn iqn.2011-02.com.rulerof.desktop:iscsiboot Alternatively, the doc suggests that you can also set the initiator IQN using DHCP option 203 (defined here: http://etherboot.org/api/dhcp_8h-source.html#l00399). I don't know if I've ever done this, but it should work. Not sure off the top of my head what you'd need to do to get it set up, though I suspect it's easier for ISC DHCP than MS DHCP ;-) The script-based method is more straightforward, but if you're currently booting your client using the DHCP root-path option, converting over to a scripted setup can be a bit of a chore. Best regards, Andrew Bobulsky On Thu, Feb 10, 2011 at 1:59 AM, Mahboob AliKhan <Mah...@ri...> wrote: > I had a question about iscsi initiator san boot and would really > appreciate if someone could help me out. > > > > When I download iscsi initiator boot version, I can change its name > but when I try to san boot that image, the iqn name I see is > iqn.2000-09.org.etherboot:UNKNOWN, Is there any way I can change this > name as I am having a usecase, where I need different iqn names for > different booting clients. > > > > Thanks > > Mahboob > > ---------------------------------------------------------------------- > -------- The ultimate all-in-one performance toolkit: Intel(R) > Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Andrew B. <ru...@gm...> - 2011-02-10 15:05:16
|
Hello again Mahboob, You can do this fairly easily. The way I've set the initiator IQN was through the use of a script. If you drop to the gPXE command line and type "config" to enter the configuration menu, you'll see all the variables listed there, and one of them should be "initiator-iqn." By default, the initiator IQN is configured to what you're seeing there, as "iqn.2000-09.org.etherboot:UNKNOWN" You can set it to anything you like by specifying the value for it from the command line or through a script. Using "desktop.rulerof.com" as an example, you could do: > set initiator-iqn iqn.2011-02.com.rulerof.desktop:iscsiboot Alternatively, the doc suggests that you can also set the initiator IQN using DHCP option 203 (defined here: http://etherboot.org/api/dhcp_8h-source.html#l00399). I don't know if I've ever done this, but it should work. Not sure off the top of my head what you'd need to do to get it set up, though I suspect it's easier for ISC DHCP than MS DHCP ;-) The script-based method is more straightforward, but if you're currently booting your client using the DHCP root-path option, converting over to a scripted setup can be a bit of a chore. Best regards, Andrew Bobulsky On Thu, Feb 10, 2011 at 1:59 AM, Mahboob AliKhan <Mah...@ri...> wrote: > I had a question about iscsi initiator san boot and would really appreciate > if someone could help me out. > > > > When I download iscsi initiator boot version, I can change its name but when > I try to san boot that image, the iqn name I see is > iqn.2000-09.org.etherboot:UNKNOWN, Is there any way I can change this name > as I am having a usecase, where I need different iqn names for different > booting clients. > > > > Thanks > > Mahboob > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Mahboob A. <Mah...@ri...> - 2011-02-10 06:59:47
|
I had a question about iscsi initiator san boot and would really appreciate if someone could help me out. When I download iscsi initiator boot version, I can change its name but when I try to san boot that image, the iqn name I see is iqn.2000-09.org.etherboot:UNKNOWN, Is there any way I can change this name as I am having a usecase, where I need different iqn names for different booting clients. Thanks Mahboob |
|
From: Vivek S. <vi...@ch...> - 2011-02-07 05:15:28
|
Whats the size of your hard disk ? Are you trying to create one single partition ? > In fact, my boot > sequence doesn't work if partitions exist because gpxe will attempt to > boot and get a "operating system missing" error and stop without ever > falling back to boot to cd Is your CD next in the boot sequence after the iSCSI target in your BIOS boot order ? Also make sure that you don't have any USB pen drives plugged in during the installation and also Remove you local hard drives. > -----Original Message----- > From: Lyas Spiehler [mailto:lsp...@gm...] > Sent: 07 February 2011 01:35 > To: Vivek Subbarao > Subject: Re: [Etherboot-discuss] Windows 7 iscsi install > > I've tried to install with no partitions created. In fact, my boot > sequence doesn't work if partitions exist because gpxe will attempt to > boot and get a "operating system missing" error and stop without ever > falling back to boot to cd. Unless of course it was one of my attempts > of booting to a SAN with the OS already installed, in which case it > would never try to boot to cd because it would begin booting the OS on > the SAN, however, as I mentioned before, this also doesn't work > because it only reboots midway through booting. > > Sent from my iPhone > > On Feb 6, 2011, at 12:31 AM, "Vivek Subbarao" <vi...@ch...> > wrote: > > > > > Hi, > > > > Are you installing to a raw disk or to a disk that already contains a > partition ? If its the second one, then Windows 7 might have some > problem installing to that partition due to alignment issues. Try > installing to a raw disk. > > > > Thank you, > > Vivek S > > > > -----Original Message----- > > From: Lyas Spiehler [mailto:lsp...@gm...] > > Sent: Sat 2/5/2011 10:44 AM > > To: eth...@li... > > Subject: [Etherboot-discuss] Windows 7 iscsi install > > > > I am chainloading gpxe through my existing pxe environment. When I > attempt > > to boot to an unpartitioned iscsi target, my system falls back to cd > > booting, when it loads up the windows 7 enterprise install cd, and > looks > > fine until it actually appears to begin "copying files" during the > > installation, but fails before reaching even 1% with an error message > that > > says, "Windows could not format a partition on disk 0. The error > occurred > > while preparing the partition selected for installation. Error code: > > 0x80070057" I can however load the iscsi target using windows iscsi > > initiator and format the disk successfully. I've tried this with 3 > different > > client computers all using different nics. I've also tried this with > 2 > > different servers. Both of them had different nics. I've used IET and > TGT to > > setup targets on Ubuntu and CentOS based distributions. I've used USB > flash > > drives, IDE drives, and SATA drives as targets. I've also installed > directly > > to the disks and booted to them over iscsi using gpxe, but they > reboot > > midway through booting with no error. I've also used different > windows 7 > > install disks (professional and enterprise). Within each test > environment, I > > can perform and operation against any of my targets within disk > management > > after using the iscsi initiator to connect my servers, without a > hitch. > > (create partitions, format partitions, delete partitions, write and > read to > > the filesystem) I'm officially out of ideas and desperate. Any help > is > > greatly appreciated! Thank you! > > |
|
From: Lyas S. <lsp...@gm...> - 2011-02-05 18:45:03
|
I am chainloading gpxe through my existing pxe environment. When I attempt to boot to an unpartitioned iscsi target, my system falls back to cd booting, when it loads up the windows 7 enterprise install cd, and looks fine until it actually appears to begin "copying files" during the installation, but fails before reaching even 1% with an error message that says, "Windows could not format a partition on disk 0. The error occurred while preparing the partition selected for installation. Error code: 0x80070057" I can however load the iscsi target using windows iscsi initiator and format the disk successfully. I've tried this with 3 different client computers all using different nics. I've also tried this with 2 different servers. Both of them had different nics. I've used IET and TGT to setup targets on Ubuntu and CentOS based distributions. I've used USB flash drives, IDE drives, and SATA drives as targets. I've also installed directly to the disks and booted to them over iscsi using gpxe, but they reboot midway through booting with no error. I've also used different windows 7 install disks (professional and enterprise). Within each test environment, I can perform and operation against any of my targets within disk management after using the iscsi initiator to connect my servers, without a hitch. (create partitions, format partitions, delete partitions, write and read to the filesystem) I'm officially out of ideas and desperate. Any help is greatly appreciated! Thank you! |
|
From: Mahboob A. <Mah...@ri...> - 2011-02-04 01:07:26
|
Thanks for the suggestion, I will try this one out and let you know. Thanks Mahboob From: Vivek Subbarao [mailto:vi...@ch...] Sent: Thursday, February 03, 2011 2:35 AM To: Mahboob AliKhan; eth...@li... Cc: Nitin Gupta Subject: RE: [Etherboot-discuss] Need help with San boot - Windows XP boot stuckat Logo Try making the disk signature 0 in the OS image you are booting from. This signature starts at offset of 440 and is 4 bytes long. Take a look at MBR wiki http://en.wikipedia.org/wiki/Master_boot_record. From: Mahboob AliKhan [mailto:Mah...@ri...] Sent: 03 February 2011 13:58 To: eth...@li... Cc: Nitin Gupta Subject: [Etherboot-discuss] Need help with San boot - Windows XP boot stuckat Logo I was trying to do a san boot (gpxe) using a windows XP and I am facing some issues with it. I have installed Microsoft iscsi boot initiator and san boot as mentioned on website (http://etherboot.org/wiki/sanboot/winnt_iscsi) and followed the steps mentioned, installing win XP on 4 gb partition and trying to boot it from a Linux machine. The problem I am facing is the boot goes fine till I see the windows logo and then it just sits there and it goes in some kind of weird loop there. So, in order to debug, I installed windbg and I noticed some irregularities: "No sBFT found". I am trying to san boot on a Windows Desktop (Dell model). I am attaching the debugging transcript I got from windbg, Can someone please let me know what's wrong? Really appreciate your help in advance. Thanks Ali |
|
From: Mahboob A. <Mah...@ri...> - 2011-02-04 01:05:05
|
Thanks a lot for replying. I did find the below mentioned website, but it does not say anything on how to fix it. The debug messages I sent earlier didn't had no NIC related information as I did not had any drivers installed on it. So, As Michael suggested, I used the new sanboot.conf and also installed NIC drivers. My Desktop has an in build NIC card (Broadcom 57XX Gigabit Integrated Controller) and an extra NIC card hooked on (Intel PRO 1000). So I installed both the drivers but I am still facing the same problem. I am attaching the debug messages along, so can someone please take a look. I really appreciate you guys help. The desktop I am using is Dell optiplex GX280 series. Thanks Mahboob -----Original Message----- From: Andrew Bobulsky [mailto:ru...@gm...] Sent: Thursday, February 03, 2011 6:53 AM To: Mahboob AliKhan Cc: eth...@li...; Nitin Gupta Subject: Re: [Etherboot-discuss] Need help with San boot - Windows XP boot stuck at Logo Hello Mahboob, It's unfortunate that you're having trouble! Some quick Googling turned up the following post to the list from June of last year: http://permalink.gmane.org/gmane.network.etherboot.gpxe/1124 While his issue isn't precisely the same as yours, I notice from your WinDbg output that the line[s] where NIC detection occurs don't show up. Perhaps Sanbootconf's debug output has changed somewhat since then, but it could be an indicator of what's causing your trouble. As Michael asked, is it possible that the NIC driver for your machine isn't installed correctly or that it's not marked as boot-start? Cheers, Andrew Bobulsky On Thu, Feb 3, 2011 at 3:27 AM, Mahboob AliKhan <Mah...@ri...> wrote: > > > I was trying to do a san boot (gpxe) using a windows XP and I am > facing some issues with it. > > > > I have installed Microsoft iscsi boot initiator and san boot as > mentioned on website (http://etherboot.org/wiki/sanboot/winnt_iscsi) > and followed the steps mentioned, installing win XP on 4 gb partition > and trying to boot it from a Linux machine. The problem I am facing is > the boot goes fine till I see the windows logo and then it just sits > there and it goes in some kind of weird loop there. > > > > So, in order to debug, I installed windbg and I noticed some irregularities: > > "No sBFT found". > > > > I am trying to san boot on a Windows Desktop (Dell model). > > > > I am attaching the debugging transcript I got from windbg, Can > someone please let me know what's wrong? > > > > Really appreciate your help in advance. > > > > Thanks > > Ali > > > > ---------------------------------------------------------------------- > -------- Special Offer-- Download ArcSight Logger for FREE (a $49 USD > value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Andrew B. <ru...@gm...> - 2011-02-03 14:52:46
|
Hello Mahboob, It's unfortunate that you're having trouble! Some quick Googling turned up the following post to the list from June of last year: http://permalink.gmane.org/gmane.network.etherboot.gpxe/1124 While his issue isn't precisely the same as yours, I notice from your WinDbg output that the line[s] where NIC detection occurs don't show up. Perhaps Sanbootconf's debug output has changed somewhat since then, but it could be an indicator of what's causing your trouble. As Michael asked, is it possible that the NIC driver for your machine isn't installed correctly or that it's not marked as boot-start? Cheers, Andrew Bobulsky On Thu, Feb 3, 2011 at 3:27 AM, Mahboob AliKhan <Mah...@ri...> wrote: > > > I was trying to do a san boot (gpxe) using a windows XP and I am facing some > issues with it. > > > > I have installed Microsoft iscsi boot initiator and san boot as mentioned on > website (http://etherboot.org/wiki/sanboot/winnt_iscsi) and followed the > steps mentioned, installing win XP on 4 gb partition and trying to boot it > from a Linux machine. The problem I am facing is the boot goes fine till I > see the windows logo and then it just sits there and it goes in some kind of > weird loop there. > > > > So, in order to debug, I installed windbg and I noticed some irregularities: > > “No sBFT found”. > > > > I am trying to san boot on a Windows Desktop (Dell model). > > > > I am attaching the debugging transcript I got from windbg, Can someone > please let me know what’s wrong? > > > > Really appreciate your help in advance. > > > > Thanks > > Ali > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Vivek S. <vi...@ch...> - 2011-02-03 10:34:45
|
Try making the disk signature 0 in the OS image you are booting from. This signature starts at offset of 440 and is 4 bytes long. Take a look at MBR wiki http://en.wikipedia.org/wiki/Master_boot_record. From: Mahboob AliKhan [mailto:Mah...@ri...] Sent: 03 February 2011 13:58 To: eth...@li... Cc: Nitin Gupta Subject: [Etherboot-discuss] Need help with San boot - Windows XP boot stuckat Logo I was trying to do a san boot (gpxe) using a windows XP and I am facing some issues with it. I have installed Microsoft iscsi boot initiator and san boot as mentioned on website (http://etherboot.org/wiki/sanboot/winnt_iscsi) and followed the steps mentioned, installing win XP on 4 gb partition and trying to boot it from a Linux machine. The problem I am facing is the boot goes fine till I see the windows logo and then it just sits there and it goes in some kind of weird loop there. So, in order to debug, I installed windbg and I noticed some irregularities: "No sBFT found". I am trying to san boot on a Windows Desktop (Dell model). I am attaching the debugging transcript I got from windbg, Can someone please let me know what's wrong? Really appreciate your help in advance. Thanks Ali |
|
From: Mahboob A. <Mah...@ri...> - 2011-02-03 08:28:05
|
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com4
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Wed Feb 2 21:28:29.265 2011 (UTC - 8:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
nt!DbgBreakPoint:
804e2a36 cc int 3
kd> g
SAN Boot Configuration Driver initialising
Found ACPI table "iBFT" at 93af0 OEM ID "FENSYS" OEM table ID "gPXE"
Found iBFT Initiator 0:
Flags = 0x3, valid, boot selected
iSNS = 0.0.0.0
SLP = 0.0.0.0
Radius = 0.0.0.0, 0.0.0.0
Name = iqn.2000-09.org.etherboot:UNKNOWN
Found iBFT NIC 0:
Flags = 0x3, valid, boot selected
IP = 172.16.0.247/24
Origin = 0
Gateway = 172.16.0.10
DNS = 0.0.0.0, 0.0.0.0
DHCP = 0.0.0.0
VLAN = 0000
MAC = 00:1b:21:3e:98:ac
PCI = 04:00.0
Hostname =
Found iBFT target 0:
Flags = 0x3, valid, boot selected
IP = 172.16.0.10
Port = 3260
LUN = 0000-0000-0000-0000
CHAP type = 0 (None)
NIC = 0
Name = iqn.2003-10.com.riverbed:default-target
CHAP name =
CHAP secret =
Reverse CHAP name =
Reverse CHAP secret =
No sBFT found
Attempting SAN boot; will wait for system disk
iBFT requested
iBFT requested
Found iSCSI Boot Parameters at 89B9A9F0, attempting iSCSI boot
Allocating the Boot Connection Pool of size 30
Allocating Connection Pool 89BF3D50
Allocating the Boot Connection Pool entry 0 SUCCESS
Allocating the Boot Connection Pool entry 1 SUCCESS
Allocating the Boot Connection Pool entry 2 SUCCESS
Allocating the Boot Connection Pool entry 3 SUCCESS
Allocating the Boot Connection Pool entry 4 SUCCESS
Allocating the Boot Connection Pool entry 5 SUCCESS
Allocating the Boot Connection Pool entry 6 SUCCESS
Allocating the Boot Connection Pool entry 7 SUCCESS
Allocating the Boot Connection Pool entry 8 SUCCESS
Allocating the Boot Connection Pool entry 9 SUCCESS
Allocating the Boot Connection Pool entry 10 SUCCESS
Allocating the Boot Connection Pool entry 11 SUCCESS
Allocating the Boot Connection Pool entry 12 SUCCESS
Allocating the Boot Connection Pool entry 13 SUCCESS
Allocating the Boot Connection Pool entry 14 SUCCESS
Allocating the Boot Connection Pool entry 15 SUCCESS
Allocating the Boot Connection Pool entry 16 SUCCESS
Allocating the Boot Connection Pool entry 17 SUCCESS
Allocating the Boot Connection Pool entry 18 SUCCESS
Allocating the Boot Connection Pool entry 19 SUCCESS
Allocating the Boot Connection Pool entry 20 SUCCESS
Allocating the Boot Connection Pool entry 21 SUCCESS
Allocating the Boot Connection Pool entry 22 SUCCESS
Allocating the Boot Connection Pool entry 23 SUCCESS
Allocating the Boot Connection Pool entry 24 SUCCESS
Allocating the Boot Connection Pool entry 25 SUCCESS
Allocating the Boot Connection Pool entry 26 SUCCESS
Allocating the Boot Connection Pool entry 27 SUCCESS
Allocating the Boot Connection Pool entry 28 SUCCESS
Allocating the Boot Connection Pool entry 29 SUCCESS
iSpSystemWorkerThread: Entering
Waiting 60 seconds for boot disk
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B89B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B89B70
Using Connection 89BF38B8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF38B8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF38B8
Using Connection 89B40198 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworaer: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B40198
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B40198
Using Connection 89B3F200 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3F200
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3F200
Using Connection 89B3EB28 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3EB28
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3EB28
Using Connection 89B3E390 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: EConnint Sn sinish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3E390
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3E390
Using Connection 89B3DB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3DB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3DB70
Using Connection 89BD29A8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BD29A8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BD29A8
Using Connection 89BB3B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB3B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB3B70
Using Connection 89BB2B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworailed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB2B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB2B70
Using Connection 89BB1B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB1B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB1B70
Using Connection 89BAA290 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BAA290
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BAA290
Using Connection 89B3F200 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3F200
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3F200
Using Connection 89B3D440 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3D440
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3D440
Using Connection 89BCF008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BCF008
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BCF008
Using Connection 89BF8008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF8008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF8008
Using Connection 89B72008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B72008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B72008
Using Connection 89B9A008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B9A008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B9A008
Using Connection 89B71008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B71008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B71008
Using Connection 89BB4008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB4008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB4008
Using Connection 89BF7008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF7008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF7008
Using Connection 89BF6008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF6008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF6008
Using Connection 89BB3008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB3008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB3008
Using Connection 89BB2008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB2008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB2008
Using Connection 89B9B008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B9B008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B9B008
Using Connection 89B89008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B89008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B89008
Using Connection 89B89668 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Enterecg Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B89668
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B89668
Using Connection 89B3C008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3C008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3C008
Using Connection 89B3CB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3CB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3CB70
Using Connection 89B3C6D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3C6D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3C6D8
Using Connection 89B3B008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3B008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3B008
Using Connection 89B3BB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3BB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3BB70
Using Connection 89B3B6D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3B6D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3B6D8
Using Connection 89B3A008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3A008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3A008
Using Connection 89B3AB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3AB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3AB70
Using Connection 89B3A6D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3A6D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3A6D8
Using Connection 89B39008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B39008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B39008
Using Connection 89B39B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B39B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B39B70
Using Connection 89B396D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B396D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B396D8
Using Connection 89B38008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B38008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B38008
Using Connection 89B38B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B38B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B38B70
Using Connection 89B386D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B386D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B386D8
Using Connection 89B37008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B37008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B37008
Using Connection 89B37B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B37B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B37B70
Using Connection 89B376D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B376D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B376D8
Using Connection 89B36008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B36008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B36008
Using Connection 89B36B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B36B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B36B70
Using Connection 89B366D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B366D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B366D8
Using Connection 89B35008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B35008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B35008
Using Connection 89BF8008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF8008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF8008
Using Connection 89B72008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B72008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B72008
Using Connection 89B71008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B71008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B71008
Using Connection 89BB4008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB4008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB4008
Using Connection 89BF7008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF7008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF7008
Using Connection 89B89008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B89008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B89008
Using Connection 89BF6008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BF6008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BF6008
Using Connection 89B9B008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B9B008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B9B008
Using Connection 89BB2B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB2B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB2B70
Using Connection 89BB1B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB1B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB1B70
Using Connection 89B36008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B36008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B36008
Using Connection 89BAA290 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BAA290
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Timeout waiting for Disk to arrive.......
Delay 10 seconds for Disk to arrive.......
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BAA290
Using Connection 89B3F200 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3F200
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3F200
Using Connection 89B9A008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B9A008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B9A008
Using Connection 89B89668 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B89668
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B89668
Using Connection 89B3E3B8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3E3B8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3E3B8
Using Connection 89B3EB28 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3EB28
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3EB28
Using Connection 89BCF008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BCF008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BCF008
Using Connection 89BB3008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB3008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB3008
Using Connection 89BB2008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89BB2008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89BB2008
Using Connection 89B35B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B35B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B35B70
Using Connection 89B356D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B356D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Delay for Disk Complete, continue with boot
ISCSI Boot Status 0, (0, 0, 0, 0)
StartIO: No Device for 89B4F000 (a0)
StartIO: No Device for 89B4F000 (12)
Waiting for SAN system disk (attempt 1)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B356D8
Using Connection 89B3DB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3DB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 2)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3DB70
Using Connection 89B3C008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3C008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 3)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3C008
Using Connection 89B3CB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3CB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 4)
System disk is <unknown>, boot disk is <unknown>
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3CB70
Using Connection 89B3C6D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3C6D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3C6D8
Using Connection 89B34008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B34008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 5)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B34008
Using Connection 89B34B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session = 89B4F00089B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B34B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 6)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B34B70
Using Connection 89B346D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B346D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 7)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B346D8
Using Connection 89B3B008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3B008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 8)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3B008
Using Connection 89B3BB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3BB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 9)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3BB70
Using Connection 89B3B6D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3B6D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 10)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3B6D8
Using Connection 89B33008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B33008
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 11)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B33008
Using Connection 89B33B70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B33B70
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 12)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B33B70
Using Connection 89B336D8 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B336D8
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 13)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B336D8
Using Connection 89B3A008 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3A008
iSpSystemWorkerThread: After Logon Completion Thread
iSpSystemWorkerThread: Failed Connection finish 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 14)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3A008
Using Connection 89B3AB70 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpBootConnectionPoolworker: Entering Session =
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3AB70
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3AB70
Using Connection 89B3A5B0 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B3A5B0
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 15)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B3A5B0
Using Connection 89B39A48 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B39A48
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 16)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034): "\??\IDE#DiskST3250310NS_____________________________SN04____#5&2a36c317&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Disk unavailable (c0000034): "\??\USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_2.0&Rev_1.00#001372982F25C03046405236&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Reinstate Failed Connection 89B39A48
Using Connection 89B39318 index = 0 for Boot Session 89B4F000
Queue a WorkItem to create connections for Boot Session 89B4F000
iSpSystemWorkerThread: Failed Connection finish
iSpSystemWorkerThread: Coming out of wait
iSpSystemWorkerThread: Start Logon Completion Thread 89B39318
iSpSystemWorkerThread: After Logon Completion Thread
iSpBootConnectionPoolworker: Entering Session = 89B4F000
iSpBootConnectionPoolworker: Exit Session = 89B4F000
Waiting for SAN system disk (attempt 17)
System disk...
[truncated message content] |
|
From: Vivek S. <vi...@ch...> - 2011-02-03 07:52:25
|
Hi guys, I would like to know when the next version of gPXE (v1.0.2) with fix http://www.mail-archive.com/gp...@et.../msg01465.html will be released. Our option ROM is dependent on this fix. Kindly reply. Thank you, Vivek S |
|
From: Marty C. <md...@et...> - 2011-01-28 12:53:55
|
Hello Everyone, This is a brief message to let you know that we are working on getting etherboot.org and rom-o-matic.net back up as soon as possible. Over the years we have been fortunate to have so very little downtime, and we have made sure that we do nightly backups so that we can recover from problems. Our data and history are secure. Thanks to those of you who have offered support to help us get things working again. It means a lot to me. We're working with the great folks at http://osuosl.org/ (who rock!) and who host our servers to help us migrate onto new hardware. I'll keep you updated on how things are going. Feel free to ask questions and offer ideas, and let's talk. I remember a time before rom-o-matic.net, and before we had so many users and services. This downtime has reminded me how far we've come over the 11 years since I joined the project, and how fortunate we are to have each other. Let's take this time to reflect, as we find our way forward. With a grateful heart, / Marty / |
|
From: nicopsycho <nic...@gm...> - 2011-01-14 16:31:45
|
Hi, I'm new to discuss list so, please be kind ^^ The network setup, composed of 3 distinct machines: 1/ a DHCP server with no boot option (no 66 or 67) aka the real DHCP 2/ a DHCP gateway which patches the answers of the DHCP with boot options (option 67 boot file name and next-server) aka the gateway 3/ a target DELL GX280 aka the client Restriction: - I would like to make this work and most of all avoid modifying the real DHCP config, and NOT using the native/onboard PXE rom. What works: - Using the PXE native boot on the client. Boots, uses the answer from the gateway because it contains the boot informations, ignores the answer from the real DHCP. OK. - Using the gPXE on the client, modifying the real DHCP adding the next-server and boot filename options. Boots, gets the info from the real DHCP. OK. What fails: - Using gPXE on the client, put the real DHCP back to its original state (no boot options). Boots, gets the info from the real DHCP (no boot options), fails with "no root path or filename". FAIL. Captured the frames in promiscous mode on the gateway, the real DHCP answer has no boot info, but the gateway answer does. gPXE versions used: from rom-o-matic, latest, 1.0.1, 1.0.0, from git repo, compiled latest. medium used: iso for CDROM, burnt on CD-RW. The problem/bug? The gPXE does not seem to ignore the real DHCP answer even thought it does not contain boot info, the very next answer on the network does contain boot info but gPXE does not seem to go that far. From what i understand gPXE is supposed to use a valid answer, and valid would be with boot info. From the website documention for etherboot/gpxe there was an option -DREQUIRE_VCI_ETHERBOOT and -DALLOW_ONLY_ENCAPSULATED but after a while I realised it was only for etherboot, not gPXE. This doc was from 2003... Even though I thought I should give a shot and that those options were somehow present as a default in gPXE, at least for the VCI_ETHERBOOT one... So I added the described options in the gateway answer, meaning adding option 43 with as value: option 60 9 in length and Etherboot as message... (option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff; from the online documentation at http://etherboot.org/wiki/usermanual?s[]=compilation&s[]=options#require_vci_etherboot) The option I added is present in my WireShark capture but made no difference... Is there a way to ensure gPXE uses the answer with the boot info and skip the (first) one which does not have them? Like a real PXE rom? I have been to the #Etherboot channel asking all this, and the feedback was that it might be a bug... but again it was not a developer... Any suggestion? |
|
From: Chin Li C. <max...@gm...> - 2010-12-18 08:51:50
|
Hi, Thanks for your reply. I'm attempting to boot several Windows PCs using the same image by using AOE. In my country (Malaysia) there is actually alot of similar solution (PXE base) but majority of them are Windows server base. I'm finding solution on Linux server base that's what AoE pop out when i tried googling around. I'm still researching around internet without implementing. If someone with experience can point me more information that will be very helpful. Thanks & regards, Max Chock. On Sat, Dec 18, 2010 at 4:04 PM, Robert Jordan < rj...@im...> wrote: > Can you expand upon your question a bit? Are you attempting to boot > several Windows PCs using the same image via iSCSI? If so I have done quite > a bit of work in this area and can say that for most environments it is not > possible to get a satisfactory result. > > On Dec 17, 2010, at 11:36 PM, Chin Li Chock wrote: > > > Hi all, > > > > I'm very new to etherboot and i'm thinking to implement the system into > my cyber cafe and the client is using XP server is using linux. > > > > One thing I can't find any useful information on the web is about > assigning individual "Computer Name" for multiple PC environment. Can > someone here help to point out a solution or another website? > > > > Thanks & regards, > > Max Chock. > > > ------------------------------------------------------------------------------ > > Lotusphere 2011 > > Register now for Lotusphere 2011 and learn how > > to connect the dots, take your collaborative environment > > to the next level, and enter the era of Social Business. > > > http://p.sf.net/sfu/lotusphere-d2d_______________________________________________ > > Etherboot-discuss mailing list > > Eth...@li... > > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Robert J. <rj...@im...> - 2010-12-18 08:35:07
|
Can you expand upon your question a bit? Are you attempting to boot several Windows PCs using the same image via iSCSI? If so I have done quite a bit of work in this area and can say that for most environments it is not possible to get a satisfactory result. On Dec 17, 2010, at 11:36 PM, Chin Li Chock wrote: > Hi all, > > I'm very new to etherboot and i'm thinking to implement the system into my cyber cafe and the client is using XP server is using linux. > > One thing I can't find any useful information on the web is about assigning individual "Computer Name" for multiple PC environment. Can someone here help to point out a solution or another website? > > Thanks & regards, > Max Chock. > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d_______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss |
|
From: Michael H. <iti...@gm...> - 2010-12-18 08:26:47
|
Hi Chin Li, You can certainly do what you are thinking of, but you need to base each image on the MAC address of the NIC rather than the hostname of the OS. From how I understand PXE, a client will look for a file in your /var/lib/tftpboot/pxelinux.cfg directory that is a match for its MAC address. So if you generate a unique file for each client and name the files using the MAC address, each workstation will boot its pre-determined image. More on this is near the end of this post: http://www.debian-administration.org/articles/478 In the example on that page a sample boot looks like this: Trying to load: pxelinux.cfg/01-00-14-22-a1-53-85 Trying to load: pxelinux.cfg/C0A80146 Trying to load: pxelinux.cfg/C0A8014 Trying to load: pxelinux.cfg/C0A801 Trying to load: pxelinux.cfg/C0A80 Trying to load: pxelinux.cfg/C0A8 Trying to load: pxelinux.cfg/C0A Trying to load: pxelinux.cfg/C0 Trying to load: pxelinux.cfg/C Trying to load: pxelinux.cfg/default So your 'default' file would contain a generic boot image (maybe a Linux diagnostics utility), and the full MAC addresses would be matched up with the configuration files you created for each client. It drops a character from the MAC address each time in case you want to use a specific image on certain types of hardware. Good luck! On Sat, Dec 18, 2010 at 1:36 AM, Chin Li Chock <max...@gm...> wrote: > Hi all, > I'm very new to etherboot and i'm thinking to implement the system into my > cyber cafe and the client is using XP server is using linux. > One thing I can't find any useful information on the web is about assigning > individual "Computer Name" for multiple PC environment. Can someone here > help to point out a solution or another website? > Thanks & regards, > Max Chock. > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Etherboot-discuss mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-discuss > > |
|
From: Chin Li C. <max...@gm...> - 2010-12-18 07:36:36
|
Hi all, I'm very new to etherboot and i'm thinking to implement the system into my cyber cafe and the client is using XP server is using linux. One thing I can't find any useful information on the web is about assigning individual "Computer Name" for multiple PC environment. Can someone here help to point out a solution or another website? Thanks & regards, Max Chock. |
25 messages has been excluded from this view by a project administrator.
