Windows 10 20H1 failing to mount C:\ directory

[mperriello]

Kinda new to FOG and working off of prior staff’s build. So we had FOG working to image our laptops for 4-5 years previous, and testing this year’s laptops with last years image worked fine. I am building this years base image and we tested deploying it and get the error messages:

"rsync: mkdir "ntfs/Windows/Setup"failed: No such file or directory (2)
rsync error: error in fileIO ( code 11)at main.c(664)[Reciever-3.1.3]

then a box with (An error has been detected)

Failed to copy setupComplete.cmd

then we get no farther in post image.

Can anyone help me interpret and fix this?

Here is section of script :

# make the driver path on the client side to copy drivers to below from
# https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/7
# create a directory to hang the Windows C: drive partition on in FOS
# the 2>/dev/null below just redirects any errors from the mkdir command to null. i.e.
# if the directory already exists, I don't want to know about it, just hide the error. Understand
# that I could have tested if the directory already existed, but that takes more programming steps
# I'm just going to try to create it and ignore the error if it already exists.
mkdir /ntfs &>/dev/null

# The ntfs-3g -o force,rw $part /ntfs is using the last partition FOG processed
# instead of looping the partitions separately.
# mount image (remember this is mounting partition [U][B]after[/B][/U] new image is deployed)
ntfs-3g -o force,rw $part /ntfs

# 2018.06.19 JRB:  via https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/7 (again)
# this last bit of magic checks to see if the mntfail file exists and if it does then it means the mount
# failed so there is no need to continue on with the script.
mntRet="$?";
if [ ! "$mntRet" = "0" ]; then
    echo "Failed to mount C:";
    # display what happened
    cat /tmp/mntfail;
    # give the reader a chance to see what the error was - 120 == 2 minutes, this can be changed
    sleep 120;
    # terminate the post install script
    exit 1;
fi

[george1421]

@mperriello ok so you are using the post init script to update the unattend.xml file with the system name? I’m trying to understand where its falling down. In the link I provided you there should be a section of the code that calls.

${postdownpath}fog.updateunattend

That line is commented out in the tutorial. Remove the hashtag from in front of that line and it should update your unattend.xml file. You may need to update the code if your unattend.xml file is not found in the standard location.

[mperriello]

@george1421 we are using the unattended XML

[george1421]

@mperriello said in Windows 10 20H1 failing to mount C:\ directory:

but it is not domained or renamed as has happened in previous years

Are you using the FOG Client service to do this or the unattend.xml file? I use the unattend.xml file for that and not the fog service, fwiw.

[mperriello]

@george1421, thanks for the help, we are 2 steps forward as we no longer error out and now the drivers are seen and added. I think the problem we are facing now is the unattended.xml file as when the system reboots it dumps us back in the OOBE. If I answer those I see my image, but it is not domained or renamed as has happened in previous years.

[george1421]

@mperriello That code looks from a very old post. There has been an improved post download script here: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I have not tried the post install script on 20h1 or 20h2 yet but this updated code should find the proper partition for windows.