Cannot Get Capture To Work (New Server)

[Tom Elliott]

@nbuursma Where do you see it saying it’s 1.2.0?

FOG did not have the function name reported in 1.2.0 when there was an error. Your screenshots show otherwise.

You can see the Version you’re actually running by looking at the GUI and in the cloud, or when the init displays the FOG banner before starting the task.

[nbuursma]

@Sebastian-Roth I’ve attempted it on different machines, Windows 7 and Windows 10… both get the same error and their both got different partition tables and completely different HDD types.

Do you still need it?

Side note - I tired using the desk test task to get a look that partition table for you and its hung “Scanning /dev/sda1…” for like 10 mins now.

[nbuursma]

@Tom-Elliott Is this what you’re looking for?

[Sebastian Roth]

@nbuursma The version you can see in the blue cloud on the web interface. Probably a number between five and six thousand. I doubt you see 1.2.0 in that cloud. Right?

Edit: Yeah, so you are running trunk version (will be 1.3.0 when finally released but is still under development right now). Probably best if you upgrade to the very latest version (update the checkout code and re-run the installer) and see if it works for you.

[nbuursma]

@george1421 … soo…5927?

[nbuursma]

@Sebastian-Roth said:

@nbuursma The version you can see in the blue cloud on the web interface. Probably a number between five and six thousand. I doubt you see 1.2.0 in that cloud. Right?

Gotcha! Sorry guys, yep its 5927, thanks so much!

[george1421]

@nbuursma said:

@george1421 … soo…5927?

As Sebastian said, its best if you have problems to upgrade the latest trunk release. The trunk releases are really dynamic as the bugs are squashed. Your version can get stale in a matter of hours. But the more things people run into the better the quality of 1.3.0 stable will be when its released.

[nbuursma]

@george1421 said:

@nbuursma said:

@george1421 … soo…5927?

As Sebastian said, its best if you have problems to upgrade the latest trunk release. The trunk releases are really dynamic as the bugs are squashed.

Okay, so how do I do this? (Again, I’m a total noob), do I use this?

svn co https://svn.code.sf.net/p/freeghost/code/trunk FogDownload

svn co https://github.com/FOGProject/fogproject FogDownload

Will that get me the newest version?

[george1421]

@nbuursma Well since you are already on a trunk version what did you do to upgrade from 1.2.0 stable? Did you use svn or git?

If you use svn, just change into the trunk directory [FogDirectory] and key in svn up then run the installer again in the …/bin folder.

No worries on being a noob. We all were at one time or another. Just hang in there we’ll get this worked out.

[nbuursma]

@george1421 said:

@nbuursma Well since you are already on a trunk version what did you do to upgrade from 1.2.0 stable? Did you use svn or git?

If you use svn, just change into the trunk directory [FogDirectory] and key in svn up then run the installer again in the …/bin folder.

No worries on being a noob. We all were at one time or another. Just hang in there we’ll get this worked out.

Ugh. I hate feeling so usesless…

I"m gonna talk this out like a toddler - ha!

So I need to “svn up https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_1.2.0/” ?

That URL I have is the same one I used to install my server yesterday, and the readme I get when I browse says 1.2.0… do I not have the correct version URL?

[george1421]

@nbuursma no worries here.

Just change into the directory where you already ran the svn program and it downloaded the files to.

SO assuming if you ran this command to initially download the svn trunk.
svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_trunk

To upgrade to the latest release you need to do this

cd /opt/fog_trunk
svn up
cd /opt/fog_trunk/bin
./installfog.sh

Then just follow the installer script again. It should pick up your previous settings so you don’t need to answer them again. Once the installer is complete then refresh the fog management page and the number in the cloud should be updated. Just be aware that the git and svn numbers will be different so don’t worry about that what you need is the cloud number.

[nbuursma]

@george1421 said:

@nbuursma no worries here.

Just change into the directory where you already ran the svn program and it downloaded the files to.

SO assuming if you ran this command to initially download the svn trunk.
svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_trunk

To upgrade to the latest release you need to do this

cd /opt/fog_trunk
svn up
cd /opt/fog_trunk/bin
./installfog.sh

Then just follow the installer script again. It should pick up your previous settings so you don’t need to answer them again. Once the installer is complete then refresh the fog management page and the number in the cloud should be updated. Just be aware that the git and svn numbers will be different so don’t worry about that what you need is the cloud number.

Thank you guys, its running now…

@george1421 said:

@nbuursma no worries here.

Just change into the directory where you already ran the svn program and it downloaded the files to.

SO assuming if you ran this command to initially download the svn trunk.
svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_trunk

To upgrade to the latest release you need to do this

cd /opt/fog_trunk
svn up
cd /opt/fog_trunk/bin
./installfog.sh

Then just follow the installer script again. It should pick up your previous settings so you don’t need to answer them again. Once the installer is complete then refresh the fog management page and the number in the cloud should be updated. Just be aware that the git and svn numbers will be different so don’t worry about that what you need is the cloud number.

Well I’m updated and all my settings stayed - yay!

But I’m getting the same error - but with more information maybe?

http://imgur.com/QnoooBh

Thoughts?

[george1421]

OK now that you are at the latest release the devs can start to work on your issue.

[george1421]

To acquire / steal a post from Sebastian.

“Could you please run a debug session on this device (WebGUI -> Host -> Basic tasks -> Debug) and run lsblk from the command line of the target computer? What do you get?”

We were also focused on the fog version (important to know). What device are you trying to capture (make and model). Does this have a traditional hard drive, ssd, or m.2 SSD drive?

[nbuursma]

@george1421 said:

To acquire / steal a post from Sebastian.

“Could you please run a debug session on this device (WebGUI -> Host -> Basic tasks -> Debug) and run lsblk from the command line of the target computer? What do you get?”

We were also focused on the fog version (important to know). What device are you trying to capture (make and model). Does this have a traditional hard drive, ssd, or m.2 SSD drive?

I’ll run the task right now, as to the device - currently its a Lenovo X250 with a Samsung SSD 850 EVO 120GB HDD

[nbuursma]

@george1421 said:

To acquire / steal a post from Sebastian.

“Could you please run a debug session on this device (WebGUI -> Host -> Basic tasks -> Debug) and run lsblk from the command line of the target computer? What do you get?”

We were also focused on the fog version (important to know). What device are you trying to capture (make and model). Does this have a traditional hard drive, ssd, or m.2 SSD drive?

Okay I ran it:

http://imgur.com/tVVvEj7

[nbuursma]

Oh! Okay… hmm… it appears that the x250s have a small SSD built into them perhaps?

Would that not having any partitions on it throw off Fog?

[george1421]

@nbuursma OK, that is where lenovo is hiding all of that malware lol.

I think that should be a question for the @Developers but the structure of the drives /dev/sda (etc) should not trow off FOG. But that 14GB empty hard drive might.

[Tom Elliott]

@george1421 depends on how it is seen in the system.

If the SSD is the first drive, it may pose a problem.

[george1421]

@Tom-Elliott His link to the image has this built in lenovo hard drive as /dev/sdb, where his main SATA SSD is /dev/sda. But who knows what format or partition table it has on this 14GB drive, let alone the reason why it is there truly there.