Issues with Downloading images FOG 1.2.0 CentOS 7
-
Well, minor update. I got the current SVN version from updating (3526 is what’s listed), and it seems to be having an issue with the old image I had from 1.2.0. Is there a known way to work with old images on the current SVN?
-
Yes.
First thing is to verify that the path is correct. Nevermind the image name, look at general - > path.
This must exactly match the actual path of the image, and it is case sensitive.
Second thing is to make sure FTP is good, third thing is to make permissions 777 recursively on the images directory.
and if the image was made with 1.2.0, it would be using partclone (not partimage).
-
Those all appear to be good, I’m getting an error something along the lines of “unable to location partition” when I try to do the clone. Do I need to change the image settings to only copy the MBR and partition table, or is there some other configuration I still need to do that I’m missing? It’s currently setup as a single disk-multiple partition, using Partclone. You guys really are saints for taking so much time to try and help me figure this out, if I haven’t pointed that out already.
-
is it an SSD?
Try single disk - resizeable. and under “partitions”, choose “everything”.
Also - a photo of the error you’re seeing would help greatly.
-
I’ll try it with single disk and see how it goes. In the meantime, here is a picture of the error I’m getting, which make sense given that the file doesn’t exist because it was never part of 1.2.0’s image setup as far as I could tell.
-
Can you post the output of this?
On your FOG server:
[CODE]ls -laR /images/Win7Prox64[/CODE] -
[root@localhost /]# ls -laR /images/Win7Prox64/
/images/Win7Prox64/:
total 9226228
drwxrwxrwx 2 root root 49 May 27 11:58 .
drwxrwxrwx 5 fog root 75 Jun 5 10:04 …
-rwxrwxrwx 1 root root 512 May 27 14:00 d1.mbr
-rwxrwxrwx 1 root root 8478104 May 27 14:00 d1p1.img
-rwxrwxrwx 1 root root 9439173435 May 27 14:18 d1p2.img -
chmod -R 777 /imagesif errors with operation not permitted…
sudo chmod -R 777 /images -
While I appreciate the advice Wolf, it’s not a permission issue in the directory so far as I can tell. It seems to be looking for a file that doesn’t exist.
-
This post is deleted! -
Just a quick update, I can upload an image from another client correctly, so it looks like the old image could be the issue. Will try with new image and see.
-
Well obviously the file doesn’t exist. When you uploaded you used Multi partition single disk right? We can see this by your file listing. However you need to reupload using single disk as Wayne was suggesting.
Just changing the option to single disk and trying to download will not create the files needed. Please change the image setting to Single Disk then upload the image. THEN download it another host.
-
Yeah I forgot to mention that the image type must match the old image type… sory.
-
Well I just uploaded an image from another machine, and I created the image as a Single Disk. It downloaded the first partition fine, however when I got to the second partition I got an error stating “this is not a partclone image”. So I’m at least halfway to getting things working. Going to go through the debug download again to see what comes out, will update shortly.
That’s the error I get when I reach the second partition on the image now.
-
You will need to change the “Image Manager” from partImage to partclone. Then reupload.
<OS>
<path>
Single Disk
Everything
<compression>
PartCloneUPLOAD!
-
This is a brand new image uploaded with the current version of FOG, so it’s already set to Partclone. I’m creating a new image from scratch to see if that will fix the issue, should have it ready later on this afternoon. I’m really at a loss as to why it isn’t cloning the second partition at this point.
-
Well after fighting with this thing for the better part of a week, I think I’ve finally got it stabilized. I’m on revision 3526, and I ended up creating a new image from scratch. Uploading and downloading finally work correctly, and while I do have an issue with the image, that’s a Windows issue not a FOG issue. Thanks to @Wayne-Workman for all his help, hopefully now you guys can move on to more important things, like a stable release.
