@kibade The hardware is identical on both machines. It is the same model 500gb seagate drive.
Posts made by coop90
-
RE: PartClone fail on deploy - error code 1
-
PartClone fail on deploy - error code 1
Server
- FOG Version: 1.3.4
- OS: Ubuntu Server 14.04
Client
- Service Version:
- OS: Windows 7
Description
I created a new image for one of our desktops (HP 6305). The image looked like it captured ok but when I tested the deployment, PartClone threw error code 1. I looked in /var/logs/ but dont see the partclone.log file.
Here is a video of the error:
https://www.youtube.com/watch?v=m7OGi9wdq-E -
RE: Partitions is not shrinking in windows 10
@Tom-Elliott The resize worked correctly. Thank you for quickly finding the solution!
-
RE: Partitions is not shrinking in windows 10
@Quazz Thanks! I will try on Monday and report back.
-
RE: Partitions is not shrinking in windows 10
I wont be able to try until Monday.
I am not so familiar with linux, where/how can I run the wget commands?
-
RE: Partitions is not shrinking in windows 10
Its MBR.
takes up 465gb which is followed by a 450mb recovery partition.
-
RE: Partitions is not shrinking in windows 10
After updating to 1.3.3, it is doing the same thing. It isnt shrinking the main partition.
-
RE: Partitions is not shrinking in windows 10
Thanks! I will update and retry the capture tomorrow.
-
Partitions is not shrinking in windows 10
Server
- FOG Version: 1.3.2
- OS: Ubuntu 14.04
Client
- Service Version: 0.11.8
- OS: Windows 10
Description
I am trying to capture an image from a windows 10 machine. (Our windows 7 machines captured fine.) The issue is, when single disk resizable is selected, it does not resize. Before partclone begins it says “not shrinking, fixed size.” When partclone is running it shows the correct device size (498.6gb) and the correct space in use (18.3gb).
This is going to prevent me from deploying to clients with a smaller hard drive.
Why isnt fog able to shrink the partition to the 18gb that are in use? Is there a problem with how the partitions were created?
Thanks!
I am seeing the same problem in 1.3.1 and 1.3.2 and now in 1.3.3.