Re: Booting problem with XP / DOS

Ixcoatl Perez <[email protected]> Mon, 31 Aug 2009 01:14:15 -0700 (PDT)

Newsgroups	gmane.network.etherboot.user
Message-ID	<[email protected]>

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" <[email protected]>
Para: Ixcoatl Perez <[email protected]>
CC: [email protected]
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
[email protected]
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

_______________________________________________
Etherboot-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss