@Logan

Problem solved :

I just disabled “fast boot” in the BIOS.

@george1421 alride thanks for the help. i will get to work then 🙂

@george1421 I might just try that, just for troubleshooting purposes.

Re: firmware - There is a BIOS update for the machines, and a firmware update for the NVM Samsung drive. Sadly, trying these was my first troubleshooting step (not listed here, because it was before I suspected components of FOG). I sure was holding my breath that it was the drive firmware though!

@tcs_taylor this doesn’t sound like expected behavior. we’re probably going to need help from the other developers if we can confirm this bug. we’ll also need details on exactly what version of fog you’re running

I had the same issue with T540p’s, a git pull and the 1.5.0-RC-10 resolved this for me also.

thanks you guys for advice, i solve the problem by change multi partitions all disks to single disk in Image options.

Hey @Tom-Elliott

I confirm that now everything works correctly. The error message was on one of the 2 partitions on the hard drive was too full. I will refine the settings and make you a return on the minimum size of available space to deploy.

I confirm that I capture and deploy on the same machine and therefore even hard drive. So no space problem available.

We can pass the inviter in resolve
As soon as I have the information on minimum available space I will add them in this topic

@+

@TThax You don’t need to actually download the client. The latest kernel, init, and client gets downloaded automatically when you run the fog installer. You just need to update to the latest FOG release candidate, run that installer, and you should be good to go.