There is not enough space on the disk

it appears the the issue has come back with the same error message

 "There is not enough space on the disk".
I have managed one build to upload on to the WDS
the work around tried last time was adding the "anonymous" user permission to the "remote install" folder in WDS  .

The image that has been uploaded to WDS has since been deployed also. The machine that has received the windows 7 image from WDS has had more applications added and then syspreped.

When the syspreped machine has been captured (F12 Nic card)
the image appears to fail on the upload to the WDS  with the usual error
 "There is not enough space on the disk".  (usually fails at the 35% mark)
the image size is 6.5 GB
the WDS has over 35 GB of space

the image captures to a USB drive without an issue.

is there any advice on this
IMG-00000196-hdr.jpg
lcolvinAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
lcolvinConnect With a Mentor Author Commented:
hello Felix it seems that the upload is now working. nothing has changed other than moving the network cable on to another port.
the problem resolved !
0
 
Felix LevenSenior System and DatabaseadministratorCommented:
WB :),

is there any diskquota on the WDS disk ? Maybe the drive is full, because someone did not want WDS to eat up all the drive space.

Best Practice with WSD is to always start a new OS install, Update, capture. It's not recommendet to update a previous capture Image and capture it again.
0
 
lcolvinAuthor Commented:
hello Felix there is no restriction on the disk quota.
the image has captured without an issue on to USB.  the image (WIM) seems to fail on the upload to wds with the same error message each time?
disk-quota.JPG
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Felix LevenSenior System and DatabaseadministratorCommented:
Well, I would try to update the NIC Drivers of the Capture Image, there must be a Problem if you can work with a local usb drive.
0
 
lcolvinAuthor Commented:
It appears the issue is coming from the windows PE environment.
I have setup a tracelog to help work out what could be happening.
What has been noticed is the image captures without issues. The image tries to upload but fails at 30%.
If I check the folder path x:\windows\tracing whilst the WIM file is uploading I can see the log recording the events. When the upload reaches 30% it then fails and clears the log. It seems as though the upload is unable to handle some of the file size it is trying to move. I’m not sure if there is a way round this?
wds-tracing.JPG
0
 
Felix LevenSenior System and DatabaseadministratorCommented:
What about preparing a new win7 SP1 x64 boot Image, include new/up to date NIC Drivers -> convert to capture Image and try the capture again.

FileSize can be limited by the filesystem like fat32 for example.

Sometimes it appears to me, that the drive letters are wrong and when you select C: or D: for the storagelocation of the WIM file, you chosse a to small partition, an active usb stick partion that is marked as a c: oder d: drive.

I just mention this because you were testing an USB drive for the WIM file, better unplugg it before you try to move the file to the server.
0
 
lcolvinAuthor Commented:
the movement of the the network cabel to a different port seemed to have made a difference
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.