Thanks for the info, Shao
I've followed your advice and checked if sanbootconf driver was loaded, and
it looks like it wasn't. I don't know why this happend, I installed the last
version of sanbootconf with no error.
I attach the new WinDbg capture with the result of the "lm" command.
Daniel Garcia.
El 5 de octubre de 2011 15:26, Daniel García <abuelanders...@gmail.com>escribió:
> Hi again,
>
> I've upgraded to iPXE and to the new version of sanbootconf too, but I'm
> getting the same error: the client machines conects to the iscsi target and
> starts booting windows xp, until it reboots itself, giving a 0x00007b error
> in the WinDbg.
>
> I attach the WinDbg output file. I'd appreciate any kind of help. I've been
> looking hard for any solution, but I found nothing...
>
> Daniel.
>
> El 4 de octubre de 2011 13:51, Daniel García
> <abuelanders...@gmail.com>escribió:
>
> Hi,
>>
>> I've followed the how-to and I get the error report from WinDbg attached
>> to this mail. I'd appreciate any information you can give me.
>>
>> It seems like sanbootconf driver doesn't load.
>>
>>
>> Daniel.
>>
>
>
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\COM2
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Wed Oct 5 16:03:21.984
2011 (UTC + 2: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
ntkrpamp.exe -
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrpamp.exe -
nt!DbgBreakPoint:
8052b5d0 cc int 3
kd> lm
start end module name
804d7000 806e5000 nt (export symbols) ntkrpamp.exe
806e5000 80705d00 hal (export symbols) halmacpi.dll
kd> g
*** Fatal System Error: 0x0000007b
(0xF79EA524,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.
*********************************************************************
* 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+ *
*********************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f79ea524, c0000034, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntkrpamp.exe ( nt!KeRegisterBugCheckReasonCallback+77c )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8052b5dc 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: f79ea524, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set
symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 804f99e4 to 8052b5dc
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f79ea0d8 804f99e4 00000003 00000000 80084000 nt!DbgBreakPointWithStatus+0x4
f79ea4b8 804f9f33 0000007b f79ea524 c0000034
nt!KeRegisterBugCheckReasonCallback+0x77c
f79ea4d8 80699111 0000007b f79ea524 c0000034 nt!KeBugCheckEx+0x1b
f79ea640 8069d232 80084000 00000000 80084000 nt!NlsOemLeadByteInfo+0x19ff1
f79ea690 80699f70 80084000 f79ea6ac 00034000 nt!IoReportHalResourceUsage+0x1cc2
f79ea838 806983d3 80084000 00000000 861c42e0 nt!NlsOemLeadByteInfo+0x1ae50
f79eadac 805cff64 80084000 00000000 00000000 nt!NlsOemLeadByteInfo+0x192b3
f79eaddc 805460de 8069790c 80084000 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x214
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x72e
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeRegisterBugCheckReasonCallback+77c
804f99e4 e85f830000 call nt!ZwYieldExecution+0xa64 (80501d48)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeRegisterBugCheckReasonCallback+77c
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrpamp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> lm
start end module name
804d7000 806e5000 nt (export symbols) ntkrpamp.exe
806e5000 80705d00 hal (export symbols) halmacpi.dll
f723d000 f7273000 iscsiprt (deferred)
f7273000 f72b2000 msiscsi (deferred)
f72b2000 f72cbb80 Mup (deferred)
f72cc000 f72ef180 Fastfat (deferred)
f72f0000 f7301f00 sr (deferred)
f7302000 f7321b00 fltMgr (deferred)
f7322000 f7339900 atapi (deferred)
f733a000 f734ae00 psched (deferred)
f734b000 f73a3380 tcpip (deferred)
f73a4000 f73b6600 ipsec (deferred)
f73b7000 f73cd880 KSecDD (deferred)
f73ce000 f741b680 Rtenicxp (deferred)
f741c000 f7448980 NDIS (deferred)
f7449000 f746ea80 dmio (deferred)
f746f000 f748dc00 ftdisk (deferred)
f748e000 f749ed80 pci (deferred)
f749f000 f74cd280 ACPI (deferred)
f75cf000 f75d8380 isapnp (deferred)
f75df000 f75e9580 MountMgr (deferred)
f75ef000 f75fc000 VolSnap (deferred)
f75ff000 f7607900 msgpc (deferred)
f760f000 f7617e00 disk (deferred)
f761f000 f762b180 CLASSPNP (deferred)
f784f000 f7855180 PCIIDEX (deferred)
f7857000 f785bd00 PartMgr (deferred)
f785f000 f7863a80 TDI (deferred)
f79df000 f79e2000 BOOTVID (deferred)
f7acf000 f7ad0b80 kdcom (deferred)
f7ad1000 f7ad2100 WMILIB (deferred)
f7ad3000 f7ad4600 intelide (deferred)
f7ad5000 f7ad6700 dmload (deferred)
f7b97000 f7b97d80 pciide (deferred)
_______________________________________________
gPXE mailing list
gPXE@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
