• Ubuntu 14.04 with FOG 1.2.0 Problems

    Unsolved
    6
    0 Votes
    6 Posts
    4k Views
    Wayne WorkmanW

    @Clifford-Raymond Look at that line…
    Mount: mounting 10.10.0.235:/media/fog/images/images on /images faild: permission denied.

    you should start right there.

    Is that where your images directory actually is? /media/fog/images/images that’s very confusing.

    Go into Storage Management -> Your storage node & look at the image path. The image path should exactly match where the actual image directory is. I’d get rid of the /images/images thing because that’s very confusing.

    After changing this, you might want to look at your NFS exports file to confirm it matches. that’s here: /etc/exports

    You also need to have 777 permissions set on the /images directory recursively for troubleshooting purposes.

    This article talks all about that stuff: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS

  • Fog repositori not working

    9
    0 Votes
    9 Posts
    4k Views
    W

    Please continue to use git as that version is up to 4193 and the svn is at 3799. Tom is currently working on repushing the versions up.

    Again Tom will release an announcement when svn is up-to-date.

  • Unable to Login after IP Address Change

    Unsolved
    3
    0 Votes
    3 Posts
    1k Views
    Wayne WorkmanW

    What WiKi page did you follow?

  • Debian 8 and FOG

    1
    3 Votes
    1 Posts
    2k Views
    No one has replied
  • PXE Menu

    Unsolved
    3
    0 Votes
    3 Posts
    3k Views
    G

    Thank you for your reply. I will give it a shot.

    Greg

  • Bare metal imaging

    2
    0 Votes
    2 Posts
    2k Views
    Wayne WorkmanW

    @Scott-Adams Yup.

    It’s called a “raw” image type. But, I’d really recommend against that… really strongly… using a raw image type is 99% of the time not necessary and also ridiculous.

    When you come into the FOG world, you need to re-learn how you think of imaging.

  • issues with svn 3761 client version 0.9.2

    Unsolved
    5
    0 Votes
    5 Posts
    2k Views
    F

    Today I have installed svn 3783 which uses client 0.9.4 and the service error has gone.
    Another issue that remains is in host login history, where you can read logins/logouts but not username info.

  • Built in Driver Injection?

    3
    0 Votes
    3 Posts
    2k Views
    Lee RowlettL

    as Wayne said it’s not built-in oob but it’s easier to implement, you can even use postscripts which is very powerful - only restriction is your creativity 🙂

    https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins

  • Images being replicated without being associated with the group

    Unsolved
    17
    0 Votes
    17 Posts
    7k Views
    Wayne WorkmanW

    @Hanz Please check your messages, I left a few for you.

  • Can you make inf file a snapin

    Solved
    3
    0 Votes
    3 Posts
    2k Views
    D

    Figured out a solution I copied the PnPutil into the same directory as the inf than used SFXMaker to create the filesfxmaker.jpg

  • Imaging transfer rates - VM vs Physical machine

    21
    0 Votes
    21 Posts
    18k Views
    Wayne WorkmanW

    bumping this thread…

  • Host General view issue

    Unsolved
    4
    0 Votes
    4 Posts
    2k Views
    ch3iC

    @Hanz said:

    For the last few svn versions released, the general view screen for an individual host shows only…

    ${field}…${input}.

    Currently running 3726

    Have the same problem, Tom try to correct it.

  • Node Client Plugin usage ?

    2
  • imaging using a macbook pro

    Unsolved
    11
    0 Votes
    11 Posts
    6k Views
    R

    Unetbootin:

    http://unetbootin.sourceforge.net/ - download it for whichever OS you’re currently using.

    iPXE iso:

    http://ipxe.org/download

    OR as an alternative, you can use the Clonezilla live CD iso and choose the network boot option (which chains iPXE) – that’s located below:

    http://clonezilla.org/downloads/download.php?branch=stable

  • Second "server" to solve bios boot order problem if Fog server not available

    Unsolved
    11
    0 Votes
    11 Posts
    5k Views
    F

    Aha, thx! Surely i will do a try! Thx 🙂

  • Is there a special procedure for SSDs?

    3
    0 Votes
    3 Posts
    2k Views
    ch3iC

    @Andrew-Farney Just upload my HP Elitebook 820 with SSD (with trunk) and download without problem 😉
    @Wayne-Workman said:

    Upgrade to trunk and you can choose your partitions.

    https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

  • Failure imaging Dell XPS 13 9343 w/ Dell USB ethernet adapter

    Solved
    4
    0 Votes
    4 Posts
    3k Views
    P

    @Wayne-Workman Thanks. We’ll give that a try and report back in a few days.

  • Nodeclient plugin - Purpose?

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    N

    Ah. I see. Thanks.

  • Isos bootable trying to add to my menu Fog !! I fail ...

    Unsolved
    6
    0 Votes
    6 Posts
    4k Views
    Wayne WorkmanW

    @Eze84d Normally, the complete ISO is loaded into memory before it boots… how big is the ISO ? Do you have enough space left in RAM for it to fit?

  • FOG Checksum

    Unsolved
    2
    0 Votes
    2 Posts
    1k Views
    Wayne WorkmanW

    @Marc2 Probably yes and no… and it depends on when you do the checksum…

    If you are using FOG’s early hostname change, then a simple changing of the name on the OS disk would totally change the checksum. Booting the computers before the comparison is likely to totally change the checksum. The checksum must be done before namechange and before boot.

    This means you’d have to either schedule a shutdown after imaging and then boot to a linux live CD and do the checksum test, or, do a debug deployment and cancel the process right at the early host name change point and manually do the checksum during debug (which has very limited commands and you’d probably need to install some utilities right then and there) and then proceed to manually finish the imaging process via command line.

    I found this post on another site:

    But it depends on the layer you define “same”

    For this answer I assume

    /dev/sdb1 and /dev/sdc1 are the ones you want to compare both partitions are not mounted if they are mounted, you have the permission to read each file

    You can test the two partitions on blocklevel.
    ie:
    Code:

    md5sum /dev/sdb1 md5sum /dev/sdc1

    But for this to produce the same hash, the partitons have to be exactly the same.
    Even the slightest change in one of the files in either of the two,
    will produce a different hash.

    You can also test on filelevel.
    There are probably already tools, that could be used for your purposes (tripwire maybe?),
    but a quick-and-dirty solution can be this:
    Code:

    mkdir ~/comparedir sudo mkdir /mnt/test_sdb1 sudo mkdir /mnt/test_sdc1 sudo mount -o ro /dev/sdb1 /mnt/test_sdb1 sudo mount -o ro /dev/sdc1 /mnt/test_sdc1 find -type f /mnt/test_sdb1 -exec md5sum {} 2>/dev/null \; >~/comparedir/tmp_sdb1_hashes find -type f /mnt/test_sdc1 -exec md5sum {} 2>/dev/null \; >~/comparedir/tmp_sdc1_hashes sudo umount /mnt/test_sdb1 sudo umount /mnt/test_sdc1 sudo rm -r /mnt/test_sdb1 sudo rm -r /mnt/test_sdb1 sort -k2 ~/comparedir/tmp_sdb1_hashes > ~/comparedir/sdb1_hashes sort -k2 ~/comparedir/tmp_sdc1_hashes > ~/comparedir/sdc1_hashes rm ~/comparedir/tmp_sdb1_hashes ~/comparedir/tmp_sdc1_hashes diff ~/comparedir/sdb1_hashes ~/comparedir/sdc1_hashes

    Source: http://www.linuxforums.org/forum/miscellaneous/158910-can-i-compare-two-partitions.html

70

Online

12.7k

Users

17.6k

Topics

156.9k

Posts