none
Out of disk space during capture sequence RRS feed

  • Question

  • I was able to successfully create a custom for Windows 10 and deploy it with Update 2. I discovered I needed to modify some software settings in the base wim image so I fired up my hyper-v VM of 10 and made the changes. On attempting to recapture the wim the capture process hangs during Running Action: Apply Windows PE

    It appears there is an e drive mounted by the capture process and the e:\ is full. According to disk part E is a 499 MB fat32 partition.

    BDD.log shows these

    <![LOG[  Console > 2016/01/13 16:27:01 ERROR 112 (0x00000070) Copying File E:\efi\boot\en-us\bootx64.efi.mui]LOG]!><time="16:27:02.000+000" date="01-13-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > There is not enough space on the disk.
    ]LOG]!><time="16:27:02.000+000" date="01-13-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply">

    Is this a bug in the ADK or Update 2 or do I need to modify a script or setting somewhere?


    • Edited by sleety_adorn Wednesday, January 13, 2016 9:53 PM more info on e drive added
    Wednesday, January 13, 2016 9:33 PM

All replies

  • Can you post BDD.log and SMSTS.log to OneDrive or similar and share the link here?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Wednesday, January 13, 2016 11:31 PM
    Moderator
  • https://onedrive.live.com/redir?resid=C42875EE32A03A11!1762&authkey=!AKtiZPAYeqpOrJM&ithint=file%2clog

    I have been unable to find the smsts.log since upgrading. Has the location changed?

    I started the capture process from within windows 10 by running the deploymentshare/scripts/litetouch.vbs and found logs for that in c:\minint\smsosd\osdlogs . Post deployment I have been looking in the c:\windows\temp\deploymentlogs\ (does contain the bdd.log and other logs but no smsts.log). Makes it difficult to troubleshoot task sequence failures..........

    Thursday, January 14, 2016 1:47 PM
  • You can set SLShare to have all  the logs copied at completion or from the log I saw that the SMSTS.log was located here:
    The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTISetVariable 1/13/2016 4:26:50 PM 0 (0x0000)

    What is the actual file size of: 

    Copying \\blahMDT\DeploymentShare$\Boot\LiteTouchPE_x64.wim to E:\sources\boot.wim LTIApply 1/13/2016 4:26:54 PM 0 (0x0000)


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, January 14, 2016 7:19 PM
    Moderator
  • 465,402 KB
    Friday, January 15, 2016 3:44 PM
  • From a similar issue I had on my home upgrade of windows 10 from 8.1 I remembered that you can recover some disk space by deleting the unused language folders from that boot drive.

    https://www.reddit.com/r/Windows10/comments/3a6znd/we_couldnt_update_the_system_reserved_partition/

    I wasn't able to mount the drive from within my windows 10 image using the command listed in the reddit thread but when in the winPE environment I was able to press F8 to get a command prompt that then gave me access to manually remove the language folders from the boot folder on the e drive.  Once those were removed, I also removed the extra language folders from my deployment share\boot\x64 folders in case it referenced that location in some way. Figured if I updated my deployment share it would put them back anyway so it couldn't hurt. I was then able to restart the capture and it completed successfully.

    Not sure why I ran out of space though to begin with.

    Tuesday, January 19, 2016 4:00 PM