Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all articles
Browse latest Browse all 9126

Unable to find a volume that is suitable for staging the boot image.

$
0
0

I have an SCCM 2012 OSD task sequence that is failing when it tries to stage the boot image to the drive before rebooting.  The log file shows:

Staging boot image CET00028	TSManager	6/5/2014 3:57:58 PM	1492 (0x05D4)
Mounting \Device\HarddiskVolume6 at Z:	TSManager	6/5/2014 3:57:58 PM	1492 (0x05D4)
Unmounting volume Z:\	TSManager	6/5/2014 3:57:58 PM	1492 (0x05D4)
Checking to see if the data path is on a bootable volume	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
	Volume C:\ because it is not suitable as the system partition	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
Searching for a volume to stage the boot image	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
	Volume S:\ is not NTFS	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
	Volume C:\ because it is not suitable as the system partition	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
	Volume R:\ is not on a fixed disk	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
	Volume X:\ is not on a fixed disk	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
BootImage::FindBootableVolume( NULL, sPath), HRESULT=80070490 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,1045)	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)
Unable to find a volume that is suitable for staging the boot image.
Element not found. (Error: 80070490; Source: Windows)	TSManager	6/5/2014 3:57:59 PM	1492 (0x05D4)

I've seen others get this error code and fix it by injecting the correct storage drivers.  In my case I believe I have the correct storage drivers.  In a separate MDT 2013/WDS environment I can deploy 8.1 to the same machine using the same drivers with no problems so my drivers appear to allow proper access to the drive.  When I check the volumes with DiskPart they all appear to be fine.  The C:\ volume has the _SMSTaskSequence folder on it with files so it is certainly writable.  The system is set for UEFI mode.  Of course if I change it to Legacy mode this problem doesn't happen.  I have also integrated MDT 2013 into SCCM console and both an SCCM task sequend and an MDT task sequence do the same thing. Any ideas?


Thanks,


Viewing all articles
Browse latest Browse all 9126

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>