CD BOOT (El Torito) problem with Intel SE7520 JR2 Main board

[Jay]

I am having problem booting CD image on Intel SR1400 platform which deploys
SE7520JR2 main board.

Platform is SCSI based with 3 IDE and SATA interfaces.
The CD drive used is Toshiba SD R6472 CD/DVD R/W drive. This drive don't
require special driver for OS other than CD ROM available in the image(
According to manufacturer specification).

The Image boots OK from SCSI Drive with EWF RAM working ( I am using
Slobodan's method not to create extra temporary partition on the drive by
using added registry entries for EWF).

I am creating CD using NERO6 ultra edition first create the drive image use
Elsigfix.exe to update MBR with ELT signature and then burn CD from that
image.

The PROBLEM is CD start to boot I get BOOT.ini option menu after that see
Windows XP Embedded screen and soon after that BSOD with 7B error
inaccessible boot device.

I have used windbg and checked that PCIIDE driver is loaded but it is the
last driver that gets loaded and Error occurs soon after that.

Same CD used on another platform which is IDE based boots CD fine.

any suggestions?

Thanks

Jay

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

Could you give us info where (Position on SCSI, IDE or SATA) was CD-Drive with ELTO CD connected during the FBA? Also what platform
did you use?
Also can you give us here result after BSOD created by windbg when you call: "!devnode 0 1"

Regards.
Slobodan
PS:
If you are using my approach then you must have read the BSOD remark regarding the BIOS problem. (Try updating BIOS)

 

[Jay]

Hi Slobodan

The CD/DVD drive has IDE interface and is connected to Second IDE master
(only connection available for Slimline device for the mainboard).

The FBA is run on same platform as CD Boot is attempted. No H/W change same
IDE/SCSI configuration.

I have the latest BIOS installed for this platform so I am not sure about
BIOS Issue you are Referring to Can you provide more detail?

I will provide you the Windbg info you want as soon I have it .

Thanks for your help

Regards

Jay

Hi Jay,

Could you give us info where (Position on SCSI, IDE or SATA) was CD-Drive

with ELTO CD connected during the FBA? Also what platform

did you use?
Also can you give us here result after BSOD created by windbg when you call: "!devnode 0 1"

Regards.
Slobodan
PS:
If you are using my approach then you must have read the BSOD remark

regarding the BIOS problem. (Try updating BIOS)

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

New BIOS do not guarantee that they fixed actual problem :-(. Also please read trough following thread and know that problem is not
in MS code. (Although IMHO this error is too common and they should provide patched version of ntdetect with XPe so we can use it.)

http://groups.google.com/groups?hl=en&lr=&c2coff=1&selm=OKp#[email protected]
Read troubleshooting part related to BSOD 7B.

And please do send us a windbg info, so we can see what drivers were actually loaded.
If you can't find disk driver loaded then error is not in BIOS/ndetect pair but something else.

Regards,
Slobodan

 

[Jay]

Hi Slobodan

Here is the Debug view of all the loaded drivers and result of "!devnode 0
1" command
****************************************************
0: kd> lm t n
start end module name
804e0000 806c5000 nt ntkrnlmp.exe Thu Aug 29 04:04:44 2002
(3D6DD59C)
806c5000 806e4b80 hal halmacpi.dll Thu Aug 29 04:05:02 2002
(3D6DD5AE)
f748d000 f74a6680 Mup Mup.sys Thu Aug 29 05:12:53 2002
(3D6DE595)
f74a7000 f74cfe80 NDIS NDIS.sys Thu Aug 29 05:09:23 2002
(3D6DE4C3)
f74d0000 f74e3780 KSecDD KSecDD.sys Fri Aug 17 16:50:01 2001
(3B7D8379)
f74e4000 f7507700 Fastfat Fastfat.sys Thu Aug 29 05:12:45 2002
(3D6DE58D)
f7508000 f7518e80 sr sr.sys Thu Aug 29 04:17:56 2002
(3D6DD8B4)
f7519000 f752f080 SCSIPORT SCSIPORT.SYS Thu Aug 29 04:27:47 2002
(3D6DDB03)
f7530000 f7545380 atapi atapi.sys Thu Aug 29 04:27:48 2002
(3D6DDB04)
f7546000 f7569b80 dmio dmio.sys Fri Aug 17 16:58:27 2001
(3B7D8573)
f756a000 f7588880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001
(3B7D8419)
f7589000 f75b4c80 ACPI ACPI.sys Thu Aug 29 04:09:03 2002
(3D6DD69F)
f75d6000 f75e5600 pci pci.sys Thu Aug 29 04:09:10 2002
(3D6DD6A6)
f75e6000 f75eec00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001
(3B7D8559)
f75f6000 f75ff280 MountMgr MountMgr.sys Fri Aug 17 16:47:36 2001
(3B7D82E8)
f7606000 f760e980 EWF EWF.sys Thu Jun 12 20:04:59 2003
(3EE9152B)
f7616000 f7622000 volsnap volsnap.sys Fri Aug 17 16:53:19 2001
(3B7D843F)
f7626000 f762f480 symmpi symmpi.sys Wed Oct 08 12:37:49 2003
(3F843D5D)
f7636000 f7641980 cdrom cdrom.sys Thu Aug 29 04:27:55 2002
(3D6DDB0B)
f7646000 f7651500 CLASSPNP CLASSPNP.SYS Thu Aug 29 05:08:42 2002
(3D6DE49A)
f7656000 f765e400 disk disk.sys Thu Aug 29 04:27:56 2002
(3D6DDB0C)
f7856000 f785bc80 PCIIDEX PCIIDEX.SYS Thu Aug 29 04:27:47 2002
(3D6DDB03)
f785e000 f7862900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001
(3B7DC5A7)
f79e6000 f79e9000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001
(3B7D8345)
f79ea000 f79edc80 eltorito eltorito.sys Mon Nov 05 04:41:31 2001
(3BE65ECB)
f79ee000 f79f0d80 ACPIEC ACPIEC.sys Fri Aug 17 16:57:55 2001
(3B7D8553)
f7ad6000 f7ad7b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001
(3B7D8346)
f7ad8000 f7ad9100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001
(3B7D878B)
f7ada000 f7adb700 dmload dmload.sys Fri Aug 17 16:58:15 2001
(3B7D8567)
f7b9e000 f7b9ed00 pciide pciide.sys Fri Aug 17 16:51:49 2001
(3B7D83E5)
f7b9f000 f7b9fd80 OPRGHDLR OPRGHDLR.SYS Fri Aug 17 16:57:55 2001
(3B7D8553)
0: kd> ! DEVNODE 0 1
Error retrieving address of IopRootDeviceNode
**************************************************************

Regards

Jay

Hi Jay,

New BIOS do not guarantee that they fixed actual problem :-(. Also please

read trough following thread and know that problem is not

in MS code. (Although IMHO this error is too common and they should

provide patched version of ntdetect with XPe so we can use it.)

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

From first list all drivers are present, but this tell us nothing they are not sorted or anything.

0: kd> ! DEVNODE 0 1
Error retrieving address of IopRootDeviceNode

You must make this function work. !devnode is written without space. If it does not help make use of symbols get automatically from
MS symbol server.
Function will give you list of all device instances that are loaded and connection between drivers. Also you will see if some driver
had problems loading.

Regards,
Slobodan

PS:
Look how to add symbol path syntax like:

c:\windows\symbols;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

 

[Jay]

Hi Slobodan

Thanks for the info I will provide you the update some times tomorrow.

Regards

Jay

Hi Jay,

From first list all drivers are present, but this tell us nothing they are not sorted or anything.


You must make this function work. !devnode is written without space. If it

does not help make use of symbols get automatically from

MS symbol server.
Function will give you list of all device instances that are loaded and

connection between drivers. Also you will see if some driver

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

From log that you have posted I can tell you that all drivers required to support boot are loaded.
This mean that disk/partitions with ARC path provided by ntldr can't be matched in kernel mode and this is the reason for your
error.

Regarding the way how you can obtain unsupported ntdetect I have no idea (I have seen that someone told in this NG that he was able
to get it).
MS Embedded team told that they are not interested in providing this patch as part of XPe, and I do not have it. I have created
workaround for this problem as part of my driver that does other things as well.

Regards,
Slobodan

 

[Jay]

Hi Slobodan,

Thanks for looking into the debug details.

As you mentioned Disk/Partitions with ARC path provided by ntldr can't be
matched in kernel mode I don't understand what do you mean by that. can you
clarify that

The Boot.ini has path as follows
Multi(0)disk(0)rdisk(0)partition(1)

The Image was created on this partition of the HD (ran FBA). and used NERO
to create bootable CD from this partition.

Regards

Jay

Hi Jay,

From log that you have posted I can tell you that all drivers required to support boot are loaded.
This mean that disk/partitions with ARC path provided by ntldr can't be

matched in kernel mode and this is the reason for your

error.

Regarding the way how you can obtain unsupported ntdetect I have no idea

(I have seen that someone told in this NG that he was able

to get it).
MS Embedded team told that they are not interested in providing this patch

as part of XPe, and I do not have it. I have created

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

ntldr/ntdetect should pass BIOS parameters connected to each disk along with associated ARC paths to each disk.
Also parameter used during the boot from boot.ini is passed to kernel as well.

When disk.sys or other drivers enumerate disks they create PnPIDs used by drivers that have no understanding of ARC paths.

7B error shown after critical drivers are loaded and when kernel decide to try to match disk info provided by ntldr with disk info
provided by drivers. If ntldr did not provided any data or invalid data match will fail resulting in scenario in which OS can't
determine which disk was used for OS boot and this result in BSOD.

So problem is not you, it is the way how OS implementation try to determine which disk is used for boot purposes.

Regards,
Slobodan

 

[Jay]

Hi Slobodan,

Thanks for the clarification.

Regards
Jay

Hi Jay,

ntldr/ntdetect should pass BIOS parameters connected to each disk along

with associated ARC paths to each disk.

Also parameter used during the boot from boot.ini is passed to kernel as well.

When disk.sys or other drivers enumerate disks they create PnPIDs used by

drivers that have no understanding of ARC paths.

7B error shown after critical drivers are loaded and when kernel decide to

try to match disk info provided by ntldr with disk info

provided by drivers. If ntldr did not provided any data or invalid data

match will fail resulting in scenario in which OS can't

determine which disk was used for OS boot and this result in BSOD.

So problem is not you, it is the way how OS implementation try to

determine which disk is used for boot purposes.