Last active 2 weeks ago
Weird, before this when I try to shrink volumes it gives me an error. Now when I shrink the volume it uploads successfully. Thanks for the information, I will probably use shrink more often. However, I did notice some Linux OS did not allow me to shrink, is it because shrinking is a Windows only thing? Or should all OSes be able to do that?
I have a drive in my company where it has been overheating and is either failing or already reached failure. I tried to salvage the information inside the hard drive by using CloneDeploy. I received the warning in the picture and am not sure if it's possible to rescue the information inside. Please advise.
Besides that warning, it immediately closes and reboots the computer.
I believe this is the log for the block.
I'm trying to clone a 2TB hard drive, but only 300GB is used. When I try to deploy it onto a 500GB HDD, it doesn't allow me to because the minimum client size is 2TB. Compressing the block is out of the question as we have a specific sysprep file in the system that doesn't allow compression.
I was thinking of using file as that only stores the space that is used inside the HDD, but my file upload has been failing and returns "retrieving current directory: getcwd: cannot access parent directory..."
Any advice on what to change?
Thanks for the quick reply, will use it right now.
Is there a way for me to shut down my PC after imaging it? I have CloneDeploy setup in a local environment and I would want to connect my image PCs to the internet before turning it on.
Got it to work! I also updated CloneDeploy 1.2.1 and that solved my Linux imaging issues
I uploaded a new Ubuntu image onto my server and then I tried deploying it out (both onto new computers and old ones), I keep getting this error message and it exits me out of my active task. Not sure what settings do I toggle (This is after I finished removing the structure of the GPT partition with "sgdisk -Z /dev/sda"). It uploads successfully but deploys with errors.
Probing devices to guess BIOS drives. This may take a while.
I'm trying to get CloneDeploy up on a network where there are various other cloning solutions on the network already such as FOG. What would be the steps that I should take to get that working? Or even if that's possible of having that to work?
I think it was me having some SMB shares issue. I switched back to linux and now it works!