Last active 4 weeks ago
I just deployed another machine that had a Toshiba type SSD and completely different ending on the model number, and all appears well. I'll continue to keep an eye on it, but it looks like it's been solved.
Alright, I don't have any machines to deploy right now, but when the next batch comes in I'll give a quick update. Thank you for your help.
Looks like that did it! Coincidental that the SSD in my machine had the exact phrase you were parsing for. Since we get different machines with different models, will this change how they are imaged or break things if a different SSD model is used?
Oh yeah, I see that now. Why would it do that for just partition 2 though? For partition 1 and 3 it's reading the correct byte size.
I have not. A previous incarnation of the clonedeploy server had some changes, but I have since rolled back to a previous checkpoint and everything should be fresh. I just deleted the computer, group, and profile and rebuilt them but to no avail.
I have not changed anything recently, I'm running 1.2.1. What's even stranger is the same time I deployed this machine I deployed another that was a different type running an nvme drive and it worked fine. Same image, different profile. I have since tried to redeploy this machine, but got the same thing.
This is what I got.
This just started today after several successful uses on the exact same machine type. I'll start a task and deploy an image, and once it gets about half way through the file copy on the main partition it'll error out with "No space left on device". I've already wiped the drive beforehand and destroyed the GPT/MBR. Has anyone else had this issue? There is more than enough room on the partition it's copying to, it almost seems like it's not expanding the image before files are moved.
In the Computers, Groups, and Tasks tab, it'd be nice to have a Profile column to designate which profile of the image that is being used for that group or computer. I'm not sure what everyone else's case is, but I have one image with multiple profiles for each department, so it would make it easier to tell to who that laptop belongs.
That's what I'm thinking too. It's odd because if I run a task on a machine it will wake on lan, boot to PXE, then get the boot menu without continuing to the task. I did a little digging and found that the Proxy DHCP service was timing out and I had to restart it, so the DHCP proxy is at least semi-correctly configured. I'll have to look over it a bit more.