Posts made by cnkpadobi

@george1421

No did not know it had to 2 disks on one show up in the UEFI bios… which is the SSD 256. My image does not have multi-disk but just has two partition.

Thanks

Thu Apr 06, 2017 18:39 pm
Running Version 1.4.0-RC-1
SVN Revision: 6069

I am trying to capture an image from Hp Detachable and HP Stream computers.

The capture starts well but they both get stuck around 97% and does not prgress forward. The task is still running on Fog Server when get stuck and does not go futher.

Hmmm so how would it point to the d2.mbr instead of the d1. I am deploying it now on the new machine… Would that have something to do with the flash drive fos?

Running Version 1.4.0-RC-1
SVN Revision: 6069

• OS: Ubutu

Client

• Service Version:
• OS: Windows 10

Description

Hello

I am having an issue with the deploying an image on a Toshiba laptop it seems to corrupt my image

image store corrupt unable to locate mbr

I have able to deploy successfully this image to other machines prior this one but now getting this message. When I look at the image on the fog server it now says 0.0 bytes but before this error started, it said 149.5 GB

Now When I try to deploy this image on a different machine other the Toshiba it works just fine…, And now the image does not say 0.0 bytes but now back to the original image.

Here is an better pic… Yes I will update tonight.!

this worked great issue resolved.

Server

Wed Mar 22, 2017 20:34 pm
Running Version 1.3.5-RC-13
SVN Revision: 6067
Ubutu 14

Client

• Service Version:
• OS: Win 10

Description

Hello, I am getting this issue when I trying to capture a win10 HP machine. it completes the capture successfully but constantly get this error.


@george1421 Thanks for this… just a quick clarification is there a space after the comma before the ip address

ok sorry,

So I am still gett this error
dnsmasq: bad option at line 2 of /etc/dnsmasq.d/q

the only thing inthe ltsp.conf on line two is port=0

there are no other config files in the directory

@george1421 should those configure files be rename or removed?

@george1421

YES, all 3 config files are in that directory

@george1421 so if I run the sudo netstat -an|grep 4011 it should give me something correct versus taking me back to the prompt?

@george1421

Here are the files listed

ltps.conf ltsp.conf ltsp.conf~ network-manager README

that command does not produce any results

@george1421 not sure this is what it says

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

@george1421 I dont think it is started but when I try I get this message

dnsmasq: illegal repeated keyword at line 2 of /etc/dnsmasq.conf

root@imagingvm:~# nobody 1502 0.0 0.0 33140 3132 ? S 15:41 0:01 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
root 14476 0.0 0.0 18316 2292 pts/14 S+ 17:42 0:00 grep --color=auto dnsmasq
nobody: command not found
root@imagingvm:~# root 14476 0.0 0.0 18316 2292 pts/14 S+ 17:42 0:00 grep --color=auto dnsmasq

It was prior to making the change to have fog server to do the work and use dnsmasq …

0_1489707295938_output.pcap

When it was working in legacy boot it was in the appliance

Just to make sure we are on the same page. Since I am using a hardware dhcp server. I took the option 66 and 67 off the appliance and allow the fog server dnsmsq to handle everything correct?

I edit the dnsmmsq file and made the change suggested in the previous post.

Before I made those changes was able to legacy boot but not UEFI boot. Now we cannot do either.

Just recapping to make sure we are on the same page before proceeding.

Yes my dhcp server and is on the same subnet

it also says not bootfile name recieved.