Single master image, sysprep, bsod, not what you think..

  • Thread starter Thread starter WILLIAM
  • Start date Start date
W

WILLIAM

I have an image that I've successfully been able to deploy to many different
types of workstations in my environment. Essentially I have 2 copies, the
first is a plain vanilla image with limited drivers, the second is that same
image, but sysprepped and shut down.

When I deploy the sysprepped image to any workstation in my environment mini
setup runs, then using the runonceex key, the machine type is autodetected
and the appropriate drivers are installed, along with a few applications. It
works great!

The problem I just ran into out in the field, I got to a new site that has
some specialized apps. I have two choices. One, use the sysprepped copy,
configure it with the software I need (though now it will have drivers
installed for a specific machine type), then resysprep it and create a new
image and hope it works.

Or two, use the nonsysprepped version, install the software I need, sysprep
THIS machine and shut it down. This seemed the most logical to me, but the
machine I imaged was different than the original the "master" was created
from, and since I didn't have sysprep rebuilding the mass storage driver
database, it's hopelessly blue screened, 0x0000007b.

So I'm not really looking to troubleshoot the BSOD itself, I know exactly
why it's happening. I'm looking for ideas that are specific to this
situation...how can I create a new base image that will essentially rebuild
mass storage databases like sysprep does, without using sysprep? OR, is
there another way to use sysprep in this situation I'm not aware of? Or
anything...help me brain storm people! :-) Thanks...
 
0x0000007B: INACCESSIBLE_BOOT_DEVICE

Windows lost access to the system partition or boot volume during the startup
process. Typical causes: Installing incorrect device drivers when installing or
upgrading storage adapter hardware, or a virus.
http://msdn.microsoft.com/en-gb/library/ms795508.aspx

a.. After You Remove or Reinstall Roxio Easy CD Creator 5 Platinum Edition {KB
811408} Win XP
b.. Stop 0x7B or “0x4,0,0,0†Error {KB 122926} Win NT, Win XP (on restart)
c.. During setup (Sysprep issue) {KB 303786} Win XP
d.. When You Press F6 to Load Drivers During Unattended Win XP Setup {KB 307099}
Win XP
e.. When you restart your Win XP-based computer {KB 316401} Win XP (after
replacing motherboard)
f.. When you start your computer from a WinPE CD-ROM or from a Server 2003 CD-ROM
using a USB CD-ROM device {KB 839210} Win XP, Win Server 2003 (patch available)
g.. Limited OEM driver support is available with F6 during Win XP & Server 2003
setup {KB 314859} Win XP, Win Server 2003
h.. Error message When Starting Windows Vista After Changing SATA Mode of Boot
Drive: STOP 0x0000007B INACCESSABLE_BOOT_DEVICE {KB 922976} Vista
i.. Error message When Installing Vista on Computer With a DELL CERC SATA 1.5/6ch
RAID controller: STOP 0x0000007B {KB 928632} Vista (needs driver update)
 
Peter Foldes said:
0x0000007B: INACCESSIBLE_BOOT_DEVICE

Windows lost access to the system partition or boot volume during
the startup process. Typical causes: Installing incorrect device
drivers when installing or upgrading storage adapter hardware, or a
virus.
http://msdn.microsoft.com/en-gb/library/ms795508.aspx
Click to expand...
<snip remainder of troubleshooting for BSOD 7B>

Peter, looks like you missed the part where the OP said he didn't need
to troubleshoot the BSOD...

--
Zaphod

Pan-Galactic Gargle Blaster: A cocktail based on Janx Spirit.
The effect of one is like having your brain smashed out
by a slice of lemon wrapped round a large gold brick.
 
Yes, thank you.

Is there a way to, in lay terms, reload the mass storage driver database
(which is sort of what [sysprep] BuildMassStorageSection=yes section does,
right?)?

So I can put this original base image with very few drivers onto another
machine type...
 
WILLIAM

No you cannot. That is why I posted that Stop error (BSOD) that you were receiving
which itself becomes self explanatory just by the title itself. (
INACCESSIBLE_BOOT_DEVICE )

I though you would have understood this.


--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

WILLIAM said:
Yes, thank you.

Is there a way to, in lay terms, reload the mass storage driver database
(which is sort of what [sysprep] BuildMassStorageSection=yes section does,
right?)?

So I can put this original base image with very few drivers onto another
machine type...

Zaphod Beeblebrox said:
<snip remainder of troubleshooting for BSOD 7B>

Peter, looks like you missed the part where the OP said he didn't need
to troubleshoot the BSOD...

--
Zaphod

Pan-Galactic Gargle Blaster: A cocktail based on Janx Spirit.
The effect of one is like having your brain smashed out
by a slice of lemon wrapped round a large gold brick.
Click to expand...
Click to expand...
 
WILLIAM said:
Yes, thank you.

Is there a way to, in lay terms, reload the mass storage driver
database
(which is sort of what [sysprep] BuildMassStorageSection=yes section
does,
right?)?

So I can put this original base image with very few drivers onto
another
machine type...
Click to expand...
I don't know of a way, but that doesn't mean it can't be done. I was
going to suggest you ask over in the technet forums, but it appears
that the XP deployment form is no more, and I doubt that the Vista
deployment forum would be much help - Vista's sysprep is much
different than XPs.

Good luck...

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
 
Thanks again Zaphod...if that's your real name LOL (love those books!)

I know it can be done, I've seen setups with a much broader variety of
machine types that are using a single image...I think I've got my mass
storage drivers issue worked out, now I'm leaning toward the HAL side as the
root cause.

I'll keep reasearching...it will be worth it in my situation to have one non
sysprepped image that i can deploy to any machine type, install my needed
software (which are all automated unattended installs, which makes me think i
can play with factory mode), then reseal it for deployment...


Zaphod Beeblebrox said:
WILLIAM said:
Yes, thank you.

Is there a way to, in lay terms, reload the mass storage driver
database
(which is sort of what [sysprep] BuildMassStorageSection=yes section
does,
right?)?

So I can put this original base image with very few drivers onto
another
machine type...
Click to expand...
I don't know of a way, but that doesn't mean it can't be done. I was
going to suggest you ask over in the technet forums, but it appears
that the XP deployment form is no more, and I doubt that the Vista
deployment forum would be much help - Vista's sysprep is much
different than XPs.

Good luck...

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
Click to expand...
 
I have an image that I've successfully been able to deploy to many different
types of workstations in my environment.  Essentially I have 2 copies, the
first is a plain vanilla image with limited drivers, the second is that same
image, but sysprepped and shut down.

When I deploy the sysprepped image to any workstation in my environment mini
setup runs, then using the runonceex key, the machine type is autodetected
and the appropriate drivers are installed, along with a few applications. It
works great!

The problem I just ran into out in the field, I got to a new site that has
some specialized apps.  I have two choices. One, use the sysprepped copy,
configure it with the software I need (though now it will have drivers
installed for a specific machine type), then resysprep it and create a new
image and hope it works.

Or two, use the nonsysprepped version, install the software I need, sysprep
THIS machine and shut it down.  This seemed the most logical to me, butthe
machine I imaged was different than the original the "master" was created
from, and since I didn't have sysprep rebuilding the mass storage driver
database, it's hopelessly blue screened, 0x0000007b.

So I'm not really looking to troubleshoot the BSOD itself, I know exactly
why it's  happening.  I'm looking for ideas that are specific to this
situation...how can I create a new base image that will essentially rebuild
mass storage databases like sysprep does, without using sysprep?  OR, is
there another way to use sysprep in this situation I'm not aware of?  Or
anything...help me brain storm people!  :-)  Thanks...
Click to expand...

William,
I know you have most of the dirty work figured out already, but
especially going forward the Universal Imaging Utility (UIU) from Big
Bang LLC www.uiu4you.com handles all HAL, Sysprep (for XP and Vista)
and ALL the driver issues associated with disparate hardware (Over 26K
plug and play IDs on top of what Windows has) It is definitely a time
and effort saver and the per seat licensing is very reasonable. Hope
this helps.

My name is Nathaniel Bauer and I work for Big Bang LLC.
 
Back
Top