• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. fogubuntu
    F
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 8
    • Best 0
    • Controversial 0
    • Groups 0

    fogubuntu

    @fogubuntu

    0
    Reputation
    318
    Profile views
    8
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    fogubuntu Unfollow Follow

    Latest posts made by fogubuntu

    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman I used the same settings as the source machine on the clients and I still get the blank screen or Starting cmain() message and the OS won’t load.

      Is there any other settings I should look into to fix this?

      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman said in Ubuntu Image for FOG Clients:

      When and on what? The reference machine? The destination machine? Before capture? After capture? Before deployment? After deployment?

      I changed the setting on the destination machine after deployment.

      Using the same settings as the reference machine did not work either.

      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman I did try all the exit types but I will give this another shot. What is the difference between Host BIOS Exit Type and Host EFI Exit Type?

      I did also change the boot type on the client machine’s BIOS to UEFI.

      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman Following is the output for df -h:

      Filesystem      Size  Used Avail Use% Mounted on
      udev            7.8G     0  7.8G   0% /dev
      tmpfs           1.6G  9.7M  1.6G   1% /run
      /dev/sda2       213G   12G  191G   6% /
      tmpfs           7.8G  260K  7.8G   1% /dev/shm
      tmpfs           5.0M  4.0K  5.0M   1% /run/lock
      tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
      /dev/sda1       511M  3.6M  508M   1% /boot/efi
      tmpfs           1.6G  4.0K  1.6G   1% /run/user/108
      tmpfs           1.6G   56K  1.6G   1% /run/user/1000
      

      And the output of fdisk -l

      Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      
      
      Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: gpt
      Disk identifier: 4430D5FA-2CED-4B96-A4E8-E41E0DAFEE53
      
      Device         Start       End   Sectors   Size Type
      /dev/sda1       2048   1050623   1048576   512M EFI System
      /dev/sda2    1050624 455012351 453961728 216.5G Linux filesystem
      /dev/sda3  455012352 488396799  33384448  15.9G Linux swap
      
      
      Disk /dev/sdb: 7.5 GiB, 8015314944 bytes, 15654912 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x15e2543d
      
      Device     Boot Start     End Sectors  Size Id Type
      /dev/sdb1  *        0 3035519 3035520  1.5G  0 Empty
      /dev/sdb2       14432   19295    4864  2.4M ef EFI (FAT-12/16/32) 
      
      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman I did change it there too. Changing in the default for newly registered hosts worked the same way. Some options resulted in a blank screen with a blinking cursor and some had a message saying Starting cmail()... and nothing happened.

      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      @Wayne-Workman Yes, I tried all the exit types. I changed this in the following location:

      FOG Configuration > iPXE Boot Menu > Exit to Hard Drive type

      posted in Linux Problems
      F
      fogubuntu
    • RE: Ubuntu Image for FOG Clients

      Thank you for the response. Manually changing the boot order on each machine should not be an issue. However, once I do this and have the clients boot the FOG PXE menu and select Boot from disk, I get a blank screen with a cursor and the OS does not load.

      Will re-installing Ubuntu on the source machine without LVM fix this? I am unable to determine what is causing this.

      posted in Linux Problems
      F
      fogubuntu
    • Ubuntu Image for FOG Clients
      Server
      • FOG Version: 1.3.5
      • OS: Ubuntu 16.04
      Client
      • Service Version: 0.11.11
      • OS: Ubuntu 16.04
      Description

      I created a source image on one of my client machines and installed FOG client as well. I was able to successfully capture this image and clone to multiple machines with ease. However, after cloning the BIOS seems to boot straight into the OS and does not boot over the network.

      After seeing this, I manually changed the BIOS settings on the new cloned machine to boot first from the network. This made the cloned machine boot from the FOG server first and then after choosing the Boot from disk option, all I see is a blank cursor and nothing loads. I played around with the BIOS Exit Type in FOG and instead of a blank cursor I got a message along the lines of waiting for PXE.... Starting cmain() and nothing happens after that.

      Here are my questions:

      • How should I prepare my source image? Do I need to disable some bootloader option when I Install the OS on my source machine? I would my client machines to boot from the FOG server first before the cloned OS so that I can wipe the drive, re-image etc.
      • How do I prevent the BIOS boot order from changing after installing Ubuntu?

      My goal is to be able to clone multiple machines with the source image (which I’ve already done) and then be able wipe these cloned machines and overwrite them with new images when needed. if the machines boot straight to the hard drive then I will not be able to do this.

      I did manage to install FOG client on the machine, but I have not been able to issue commands to FOG client and couldn’t find any instructions on doing so. Any help regarding this would be appreciated as well.

      posted in Linux Problems
      F
      fogubuntu