Hosts not imaging - HELP
-
@prestop web interface, storage management, DefaultMember > Management Password
also, you’ll want to update the information in the hidden file /opt/fog/.fogsettings where it stores the password for fog upgrades
off the top of my head, i can’t remember where else it will be needed
technically, also FOG_TFTP_FTP_PASSWORD in fog settings. but that shouldn’t be important unless you change the IP of the server -
-
@Wayne-Workman
HOLY CR@P …Partclone started!!! Could it be???It looks like it’s actually moving quickly…ten more minutes.
-
@prestop oh yeah, btw, the trunk version of fog is faster. depending on circumstances, it can be a LOT faster. lol
-
@Junkhacker
Well, it looked as though it mostly worked , it did /sda1, /sda2 but then it said the disk was too small to image /sda3. the machine boots to the windows recovery console - like if you had your cd in the drive to restore windows. -
@prestop did you replace the drive with a larger one, as previously suggested? your non-resizable image will need to be deployed and recaptured to become resizable. you’ll want to check the “Schedule Shutdown after task completion” checkbox when you deploy, and then schedule a capture after it finishes. if you don’t boot up the computer after imaging, it doesn’t even have to be a computer compatible with the image you’re deploying.
-
@Junkhacker
I don’t have any larger disks in this junkpile left behind. -
@prestop Ever consider building a new image?
-
@prestop i’m afraid there really aren’t any other options. if you have a lot of storage available on another computer, you could create a virtual machine to deploy it to (but that’s going to have some headaches involved too). i’m guessing the original drive was 500GB?
-
@Wayne-Workman
Yes - but there’s a lot of programs and things that I don’t know much about that appear to be in the image. I was hoping to be able to figure it out at some later date. -
@prestop said in Hosts not imaging - HELP:
@Junkhacker
I don’t have any larger disks in this junkpile left behind.Order one. They are cheap.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
or even borrow one. once you just need to recapture the image, you won’t need it permanently.
-
@Junkhacker I don’t think so - I think it was this machine, it was listed as a tester but I don’t know. All the machines he previously did were these dells with 250G drives. Strange.
-
@prestop and what are you trying to deploy them to?
-
@Junkhacker same ones - Dells w/250G HDD. I’m trying a deploy w/debug now
-
@Junkhacker
So, these disks have 3 parts in them and the last one is too small on the device for the image stored? Does that sound right? -
@prestop from the errors you described before, that sounds right. the image size is too large for the disk. it runs out of space at the 3rd partition.
-
@Junkhacker bare in mind that non-resizable is really strict about size. being smaller by just a tiny amount is enough for it to fail. there aren’t a lot of circumstances where i recommend it over resizeable
-
@Junkhacker Doesn’t make sense to me - he didn’t have any different computers. What is confusing is that the image on the server is alot smaller than 250G.
-
@prestop that’s because of 2 things. partclone is file-system aware, and only copies the data in use, and fog compresses it.
however, a non-resizable image is a snapshot of the drive just as it existed on the source computer. when a resizeable image is created, a few more steps are taken before the image is uploaded, like shrinking the partitions down to the size of the data on the drives (plus some buffer space).
