Posts made by Jordonlovik

Ok so imaged the PC with the Bios set to ATA. this time no errors. Already purchased new License for windows. Thanks Tom

@shoong after uploading i changed the new host to ATA and it booted. However It will not let me authenticate my windows 7 key. Says that my bios is not licensed and so im stuck there. Would the next step be to play with the Bios on the Host im taking the image from? This Host is extremely important and i would hate to F something up on his computer. The new host i deployed to was set to Raid in the bios (which i then changed to ATA after deployment).

In the Optiplex Bios
On Raid(default): Will not boot
ATA: boots but gets below error
AHCI: Will not boot

For clarification purposes. I am trying to take a Custom Build Host1 (gigabyte MotherBoard) to an Optiplex 9020 Host2

I had the same issue moving from one Bare metal Machine to an Optiplex. Set the SATA port to ATA and it booted. I will be uploading the image with better compatability like need2 mentioned here.

@need2 said:

Windows 7 still thought SATA was a little hard. Before you upload the image, you should generalize the way Windows handles its storage drivers. HowTo:

http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation

What that will do is force Windows to try multiple different types of storage driver on boot, instead of just the last one it used. The reason you are having this is that the VM likely used a form of IDE driver, and your Dell Optiplex 3020 defaults to AHCI mode on its SATA port.

If you really didn’t want to upload the image again, you could go to the BIOS and change the SATA mode to IDE or Compatibility. This should allow you to boot at least, but you will be running the drive controller much slower than it is capable of.

FYI that link is broken.

Ok i think i fixed the issue. One of my images was way way to big (probably bad) and the other had the wrong storage configuration attached. once i changed to single disk multiple partitions the lighter image worked. Yippie!

everything completed successfully. the only thing that didn’t say Done! or Complete was. Backing up and replacing BCD… BCD not present. Also the host didn’t restart at the end like it said it would.

I recently installed a fog Version 4956 on Fedora 22 64bit server. Everything went as planned with installation and first image upload. However when i attempt to download that image to a new host nothing happens. I setup the task for download then reboot the host to network and for some reason it just brings me to the FOG splash screen with options to register host etc… etc… Once I shutdown the destination host and check on the FOG tasks I see that the download task dispersal. as if it actually deployed the image. I get no warnings or error. I have tried using a new similar image i uploaded with the same results.

Thanks Tom. Fixed the issue. Here is what I did in case it saves anyone a step. i am now running v 4956

cd svn 
svn checkout https://svn.code.sf.net/p/freeghost/code/trunk

cd ~/svn/trunk/bin 
./installfog.sh

@Tom-Elliott is there a wiki article on that?

@Tom-Elliott said:

This is fixed in latest trunk. Sorry had a bad method call.

My install is brand new too 4938. Should i be rerunning the ./installfog.sh? I want to make sure i do this right. I find it strange that i did the SVN install originally which says its at version 4157. Would have thought that would have been my version.

Having the same issue on my newly installed Fedora22 server. How would i go about updating?

@need2

Thanks. I began reinstalled using Fedora 22 server 64bit. hope to have FOG back up and running soon.

@Wayne-Workman You don’t prefer Kubuntu for FOG setups?

At this point I am strongly considering a full reinstall of the server. Although it was labor intensive. I was just starting to experience the wonder of FOG imaging too. and I love it.

@Tom-Elliott said:

10.1.1.201, but the new node (which I imagine is on the same s

I noticed this myself. I changed that and am sill experiencing the same error.

@Wayne-Workman Sorry im saying that wrong i am actually modifying the /etc/exports file! I don’t know how or why i was thinking .mntcheck still. It looks like i may have F’ed my server over anyways. This is my first run at Linux and its been a bumpy one. I was not able to edit the /etc/Exports file because it was owned by root. So i ran the 777 permissions command not knowing the consequences. now i am getting the Sudoers is world writable error. I wish i had realize my install partitioned so idiotic by default. i have plenty of storage space its just not in the root directory where it needs to be.

@Wayne-Workman Is there any other way to edit the .mntcheck file? the vi editor is really giving me trouble through my remote session.

@Wayne-Workman yes it does thank you. all i have to do is add two new lines with new IDs that correspond with the new node location.

@Wayne-Workman So essentially I am editing the old original .mntcheck files copying their contents, editing them to reflect my new location, changing the 1 to 3 and the 2 to a 4 and then saving that data over my new .mntcheck files in the new location under /media/administrator/Fogdrive. Do I have that correct?

@Wayne-Workman Ok so i think i followed you up untill the last part

@Wayne-Workman said:

After the new drive is formated and mounted and you can SEE it in the linux system,

open the CLI, go to the new image directory (wherever you mounted it)

create a .mntcheck file there, then create the dev folder and a .mntcheck file in there.

touch .mntcheck;mkdir dev;touch dev/.mntcheck

The new directory needs 777 permissions assigned to it recursively as well (you may change this later after it’s working)

I’m keeping my instructions and commands here generic so that this can help others.

chmod -R 777 /the/path/to/your/new/hdd/mount/goes/here

Then you need to add the new images and new dev folders to the exports file:

vi /etc/exports

You’ll see the two lines in there already for your old local storage node. They will have IDs, and in 1.2.0 they start at 1.
Copy those two lines, change the IDs to 3 and 4. Modify the paths so they are correct.

Then either reboot or restart NFS and RCP.

Could you expound on what the last step does?

@ITSolutions I did what you said. formatted for Ext4 (same as Root). I am getting the same error.

Ext 4 does not allow me to create new folders so this time i just made the location /Fogdrive