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 <ixcoatl_perez@...>
Para: etherboot-discuss@...
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" <Shao.Miller@...>
Para: Ixcoatl Perez <ixcoatl_perez@...>
CC: etherboot-discuss@...
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-discuss@...
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/
|