Yes, but those errors aren’t fatal, at least up until the point where you need a disk (e.g. apply OS, reboot). So you’ll see them all over a typical bare metal deployment log. Sometimes they just distract you from the real issue.
The “not bootable” message just says those aren’t active volumes. There does need to be at least one bootable (active) partition on the system if you expect it to boot. Drives can be unsuitable if they are not formatted NTFS, or if they are too small. Are you using a custom disk layout (meaning you manually configured the “Format and Partition Disk” step)? Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Tuesday, November 11, 2014 1:08 PM To: '[email protected]' Subject: RE: [mssms] Issue with OSD from a DP I see logs like this when the TS engine doesn’t think there’s a local disk to write to. Like when a RAID controller doesn’t have drivers in WinPE. Which is what We do not find an available volume to store the local data path TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to persist execution state. Error 0x(80070057) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to save execution state and environment to local hard disk TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Seems to suggest. C and D are somehow not suitable. The volumes seem to not be bootable. Using diskpart, can you see if the volumes are marked ‘active’ or not? Todd From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kevin Johnston Sent: Tuesday, November 11, 2014 12:55 PM To: '[email protected]' Subject: RE: [mssms] Issue with OSD from a DP I am still researching but I get errors like this: Request was successful. TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) User did not specify local data drive TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Volume C:\ has 4208287744 bytes of free space TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Volume C:\ is not bootable TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Volume D:\ has 200095629312 bytes of free space TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Volume D:\ is not bootable TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Volume X:\ is not a fixed hard drive TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) TSM root drive = TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) We do not find an available volume to store the local data path TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Set a TS execution environment variable _SMSTSNextInstructionPointer=1 TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Set a global environment variable _SMSTSInstructionStackString=0 TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Set a TS execution environment variable _SMSTSInstructionStackString=0 TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Save the current environment block TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,676) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to save environment to (80070057) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to persist execution state. Error 0x(80070057) TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) Failed to save execution state and environment to local hard disk TSManager 11/11/2014 1:07:41 PM 1916 (0x077C) It seems to keep repeating this over and over till it gives me the fail/restart screen when the log file stops. Kevin From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Monday, November 10, 2014 8:29 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Issue with OSD from a DP cant you just use NET to map a network drive and copy the log files there ? net use h: \\server\share<file:///\\server\share> the error message 8007008a1 means... The specified path is invalid. Source: Windows ----- so have you hardcoded something to C: and it's now on D: or something like that ? On Mon, Nov 10, 2014 at 2:14 PM, Kevin Johnston <[email protected]<mailto:[email protected]>> wrote: I have a DP in the UK. I have everything configured like I do here for my deployments. I can PXE boot, I enter the TS password, then it loads some files and then I get the following: [cid:[email protected]] Looking at the SMSTSLog on the machine, I see that there are errors related to “C:\ not bootable, X: is not fixed drive” but that is all. Because I am using vPro and VNC to see the machine, I can’t copy the log file here. This is a brand new out of the box machine. When I do diskpart I see the OS as being letter D: When I boot into the machine (Dell) the OS is actually C: So I thought this may have something to do with it, but since this does not load the UDI wizard to complete I don’t think this is an issue as the drive will get wiped as part of the TS. This same machine works without issue here in the local office, so I am not sure how to fix this issue. I was hoping it would load into the UDI wizard, but it never makes it there. Thanks, Kevin Johnston
