Collect the crash dump when booting through the SAN LUN which is not accessble

We need to collect the crash dump when we boot through the SAN LUN.(Disk less Boot - No Local Hard Disk Drive[HDD] is availble)

When booting through LUN, LUN path is down. That is the Windows Host can not find the LUN. So that we got BSOD Bugcheck Code-7B(Inaccessible boot device).

Since existing primary path(LUN) is not accessible, the crash dump creation is not completed successfully. Attached the screen shot of the BSOD which shows the dump status.

Is that possible to store the dump in the LUN?
Is there any other way to store the dump in some other drive ? If Yes, Please let us know the procedures/steps.

Hi Folks,

Sorry. I could not attach the BSOD screen shot.

Please help us to collect the crash dump.

Thanks in Advance.

Regards,
Vignesh

Hi All,

Anybody can give info about this ?

As we don’t have any alternate path to LUN. Only available path is also getting down.

At this point windows have the intelligence to store the dump in the Lost LUN???

Or any other ways to get the dump ? (because it is a server in production)

We are critically blocked because of this issue.

Thanks,
Vignesh

By default if your boot disk (LUN) is disconnected/not-reachable (for more
than the disk timeout period), Windows will throw this BSOD 0x7B.

I would suggest to root-cause & debug, why the boot LUN has got
disconnected. BSOD 0x7B will not give much information other than saying
the boot disk is not-reachable.

If you are still interested to collect the crashdump - You can do it using
.dump command (
https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx).
This will copy the dump from debuggee to the debugger machine - so make
sure you are using 1394 firewire port or network adapter (if the debuggee
is Win8 or above). Copying the dump through serial port will take much
longer time.

Regards,
Gokul T V

On Fri, Oct 14, 2016 at 10:31 AM, wrote:

> Hi All,
>
> Anybody can give info about this ?
>
> As we don’t have any alternate path to LUN. Only available path is also
> getting down.
>
> At this point windows have the intelligence to store the dump in the Lost
> LUN???
>
> Or any other ways to get the dump ? (because it is a server in production)
>
> We are critically blocked because of this issue.
>
> Thanks,
> Vignesh
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:>

Hi Gokul,

Thanks for the response.

Is there any way to redirect the dump to external hard disk drive or pen drive when the primary path goes down ?(except .dump /f in windbg)

Regards,
Vignesh

No.

Hi Gokul,

Thanks for your great inputs.

Regards,
Vignesh