Hosts not imaging - HELP

[Sebastian Roth]

@prestop said in Hosts not imaging - HELP:

It whips by and then reboots - if it doesn’t give an error message

In FOG 1.2.0 this usually happens when there is some kind of “faulty” partition layout on the disk. The tool used to enumerate disks and partitions was/is not very tolerant and freaks out easily - not giving any partition information. As FOG relies on that information to loop through the given partitions it just “whips by” if it cannot find any. Try booting the client into debug mode (FOG 1.2.0 -> Host -> Basic tasks -> debug) and run fogpartinfo --list-parts /dev/sda

[prestop]

@Sebastian-Roth
Thanks, I’ll try that…but I did format the drive into one big part as requested, etc. and I still got the same response.
My issue is that I"m out of time and I wanted to try the later version to get working.

[Wayne Workman]

@prestop So, please install fog trunk and see? This thread has gone on for so long, when fog trunk could potentially solve these issues.

[prestop]

@Wayne-Workman
UB says mk command not found
This is a make directory command, right?

[prestop]

@Sebastian-Roth
I tried this and it says:
Error: Can’t have a partition outside the disk!

This is the machine that was formatted into one big part with ntfs, it’s a 250GB disk. The image is much smaller than that. And I set the image to single/resizable.

[Tom Elliott]

@prestop Simply setting the image to resizable will not FIX anything. If it was uploaded as non-resizable, the partition table is still setup for the original source drive. If you need to make it resizable, the simplest solution is to set the image as resizable then re-upload from the master system.

[prestop]

@Tom-Elliott
Don’t have the master system anymore. That’s part of my issue.

[Tom Elliott]

@prestop Well I suspect a way to fix, find the largest harddrive (probably a 1TB drive?) and put it into the system.

Do a download task. Before letting it boot, immediately schedule that device for upload (using the image setup as resizable).

That should fix the resizable issue for you.

[prestop]

@Wayne-Workman
fog@heavyfog:~$ mkdir trunk
fog@heavyfog:~$ cd ~/svn/trunk/;svn checkout -r5428 https://svn.code.sf.net/p/freeghost/code/trunk ;cd bin; sudo ./installfog.sh
bash: cd: /home/fog/svn/trunk/: No such file or directory
The program ‘svn’ is currently not installed. You can install it by typing:
sudo apt-get install subversion
bash: cd: bin: No such file or directory
[sudo] password for fog:
sudo: ./installfog.sh: command not found
fog@heavyfog:~$

I believe I got it to make the directory but then I got all this.

[Wayne Workman]

@prestop sudo apt-get install subversion

Then rerun that command below.

Actually - I made some changes to it. here:
cd ~;mkdir svn;cd svn;svn checkout -r5428 https://svn.code.sf.net/p/freeghost/code/trunk ;cd trunk/bin;sudo ./installfog.sh

[prestop]

@Wayne-Workman
OK! It appears to be rolling now…updating packages, etc.
What do I do when it finishes?

[Wayne Workman]

@prestop at one point, it will ask you to update the db.

Go to the web interface and click the update button. It’ll be center page.

Then come back to the installer and continue.

After it’s done… just try it out.

[prestop]

@Wayne-Workman
Oh God…i walked away from the process and the computer locked. Now it doesn’t recognize my password. ?

[Junkhacker]

@prestop i noticed that you’re logging in as “fog”
i don’t recommend that, you should use a different user account.

[prestop]

@Junkhacker
That’s all i got. Can i finish as a guest session?

[Junkhacker]

that’s all you’ve got? the install instructions explicitly say not to create a user account named “fog” because the installer creates that account and sets the password

[prestop]

@Wayne-Workman how could my password change?

[prestop]

@Junkhacker
I didn’t set up the machine-the previous admin did.

[Junkhacker]

well, it looks like the fog installer changed the password for the “fog” user (which it sometimes does, it’s not supposed to, but when doing an upgrade from 1.2.0 it can happen. maybe something about the change in formatting of the .fogsettings file.) so it looks like you’ve got 2 options. reset the fog user password or restore your backup and create a new user account to do administration from.

[prestop]

@Junkhacker reset the password from AD?