Downgrade to 0.32
-
Well,
Changing the image type for Multipart to RAW won’t work. RAW makes one large file of the device, where multipart makes a replica of each of the partitions.
-
Doing a raw I can tell it to grab the d1p1.img or d1p2.img and it will download that partition that was created. So to me it seems like some kind of linkage file is somehow missing that would command the workstation to grab the first one then the second one. The first one being that like 25meg thing it creates before the actually image.
-
[quote=“TylerC, post: 29531, member: 2655”]Doing a raw I can tell it to grab the d1p1.img or d1p2.img and it will download that partition that was created. So to me it seems like some kind of linkage file is somehow missing that would command the workstation to grab the first one then the second one. The first one being that like 25meg thing it creates before the actually image.[/quote]
What part of it will not work aren’t you understanding?
I mean, the point of the RAW image is it creates, essentially, a block by block clone of the disk. Usually set as /dev/sda
While you’re correct that you can RAW image Partitions, the way the partitions are created in MPS/MPA format is completely different than what you’re talking about doing. It will “try” to image, but it doesn’t know how to interpret the data.
Notice, with RAW format, there generally is no mbr file because its a block by block copy, where in your setup you have the MBR.
My question then, as I re-read your posting:
The image you’re working with is from 0.32 or 0.33?
If it’s from 0.32, what is the “type” of image as reported from the GUI. It should show in the “notes” section and tell you either Partimage or Partclone.
-
Sorry didn’t mean to sound like a jerk eariler or anything just getting a little flustered. The image was created when I was still running 0.32 and it is a Partimage.
-
Okay,
[quote=“TylerC, post: 29538, member: 2655”]Sorry didn’t mean to sound like a jerk eariler or anything just getting a little flustered. The image was created when I was still running 0.32 and it is a Partimage.[/quote]Can you try the information in this link and see if it helps you out?
[url]http://fogproject.org/forum/threads/how-do-i-sneakernet-via-usb-drive-a-32-image-to-a-different-1-1-0-fog-server.10733/#post-29529[/url] -
Still no luck, I did as the link said. When I went into the image it was already set to Partimage. I went ahead and changed it back to Multiple Partition All Disk. When I go to image the workstation it will get to the point where the screen is showing that the image is Windows 7 number of cores and everything. It is the screen right before where it starts downloading the image. It just reboots instead of downloading the image. I hope that makes sense.
-
Can you boot follow this guide:
[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]
My guess is partitioning information is a little skewed at the moment for that device. Don’t know why it happens, but sometimes it does.
-
Still no luck, this is not a one workstation issue. I can go to any of my 400+ workstations right now and the same thing will happen no matter what workstation or image I select.
-
Since upgrading, you’ve never been able to use this image?
Or did you image one system and reupload the image?
-
Never been able to use any images. Even a couple that I uploaded since the update.
-
Any suggestions or anything or am I out of luck and need to wipe my FOG server and start over from scratch?
-
I’d recommend exporting your hosts table from 1.1.0, then uninstall FOG Completely by deleting the FOG Database.
Install FOG 0.32 as you normally would, and perform the database update on the browser. Once that’s all complete, reimport your hosts. You’ll have to set the hostOS on the host once again, and recreate your images according to your setup. But once that’s done you should be good to go.
-
I did follow your steps on the formatting the drive bit but I noticed even after that if I run the compatibility test I get this message.
Error: Can’t have a partition outside the disk!
Under the results it shows Network and Disk as pass. I’m really not wanting to recreate these 7 images lol -
The image that you already have, what was the size of the hard drive you created the image on? Is it larger than the size of the disks you’re trying to put the image on?
The “Can’t have a partition outside the disk” usually means you created the image from a larger disk than what that particular drive can actually have.
-
No they are all the same size they deployed fine last summer and I haven’t made any changes since besides updating FOG.
-
I just checked and yep it is bigger is that some kind of bug with the new version of FOG?
-
When trying to image, is it set as Partimage or Partclone?
Have you tried changing the type to Partimage if it’s not set?
-
Yeah, it’s set to partimage.
-
It must be the drive size thing. I just went and tried to image one of my 320’s and it is working. So I’m only going to have to recreate my two 755 images. Praise baby Jesus! lol
-
before you do that just try change the value of FOG_UPLOADRESIZEPCT to 15
It is in the general settings.I seem to remember we had the same problem, a couple of years ago.
