Posts made by dureal99d

@TaTa said in clone to smaller disk:

d1.fixed_size_partitions

im currently imaging with rc12 of 1.3.5 and it auto created the file “d1.fixed_size_partitions” so lets see what happens. Ill report progress as soon as the imaging is complete

@Tom-Elliott said in clone to smaller disk:

Seeing as RC 12 is out shouldn’t we start there?

yes @Tom-Elliott but i was not sure if the issue had been addressed in rc-12.

I shall try it and report back!!!

@george1421 ive edited reply since

@george1421 Yes with rc 11

its a windows 10 operating system

i deployed it using the standard compression rate “6”

and i get this error with a smaller harddrive

In previous version i could clone a 1 TB drive and if it only had 360 gigs of data on it i could still copy that data to a 500 gig hard drive.

I notice now as of build 1.3.5 RC 11, fog demands to have the exact same size drive.

Is this Normal for fog?

Well if it’s not harmful then that’s great. Wanted to make sure I didn’t break anything.

i am having this error.

when the drive spin up issue occurred i deinstalled and reinstalled fog.

no biggie, but now i get this error. any ideas?

@Tom-Elliott Worked Great!!!

Lately i have noticed that my secondary harddrive that contains my fog images constantly spins, at forist i though well maybe something is running in the background but then 48 hours later that same drive was still spinning.

I used “iotop” to see what was causing my drive to constantly spin and i found out it was realted to the fog server process (www-data)

I shall post a screen shot when i get home as i am currently not.

Has anyone else noticed this issue??

@george1421 I sure have disabled it but I kept the file for when I transport my fogserver to setup business sites. So it all comes in handy.

@Wayne-Workman Fabulous!!! I shall give it a try in a virtual machine. Feed back to follow.

I have a in home network with fog that i use to work on peoples systems almost daily. I also used a ddwrt router that recently died. It was becuaSe of this I chose to seek new options. Pfsense was that new option and i must tell you i am so happy with that option. with pfsense you don’t have to worry with what ipxe file to call upon as you can select it via pfsenses configuration even based upon a per machine bases. so if your environment is uefi & bios based those options are easily configured even down to the specific machine type as relates to what kind o file you want the fog server to call. I mean it is far easier than trying to use dnsmasq to call a certain file.

for example under Services/DHCP Server/LAN/Edit Static Mapping you can select a certain boot file based upon the settings at Services/DHCP Server/LAN = network booting tab.

Bottom line pfsense is great to use with fog and makes it a snap to get uefi and bios booting coexistence up and running

@Wayne-Workman Linux sees my drive as /dev/sdc1, however a booting fog sees my same boot drive drive as /dev/sdd1

@george1421 thank you

I know that fog does come with a way to make sure it images to a certain drive, I also know that fog uses a Linux layout "sdb1, etc, however I have loaded Linux to see how Linux see my system layout and for some reason fog does not see it the same way. so I am wondering if their is a way to check on how fog identifies your drives?

@saablord no problem

Agreed as i was taught by @george1421 inclusive to this i suggest you read my beginning struggles and later success with trying to achieve uefi ubuntu boot here

@Tom-Elliott Ok Thank You!!!

I use snapins and they are a godsend as far as I am concerned. I do wonder about some things though. When I select advanced and then snapins for a host I only get 2 options “single” or “all” clearly we know what a single snapin is but when fog say all snapins, is fog talking about only the snapins you have selected for that particular host or literally all snapins you have made? Inclusive to this it would be nice to be able to only select the snapins you want to be deployed

@Wayne-Workman said in How to deploy teamviewer ?:

@Ric41 said in How to deploy teamviewer ?:

The /S is okay, thanks a lot (without any window at the end). i regret that its not documented by teamviewer

They have no reason to help you deploy the non-enterprise version. Probably as soon as they learn the word is out, they will change the arguments.

You are right I was looking at their site and the only way I see that you can deploy and retain settings is if your corporation has a professional license with Teamviewer, or if you are one bad jama with programming of course.