Storage bus debugger extensions

WINDBG
1

Hi,

I have a system that is not booting up (I don’t have any of mine drivers on
it).
However I still need to debug it because I have done a bare metal recovery
from a backed up volume image on the target system.

Not booting up means it is giving BugCheck 0x7B (INACCESSIBLE_BOOT_DEVICE)
and call stack is below:–

kd> kb

ChildEBP RetAddr Args to Child

f78b2648 80825b5b 00000003 f78b2a98 00000000
nt!RtlpBreakWithStatusInstruction

f78b2694 80826a4f 00000003 00000000 80084000 nt!KiBugCheckDebugBreak+0x19

f78b2a2c 80826de7 0000007b f78b2a98 c0000034 nt!KeBugCheck2+0x5d1

f78b2a4c 809fe64f 0000007b f78b2a98 c0000034 nt!KeBugCheckEx+0x1b

f78b2bb4 80a00b25 80084000 00000000 80084000 nt!IopMarkBootPartition+0xf7

f78b2c04 809fd3e3 80084000 f78b2c48 00000000
nt!IopInitializeBootDrivers+0x4bb

f78b2c74 809fb5bb 80084000 00000000 8bd77948 nt!IoInitSystem+0x61f

f78b2da0 808e0a69 80084000 f78b2ddc 809419d6
nt!Phase1InitializationDiscard+0x9cf

f78b2dac 809419d6 80084000 00000000 00000000 nt!Phase1Initialization+0xd

f78b2ddc 80887faa 808e0a5c 80084000 00000000 nt!PspSystemThreadStartup+0x2e

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

I see that *nt!IopMarkBootPartition* is calling ZwOpenFile for *object path
“\ArcName\multi(0)disk(0)rdisk(0)partition(1)”.
*And return code is STATUS_OBJECT_NAME_NOT_FOUND (0xC0000034), which means
that this object path has not been built yet.

I thought of listing Miniport Adapters and IDE Adapters.
I see that there are debugger extensions for debugging SCSI Miniport/port
but don’t see any extensions for IDE based ones.

If any1 know of any1 who has developed it and is free on the web, please
provide the link.

Any pointers/approach on the problem above would also be helpful.

Thanks in advance.

Regards
Deepak

2

Looks to me like the system you got the backup off of (“target” as you
refer to it) and the system you’re trying to restore it to (“host”) have
different storage controllers and the OS that is booting doesn’t have the
driver for the disk controller loaded… For example, one might have SCSI,
the other SAS, or one SAS and the other IDE. This can happen if the
storage controllers on the two systems come from different manufacturers
and require different miniport drivers You need to find a system that
uses the same type of storage controller driver as the target system.
There may be alternatives. I don’t know if you can use Windows Repair
from CD to get the correct drivers installed. If you can recreate the
backup image, there may be a way to get the required storage controller
installed on the “target” system before making the backup.

Deepak Gupta
Sent by: xxxxx@lists.osr.com
11/04/2010 03:56 AM
Please respond to
“Kernel Debugging Interest List”

To
“Kernel Debugging Interest List”
cc

Subject
[windbg] Storage bus debugger extensions

Hi,

I have a system that is not booting up (I don’t have any of mine drivers
on it).
However I still need to debug it because I have done a bare metal recovery
from a backed up volume image on the target system.

Not booting up means it is giving BugCheck 0x7B (INACCESSIBLE_BOOT_DEVICE)
and call stack is below:–

kd> kb
ChildEBP RetAddr Args to Child
f78b2648 80825b5b 00000003 f78b2a98 00000000
nt!RtlpBreakWithStatusInstruction
f78b2694 80826a4f 00000003 00000000 80084000 nt!KiBugCheckDebugBreak+0x19
f78b2a2c 80826de7 0000007b f78b2a98 c0000034 nt!KeBugCheck2+0x5d1
f78b2a4c 809fe64f 0000007b f78b2a98 c0000034 nt!KeBugCheckEx+0x1b
f78b2bb4 80a00b25 80084000 00000000 80084000 nt!IopMarkBootPartition+0xf7
f78b2c04 809fd3e3 80084000 f78b2c48 00000000
nt!IopInitializeBootDrivers+0x4bb
f78b2c74 809fb5bb 80084000 00000000 8bd77948 nt!IoInitSystem+0x61f
f78b2da0 808e0a69 80084000 f78b2ddc 809419d6
nt!Phase1InitializationDiscard+0x9cf
f78b2dac 809419d6 80084000 00000000 00000000 nt!Phase1Initialization+0xd
f78b2ddc 80887faa 808e0a5c 80084000 00000000
nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

I see that nt!IopMarkBootPartition is calling ZwOpenFile for object path
“\ArcName\multi(0)disk(0)rdisk(0)partition(1)”.
And return code is STATUS_OBJECT_NAME_NOT_FOUND (0xC0000034), which means
that this object path has not been built yet.

I thought of listing Miniport Adapters and IDE Adapters.
I see that there are debugger extensions for debugging SCSI Miniport/port
but don’t see any extensions for IDE based ones.

If any1 know of any1 who has developed it and is free on the web, please
provide the link.

Any pointers/approach on the problem above would also be helpful.

Thanks in advance.

Regards
Deepak
— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Yeah that is the case.
I am aware of that, this is a feature of product called as Hardware
Independent Restore.
Drivers for particular hardware are inserted onto target when restore
happens (yeah all registry keys are also created).

I have another backup image also which getting restored perfectly (and this
image was not taken from any similar hardware)
and system boots up fine.

I see same drivers being inserted onto target in both the cases, but still
first one is not booting up.

That’s why I asked here if I there are debugger extensions for ATAPI port
too.

Regards
Deepak

On Thu, Nov 4, 2010 at 7:55 PM, wrote:

>
> Looks to me like the system you got the backup off of (“target” as you
> refer to it) and the system you’re trying to restore it to (“host”) have
> different storage controllers and the OS that is booting doesn’t have the
> driver for the disk controller loaded… For example, one might have SCSI,
> the other SAS, or one SAS and the other IDE. This can happen if the storage
> controllers on the two systems come from different manufacturers and require
> different miniport drivers You need to find a system that uses the same
> type of storage controller driver as the target system. There may be
> alternatives. I don’t know if you can use Windows Repair from CD to get the
> correct drivers installed. If you can recreate the backup image, there may
> be a way to get the required storage controller installed on the “target”
> system before making the backup.
>
>
>
> Deepak Gupta
> Sent by: xxxxx@lists.osr.com
>
> 11/04/2010 03:56 AM
> Please respond to
> “Kernel Debugging Interest List”
>
> To
> “Kernel Debugging Interest List”
> cc
> Subject
> [windbg] Storage bus debugger extensions
>
>
>
>
> Hi,
>
> I have a system that is not booting up (I don’t have any of mine drivers on
> it).
> However I still need to debug it because I have done a bare metal recovery
> from a backed up volume image on the target system.
>
> Not booting up means it is giving BugCheck 0x7B (INACCESSIBLE_BOOT_DEVICE)
> and call stack is below:–
>
> kd> kb
>
> ChildEBP RetAddr Args to Child
>
> f78b2648 80825b5b 00000003 f78b2a98 00000000
> nt!RtlpBreakWithStatusInstruction
>
> f78b2694 80826a4f 00000003 00000000 80084000 nt!KiBugCheckDebugBreak+0x19
>
> f78b2a2c 80826de7 0000007b f78b2a98 c0000034 nt!KeBugCheck2+0x5d1
>
> f78b2a4c 809fe64f 0000007b f78b2a98 c0000034 nt!KeBugCheckEx+0x1b
>
> f78b2bb4 80a00b25 80084000 00000000 80084000 nt!IopMarkBootPartition+0xf7
>
> f78b2c04 809fd3e3 80084000 f78b2c48 00000000
> nt!IopInitializeBootDrivers+0x4bb
>
> f78b2c74 809fb5bb 80084000 00000000 8bd77948 nt!IoInitSystem+0x61f
>
> f78b2da0 808e0a69 80084000 f78b2ddc 809419d6
> nt!Phase1InitializationDiscard+0x9cf
>
> f78b2dac 809419d6 80084000 00000000 00000000 nt!Phase1Initialization+0xd
>
> f78b2ddc 80887faa 808e0a5c 80084000 00000000 nt!PspSystemThreadStartup+0x2e
>
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> I see that nt!IopMarkBootPartition is calling ZwOpenFile for object
> path “\ArcName\multi(0)disk(0)rdisk(0)partition(1)”.
> And return code is STATUS_OBJECT_NAME_NOT_FOUND (0xC0000034), which means
> that this object path has not been built yet.
>
> I thought of listing Miniport Adapters and IDE Adapters.
> I see that there are debugger extensions for debugging SCSI Miniport/port
> but don’t see any extensions for IDE based ones.
>
> If any1 know of any1 who has developed it and is free on the web, please
> provide the link.
>
> Any pointers/approach on the problem above would also be helpful.
>
> Thanks in advance.
>
> Regards
> Deepak
>
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>