Booting problem with XP / DOS

[Ixcoatl Perez]

Hi,

I am the administrator of a scholar network with 30 PCs.
My intention was to take away the hard disks (that fail a lot) of the
computers and use a dedicated iscsi server, but im having
trouble booting any OS.

The server has Ubuntu Jaunty on it, and the version of iscsi-target is 0.4.16.

I followed the instructions at:

http://etherboot.org/wiki/sanboot/winxp

To install Windows XP from SAN.

I installed Windows XP in a QEMU box with a 3GB drive following the instructions of the guide.
The default network card on QEMU RTL8029 was configured for dhcp.
I extracted the partition image from the hard drive image as said in the guide and configured my
dhcpd and etd servers like this (only relevant parts are shown):

/etc/ietd.conf

Target iqn.2009-09.winxp1:iscsiboot
Lun 0 Path=/home/ixcoatl/Documents/boot/gPXE/imagenes/partWinXP,Type=fileio


/etc/dhcp3/dhcpd.conf

subnet 192.168.1.0 netmask 255.255.255.0
{
range 192.168.1.30 192.168.1.50;
option subnet-mask 255.255.255.0;
option routers 192.168.1.254;
filename "";
option root-path "iscsi:192.168.1.4::::iqn.2009-09.winxp1:iscsiboot";
default-lease-time 600;
max-lease-time 7200;
}


When I boot the real diskless computer with a gPXE-USB I get something like:

gPXE initialising devices ...

gPXE 0.9.7+ -- Open Source Boot Firmware -- http://etherboot.org
Features: HTTP DNS TFTP AoE iSCSI bzImage COMBOOT ELF Multiboot PXE PXEXT

net0: 00:a1:b0:25:51:e3 on PCI01:02.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 00:a1:b0:25:51:e3).... ok
net0: 192.168.1.32/255.255.255.0 gw 192.168.1.254
Booting from root path "iscsi:192.168.1.4::::iqn.2009-09.winxp1:iscsiboot"
iSCSI booting from iscsi:192.168.1.4::::iqn.2009-09.winxp1:iscsiboot
Registered as BIOS drive 0x80
Booting from BIOS drive 0x80

Error de disco

Those 2 words at the end means 'Disk error' isn sapnish and I guess they are
comming from Windows.

As far as I see the DHCP part is running fine and the network is configured correctly.
The OS (or part of it) is also loaded, and then it has trouble communicating with the
iSCSI disk.

Do I'm missing something? I watched the video of a conference with the developers
and got the impresion that the BIOS interrupts are intercepted so the the OS thinks
that there is real disk attached to the computer, so I tried with a MSDOS image instead of
the Windows one and got the same error ("Disk I/O error, insert a disk and press enter to
continue"). If my understanding of the technology was right, MSDOS shouldnt have any
trouble booting since it uses the bios interrupts, right? Or maybe the scisi emuation needs
some drivers to be loaded with DOS?

Does it has to do with the fact that QEMU has a different network card than the
real computer?

Any help will be greatly appreciated!
Tank you in advance and sorry for my bad english.


Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Miller, Shao]

Good day Ixcoatl Perez,

Concerning your process for SAN-booting Windows XP:

You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.

You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.

HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?

DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

Good luck!

- Shao Miller

[Ixcoatl Perez]

Hi,

Well, I have installed XP in a real computer with all the iSCSI software on it, network and even firefox. Then I extracted an image of the disk and tried to boot it. No luck, but this time the computer starts beeping a few seconds after the "Booting from BIOS drive 0x80" message shows.

Then I realized that the real disk was connected to the server and tried the following ietd.conf configuration:

Target iqn.2009-09.winxp01:iscsiboot
Lun 0 Path=/dev/sdd,Type=fileio

(Note that I intentionaly changed the 'winxp01' from the 'winxp1' on my later post, and that change was also reflected in the dhcp config file)
And got exactly the same result, so I guess that the image/disk portion is ok.

Asumming that the DHCP portion is also fine, my first conclusion was that the iSCSI system was the one to blame.

I have compiled and installed the latest version of iSCSI target available form here:

http://developer.berlios.de/svn/?group_id=5404

But no luck, just the exact same result.

To prove that the iSCSI system was broken I put the M$ software on my laptop and tried to access the shared drive, to my surprise everytnig worked JUST FINE! So, I guess that my configuration is the broken part and Im the only one to blame. :S

So here it is again, I dont have a DNS in my network so all my computers are known only by their IPs:

ietd.conf:

Target iqn.2009-09.winxp01:iscsiboot
Lun 0 Path=/dev/sdd,Type=fileio

dhcpd.conf:

subnet 192.168.1.0 netmask 255.255.255.0
{
range 192.168.1.30 192.168.1.50;
option subnet-mask 255.255.255.0;
option routers 192.168.1.254;
# filename "http://192.168.1.4:8080/boot/partWinXP";
filename "";
option root-path "iscsi:192.168.1.4::::iqn.2009-09.winxp01:iscsiboot";
default-lease-time 600;
max-lease-time 7200;
}

The most suspicious part to me is:
option root-path "iscsi:192.168.1.4::::iqn.2009-09.winxp01:iscsiboot";

Do you see anyting wrong on it?


By the way, is there a way to check what is the iscsi-target server doing? I was unable to find any logs, except some entries at the messages and kernel files with stuff like this:

Aug 30 19:53:04 topi kernel: [ 4483.104866] iSCSI Enterprise Target Software - version 0.4.17
Aug 30 19:53:04 topi kernel: [ 4483.104944] iscsi_trgt: Registered io type fileio
Aug 30 19:53:04 topi kernel: [ 4483.104946] iscsi_trgt: Registered io type blockio
Aug 30 19:53:04 topi kernel: [ 4483.104948] iscsi_trgt: Registered io type nullio

Do you have any ideas?

Thank you and best regards!







________________________________
De: "Miller, Shao" <***@yrdsb.edu.on.ca>
Para: Ixcoatl Perez <***@yahoo.com.mx>
CC: etherboot-***@lists.sourceforge.net
Enviado: domingo, 30 de agosto, 2009 11:24:50
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Good day Ixcoatl Perez,

Concerning your process for SAN-booting Windows XP:

You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.

You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.

HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?

DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

Good luck!

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Geert Stappers]

Post by Miller, Shao
Good day Ixcoatl Perez,
You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.
You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.
HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?
DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

A driver for the NIC, Network Interface Card, should also be installed.



Cheers
Geert Stappers

[Ixcoatl Perez]

The NIC driver is installed. Its configured with DHCP and all the
bnetwork values are correct, I can browse the LAN and internet
with no problem.

Ix




________________________________
De: Geert Stappers <***@stappers.nl>
Para: etherboot-***@lists.sourceforge.net
Enviado: domingo, 30 de agosto, 2009 12:42:07
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Post by Miller, Shao
Good day Ixcoatl Perez,
You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.
You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.
HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?
DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

A driver for the NIC, Network Interface Card, should also be installed.



Cheers
Geert Stappers


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Ixcoatl Perez]

Regarding the image configuration, I followed the instructions

in the page.

fdisk -lu gives me the following info:

You must set cylinders.
You can do this from the extra functions menu.

Disk winXPimg: 0 MB, 0 bytes
128 heads, 63 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xee54ee54

Device Boot Start End Blocks Id System
winXPimg1 * 63 6128639 3064288+ b W95 FAT32

I guess the image has a mbr beacuse it boots from QEMU.
It would be nice to have a small image with some OS at the
etherboot page to test the network configuration before trying
something bigger.

The blue screen of dead you describe would be a big progress
right now =D.

I'll try to install xp in a real disk at the client machine now.

Thank you





________________________________
De: "Miller, Shao" <***@yrdsb.edu.on.ca>
Para: Ixcoatl Perez <***@yahoo.com.mx>
CC: etherboot-***@lists.sourceforge.net
Enviado: domingo, 30 de agosto, 2009 11:24:50
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Good day Ixcoatl Perez,

Concerning your process for SAN-booting Windows XP:

You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.

You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.

HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?

DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

Good luck!

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Ixcoatl Perez]

Hi,

After a 4 hour long conversation with Shao, who kindly helped me to
put this whole thing together, we got to boot XP from the iSCSI
drive using very hard core gPXE hacking (or it was for me), but , at the time
we finish our session, XP refused to boot in the standard gPXE installation.

However, five minutes later I got to make it boot. I'm not sure what happened
but here is what we did among those 4 hours:

1) Shao, kindly, sent me several MBRs that I put in the XP drive during the process.
Lastly, I restored the original one before trying to boot.

2) It came to our notice, while we were testing stuff, that my DNS
configuration was not working from dhcp, so I added the configuration at
the dhcpd.conf file to make it work.

3) I removed a suspicious NIC on the client machine and changed the cable to
the other one.

4) In my ietd.conf, I changed the configuration option
Type=fileio
to
Type=blockio

At last the whole thing looks like:

Target iqn.2009-09.winxp01:iscsiboot
Lun 0 Path=/dev/sdd,Type=blockio

5) Shao told me that my booting problem was mostly because the boot record of
the XP partition was incorrect, and pointed me to use FIXBOOT
and FIXMBR from the Windows Recovery Console. However I never got
to use that.We boot XP (or a portion of it) using grub4dos, maybe XP somehow
autocorrected its boot record while booting.


Now Im stuck with the bsod, but that's windows configuration stuff that I will
try to solve tomorrow. My guess is that it has to do with the fact that I took one
NIC away. I will try re installing the whole windows thing with only one NIC
this time to see what happends.

Best regards.






________________________________
De: "Miller, Shao" <***@yrdsb.edu.on.ca>
Para: Ixcoatl Perez <***@yahoo.com.mx>
CC: etherboot-***@lists.sourceforge.net
Enviado: domingo, 30 de agosto, 2009 11:24:50
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Good day Ixcoatl Perez,

Concerning your process for SAN-booting Windows XP:

You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.

You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.

HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?

DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

Good luck!

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss



¡Obtén la mejor experiencia en la web! Descarga gratis el nuevo Internet Explorer 8. http://downloads.yahoo.com/ieak8/?l=mx

[Ixcoatl Perez]

Strill trying to pass the BSOD, this is my windbg dump, any ideas?

------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com18
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Mon Aug 31 18:40:30.968 2009 (GMT-5)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
nt!DbgBreakPoint:
804e30c8 cc int 3
kd> g

*** Fatal System Error: 0x0000007b
(0xF789E524,0xC0000034,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target at (Mon Aug 31 18:41:54.687 2009 (GMT-5)), ptr64 FALSE
Loading Kernel Symbols
................................
Loading User Symbols

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7B, {f789e524, c0000034, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!IopMarkBootPartition+113 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
804e30d9 cc int 3
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from which
the boot was being attempted. In the latter case, the argument (#1) is the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on ARC
systems setup must be run. See the "Advanced Server System Administrator's
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f789e524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7B

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80536753 to 804e30d9

STACK_TEXT:
f789e08c 80536753 00000003 f789e3e8 00000000 nt!RtlpBreakWithStatusInstruction
f789e0d8 8053721e 00000003 00000000 80083000 nt!KiBugCheckDebugBreak+0x19
f789e4b8 80537832 0000007b f789e524 c0000034 nt!KeBugCheck2+0x574
f789e4d8 806ce5b4 0000007b f789e524 c0000034 nt!KeBugCheckEx+0x1b
f789e640 806bcefb 80083000 00000000 80083000 nt!IopMarkBootPartition+0x113
f789e690 806b2f69 80083000 f789e6ac 00034000 nt!IopInitializeBootDrivers+0x4ba
f789e838 806b3fea 80083000 00000000 89f67548 nt!IoInitSystem+0x712
f789edac 80576b24 80083000 00000000 00000000 nt!Phase1Initialization+0xac7
f789eddc 804eed86 806b3797 80083000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IopMarkBootPartition+113
806ce5b4 8d85e4feffff lea eax,[ebp-11Ch]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!IopMarkBootPartition+113

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

FAILURE_BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113

BUCKET_ID: 0x7B_nt!IopMarkBootPartition+113

Followup: MachineOwner
---------





________________________________
De: Ixcoatl Perez <***@yahoo.com.mx>
Para: etherboot-***@lists.sourceforge.net
Enviado: lunes, 31 de agosto, 2009 3:14:15
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS


Hi,

After a 4 hour long conversation with Shao, who kindly helped me to
put this whole thing together, we got to boot XP from the iSCSI
drive using very hard core gPXE hacking (or it was for me), but , at the time
we finish our session, XP refused to boot in the standard gPXE installation.

However, five minutes later I got to make it boot. I'm not sure what happened
but here is what we did among those 4 hours:

1) Shao, kindly, sent me several MBRs that I put in the XP drive during the process.
Lastly, I restored the original one before trying to boot.

2) It came to our notice, while we were testing stuff, that my DNS
configuration was not working from dhcp, so I added the configuration at
the dhcpd.conf file to make it work.

3) I removed a suspicious NIC on the client machine and changed the cable to
the other one.

4) In my ietd.conf, I changed the configuration option
Type=fileio
to
Type=blockio

At last the whole thing looks like:

Target iqn.2009-09.winxp01:iscsiboot
Lun 0 Path=/dev/sdd,Type=blockio

5) Shao told me that my booting problem was mostly because the boot record of
the XP partition was incorrect, and pointed me to use FIXBOOT
and FIXMBR from the Windows Recovery Console. However I never got
to use that. We boot XP (or a portion of it) using grub4dos, maybe XP somehow
autocorrected its boot record while booting.


Now Im stuck with the bsod, but that's windows configuration stuff that I will
try to solve tomorrow. My guess is that it has to do with the fact that I took one
NIC away. I will try re installing the whole windows thing with only one NIC
this time to see what happends.

Best regards.






________________________________
De: "Miller, Shao" <***@yrdsb.edu.on.ca>
Para: Ixcoatl Perez <***@yahoo.com.mx>
CC: etherboot-***@lists.sourceforge.net
Enviado: domingo, 30 de agosto, 2009 11:24:50
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Good day Ixcoatl Perez,

Concerning your process for SAN-booting Windows XP:

You should be installing Windows XP on the actual target hardware that
will be SAN-booting. QEmu has different hardware (including different
NIC) than your real hardware, so three things could potentially prevent
the OS from fully booting: HAL, kernel, NIC. The symptom of this would
be a "Blue Screen of Death" with number 0x0000007B.

You would be better off installing to the actual target hardware. If
you have multiple model types, you will be better off installing to each
one and having an "image" for each model-type.

HOWEVER, it doesn't appear that you have gotten that far. Your initial
SAN-boot seems to fail. Some things to think about: Does the SAN have
an MBR (with boot-code and partition table and an active partition)?
Did you copy the whole disk (correct) or just the partition (incorrect)?
Are you able to attach to this SAN from some other running OS on the
same network and take a look at the disk?

DOS certainly does not require a driver. INT 0x13 is hooked. A guess
would be that you copied the partition, instead of the disk, or that
QEmu disk geometry is somehow messing things up.

Good luck!

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

________________________________

¡Encuentra las mejores recetas
con Yahoo! Cocina!
http://mx.mujer.yahoo.com/cocina/


Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Michael Brown]

Post by Ixcoatl Perez
Strill trying to pass the BSOD, this is my windbg dump, any ideas?
<snip>

It looks as though you do not have sanbootconf installed.

Michael

[Ixcoatl Perez]

I do have sanbootconf installed but it seems that its not doing what it has to do.

Is there a way to check that the installation of sanbootconf was performed properly?
As far as I understand, sanbootconf makes XP start some processes before others to
put up the iscsi link. Is there a way to debug that? Maybe the XP boot log?
Is there a page/document explaining the XP sanbooting in some more detail?

Thank you and best regards
Ix




________________________________
De: Michael Brown <***@fensystems.co.uk>
Para: etherboot-***@lists.sourceforge.net
CC: Ixcoatl Perez <***@yahoo.com.mx>
Enviado: martes, 1 de septiembre, 2009 3:53:51
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Post by Ixcoatl Perez
Strill trying to pass the BSOD, this is my windbg dump, any ideas?
<snip>

It looks as though you do not have sanbootconf installed.

Michael



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Ixcoatl Perez]

Do you think that the fact that the installation I'm running is
in spanish can be causing this behavior?

Later I will reinstall the OS in english and se what happens.

Greetings!





________________________________
De: Michael Brown <***@fensystems.co.uk>
Para: etherboot-***@lists.sourceforge.net
CC: Ixcoatl Perez <***@yahoo.com.mx>
Enviado: martes, 1 de septiembre, 2009 20:38:24
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Post by Ixcoatl Perez
I do have sanbootconf installed but it seems that its not doing what it has to do.
Is there a way to check that the installation of sanbootconf was performed
properly? As far as I understand, sanbootconf makes XP start some processes
before others to put up the iscsi link. Is there a way to debug that? Maybe
the XP boot log? Is there a page/document explaining the XP sanbooting in
some more detail?

sanbootconf is pretty verbose in its debug log, which you would be able to see
via your windbg session. From the fact that no messages appear, I would
guess it is not (properly) installed.

Michael



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Ixcoatl Perez]

Still no luck booting XP.

When booting from the harddisk the client computer gives me:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com18
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Wed Sep 2 15:21:25.328 2009 (GMT-5)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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
iSCSI Boot Parameter Driver initialising
No iBFT found
iscsidsc: Error 2 reading group key from registry
iScsiDsc: ExecMethod(ea4d82bf-29da-4e12-80ae5437964462c, 92) failed 1
iscsidsc: Root\SCSIADAPTER\0000_0 returned 0x1 for SetInitiatorNodeName
iscsidsc: Root\SCSIADAPTER\0000_0 (005B43B0) SetCHAPSharedSecret succeeeded
iscsidsc: SetupDiEnumDeviceInterfaces(1) failed 259
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5


Any ideas?

Greetings!



________________________________
De: Ixcoatl Perez <***@yahoo.com.mx>
Para: etherboot-***@lists.sourceforge.net
Enviado: martes, 1 de septiembre, 2009 20:52:20
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS


Do you think that the fact that the installation I'm running is
in spanish can be causing this behavior?

Later I will reinstall the OS in english and se what happens.

Greetings!





________________________________
De: Michael Brown <***@fensystems.co.uk>
Para: etherboot-***@lists.sourceforge.net
CC: Ixcoatl Perez <***@yahoo.com.mx>
Enviado: martes, 1 de septiembre, 2009 20:38:24
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Post by Ixcoatl Perez
I do have sanbootconf installed but it seems that its not doing what it has to do.
Is there a way to check that the installation of sanbootconf was performed
properly? As far as I understand, sanbootconf makes XP start some processes
before others to put up the iscsi link. Is there a way to debug that? Maybe
the XP boot log? Is there a page/document explaining the XP sanbooting in
some more detail?

sanbootconf is pretty verbose in its debug log, which you would be able to see
via your windbg session. From the fact that no messages appear, I would
guess it is not (properly) installed.

Michael

________________________________

¡Encuentra las mejores recetas
con Yahoo! Cocina!
http://mx.mujer.yahoo.com/cocina/


Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Ixcoatl Perez]

This is a harddisk XP boot in the client computer:
(after I put XP in english on it)

 Service Pack 3 9  2 2009 15:21:28.359
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver pciide.sys
Loaded driver \WINDOWS\system32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver PartMgr.sys
Loaded driver VolSnap.sys
Loaded driver NDIS.sys
Loaded driver RTL8139.SYS
Loaded driver KSecDD.sys
Loaded driver ipsec.sys
Loaded driver msgpc.sys
Loaded driver \WINDOWS\system32\DRIVERS\TDI.SYS
Loaded driver tcpip.sys
Loaded driver psched.sys
Loaded driver atapi.sys
Loaded driver disk.sys
Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
Loaded driver fltMgr.sys
Loaded driver sr.sys
Loaded driver Fastfat.sys
Loaded driver Mup.sys
Loaded driver msiscsi.sys
Loaded driver \WINDOWS\system32\DRIVERS\iscsiprt.sys
Did not load driver \SystemRoot\system32\DRIVERS\msgpc.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\system32\DRIVERS\intelppm.sys
Loaded driver \SystemRoot\system32\DRIVERS\HDAudBus.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\system32\DRIVERS\parport.sys
Loaded driver \SystemRoot\system32\DRIVERS\imapi.sys
Loaded driver \SystemRoot\system32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\system32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\system32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\system32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspppoe.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\system32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\system32\DRIVERS\rdpdr.sys
Loaded driver \SystemRoot\system32\DRIVERS\termdd.sys
Loaded driver \SystemRoot\system32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\system32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\system32\DRIVERS\update.sys
Loaded driver \SystemRoot\system32\DRIVERS\mssmbios.sys
Loaded driver \SystemRoot\system32\DRIVERS\iscsiboot.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbhub.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\system32\DRIVERS\wanarp.sys
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Fdc.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\Drivers\Beep.SYS
Loaded driver \SystemRoot\system32\DRIVERS\netbt.sys
Did not load driver \SystemRoot\System32\Drivers\Flpydisk.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Did not load driver \SystemRoot\System32\Drivers\i8042prt.SYS
Did not load driver \SystemRoot\system32\DRIVERS\kbdhid.sys
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \SystemRoot\system32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\system32\DRIVERS\serial.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Loaded driver \SystemRoot\system32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\system32\DRIVERS\USBSTOR.SYS
Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\Drivers\Fips.SYS
Loaded driver \SystemRoot\system32\DRIVERS\usbccgp.sys
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\hidusb.sys
Loaded driver \SystemRoot\system32\DRIVERS\kbdhid.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndisuio.sys
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\system32\DRIVERS\mrxdav.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Loaded driver \SystemRoot\system32\DRIVERS\srv.sys
Loaded driver \SystemRoot\system32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\System32\Drivers\HTTP.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouhid.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouhid.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouhid.sys
 Service Pack 3 9  2 2009 16:09:05.375
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver pciide.sys
Loaded driver \WINDOWS\system32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver PartMgr.sys
Loaded driver VolSnap.sys
Loaded driver NDIS.sys
Loaded driver RTL8139.SYS
Loaded driver KSecDD.sys
Loaded driver ipsec.sys
Loaded driver msgpc.sys
Loaded driver \WINDOWS\system32\DRIVERS\TDI.SYS
Loaded driver tcpip.sys
Loaded driver psched.sys
Loaded driver atapi.sys
Loaded driver disk.sys
Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
Loaded driver fltMgr.sys
Loaded driver sr.sys
Loaded driver Fastfat.sys
Loaded driver Mup.sys
Loaded driver msiscsi.sys
Loaded driver \WINDOWS\system32\DRIVERS\iscsiprt.sys
Did not load driver \SystemRoot\system32\DRIVERS\msgpc.sys
Did not load driver \SystemRoot\system32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\system32\DRIVERS\intelppm.sys
Loaded driver \SystemRoot\system32\DRIVERS\HDAudBus.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\system32\DRIVERS\parport.sys
Loaded driver \SystemRoot\system32\DRIVERS\serial.sys
Loaded driver \SystemRoot\system32\DRIVERS\serenum.sys
Loaded driver \SystemRoot\system32\DRIVERS\imapi.sys
Loaded driver \SystemRoot\system32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\system32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\system32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\system32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspppoe.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\system32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\system32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\system32\DRIVERS\rdpdr.sys
Loaded driver \SystemRoot\system32\DRIVERS\termdd.sys
Loaded driver \SystemRoot\system32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\system32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\system32\DRIVERS\update.sys
Loaded driver \SystemRoot\system32\DRIVERS\mssmbios.sys
Loaded driver \SystemRoot\system32\DRIVERS\iscsiboot.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\system32\DRIVERS\wanarp.sys
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\system32\DRIVERS\usbhub.sys
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Fdc.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\Drivers\Beep.SYS
Loaded driver \SystemRoot\system32\DRIVERS\netbt.sys
Did not load driver \SystemRoot\System32\Drivers\Flpydisk.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Did not load driver \SystemRoot\System32\Drivers\i8042prt.SYS
Did not load driver \SystemRoot\system32\DRIVERS\kbdhid.sys
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \SystemRoot\system32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Loaded driver \SystemRoot\system32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\Drivers\Fips.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\USBSTOR.SYS
Loaded driver \SystemRoot\system32\DRIVERS\hidusb.sys
Loaded driver \SystemRoot\system32\DRIVERS\usbccgp.sys
Loaded driver \SystemRoot\system32\DRIVERS\mouhid.sys
Loaded driver \SystemRoot\system32\DRIVERS\kbdhid.sys
Loaded driver \SystemRoot\system32\DRIVERS\ndisuio.sys
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\system32\DRIVERS\mrxdav.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Loaded driver \SystemRoot\system32\DRIVERS\srv.sys
Loaded driver \SystemRoot\system32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\System32\Drivers\HTTP.sys





________________________________
De: Ixcoatl Perez <***@yahoo.com.mx>
Para: etherboot-***@lists.sourceforge.net
Enviado: martes, 1 de septiembre, 2009 20:52:20
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS


Do you think that the fact that the installation I'm running is
in spanish can be causing this behavior?

Later I will reinstall the OS in english and se what happens.

Greetings!





________________________________
De: Michael Brown <***@fensystems.co.uk>
Para: etherboot-***@lists.sourceforge.net
CC: Ixcoatl Perez <***@yahoo.com.mx>
Enviado: martes, 1 de septiembre, 2009 20:38:24
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Post by Ixcoatl Perez
I do have sanbootconf installed but it seems that its not doing what it has to do.
Is there a way to check that the installation of sanbootconf was performed
properly? As far as I understand, sanbootconf makes XP start some processes
before others to put up the iscsi link. Is there a way to debug that? Maybe
the XP boot log? Is there a page/document explaining the XP sanbooting in
some more detail?

sanbootconf is pretty verbose in its debug log, which you would be able to see
via your windbg session.  From the fact that no messages appear, I would
guess it is not (properly) installed.

Michael

________________________________

¡Encuentra las mejores recetas
con Yahoo! Cocina!
http://mx.mujer.yahoo.com/cocina/


Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Miller, Shao]

Good day Ixcoatl,

I am sorry to read that you are still having troubles SAN-booting
Windows XP. As Michael Brown said, there are no messages from the
"sanbootconf" driver in your WinDbg log. Try booting the HDD and
re-installing that package.

Beyond that, also note that you really should be trying to SAN-boot the
very same computer model which the HDD boots in, which I believe you are
aware of and are doing.

If you still do not see messages in the WinDbg log, we'll have to figure
out why. You can do 'sc query iscsiboot' from a Windows CLI ("DOS
window") and e-mail its output.

As for confirmation that the "sanbootconf" package is installed
correctly, please see:
http://www.etherboot.org/wiki/sanboot/winnt_iscsi_sanbootconf

Best of luck.

- Shao Miller

[Ixcoatl Perez]

Hi,

Yesterday I tried to boot with AoE and was a complete success for me,
it worked at my first try with no problem at all.

I still cant boot with iSCSI. I tried reinstalling sanboot-conf with no luck.
Nothing comes out in WinDbg log regarding iSCSI.

I'm open to do any test/configuration that you recommend until this
work.

Best regards!




________________________________
De: "Miller, Shao" <***@yrdsb.edu.on.ca>
Para: Ixcoatl Perez <***@yahoo.com.mx>
CC: etherboot-***@lists.sourceforge.net
Enviado: jueves, 3 de septiembre, 2009 6:57:37
Asunto: Re: [Etherboot-discuss] Booting problem with XP / DOS

Good day Ixcoatl,

I am sorry to read that you are still having troubles SAN-booting
Windows XP. As Michael Brown said, there are no messages from the
"sanbootconf" driver in your WinDbg log. Try booting the HDD and
re-installing that package.

Beyond that, also note that you really should be trying to SAN-boot the
very same computer model which the HDD boots in, which I believe you are
aware of and are doing.

If you still do not see messages in the WinDbg log, we'll have to figure
out why. You can do 'sc query iscsiboot' from a Windows CLI ("DOS
window") and e-mail its output.

As for confirmation that the "sanbootconf" package is installed
correctly, please see:
http://www.etherboot.org/wiki/sanboot/winnt_iscsi_sanbootconf

Best of luck.

- Shao Miller

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss



Encuentra las mejores recetas en Yahoo! Cocina.
http://mx.mujer.yahoo.com/cocina/

[Michael Brown]

Post by Ixcoatl Perez
I do have sanbootconf installed but it seems that its not doing what it has to do.
Is there a way to check that the installation of sanbootconf was performed
properly? As far as I understand, sanbootconf makes XP start some processes
before others to put up the iscsi link. Is there a way to debug that? Maybe
the XP boot log? Is there a page/document explaining the XP sanbooting in
some more detail?

sanbootconf is pretty verbose in its debug log, which you would be able to see
via your windbg session. From the fact that no messages appear, I would
guess it is not (properly) installed.

Michael