• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. seppim
    3. Posts
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 10
    • Posts 44
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Booting Rescue ISO

      @george1421 Hello,

      the content of the file is:

      PATH /sysresccd/boot/syslinux/
      DEFAULT loadconfig
      
      LABEL loadconfig
        CONFIG /sysresccd/boot/syslinux/sysresccd.cfg
        APPEND /sysresccd/
      

      Content /sysresccd/boot/syslinux/sysresccd.cfg:

      DEFAULT select
      
      LABEL select
      COM32 boot/syslinux/whichsys.c32
      APPEND -pxe- pxe -sys- sys -iso- sys
      
      LABEL pxe
      CONFIG boot/syslinux/sysresccd_pxe.cfg
      
      LABEL sys
      CONFIG boot/syslinux/sysresccd_sys.cfg
      

      Content sysresccd_pxe.cfg:

      DEFAULT select
      
      LABEL select
      COM32 boot/syslinux/whichsys.c32
      APPEND -pxe- pxe -sys- sys -iso- sys
      
      LABEL pxe
      CONFIG boot/syslinux/sysresccd_pxe.cfg
      
      LABEL sys
      CONFIG boot/syslinux/sysresccd_sys.cfg
      root@fog:/mnt/loop# cat sysresccd/boot/syslinux/sysresccd_pxe.cfg 
      INCLUDE boot/syslinux/sysresccd_head.cfg
      
      LABEL sysresccd_nbd
      TEXT HELP
      Boot the SystemRescue live medium (Using NBD).
      It allows you to install Arch Linux or perform system maintenance.
      ENDTEXT
      MENU LABEL Boot SystemRescue (NBD)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 archiso_nbd_srv=${pxeserver}
      SYSAPPEND 3
      
      LABEL sysresccd_nfs
      TEXT HELP
      Boot the SystemRescue live medium (Using NFS).
      It allows you to install Arch Linux or perform system maintenance.
      ENDTEXT
      MENU LABEL Boot SystemRescue (NFS)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archiso_nfs_srv=${pxeserver}:/run/sysresccd/bootmnt
      SYSAPPEND 3
      
      LABEL sysresccd_http
      TEXT HELP
      Boot the SystemRescue live medium (Using HTTP).
      It allows you to install Arch Linux or perform system maintenance.
      ENDTEXT
      MENU LABEL Boot SystemRescue (HTTP)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archiso_http_srv=http://${pxeserver}/
      SYSAPPEND 3
      
      INCLUDE boot/syslinux/sysresccd_tail.cfg
      

      Content sysresccd_sys.cfg:

      INCLUDE boot/syslinux/sysresccd_head.cfg
      
      LABEL sysresccd
      TEXT HELP
      Boot the SystemRescue live medium.
      ENDTEXT
      MENU LABEL Boot SystemRescue using default options
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701
      
      LABEL sysresccd_copytoram
      TEXT HELP
      Boot the SystemRescue live medium and copy system to RAM
      ENDTEXT
      MENU LABEL Boot SystemRescue and copy system to RAM (copytoram)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 copytoram
      
      LABEL sysresccd_checksum
      TEXT HELP
      Boot SystemRescue and verify the integrity of the live medium
      ENDTEXT
      MENU LABEL Boot SystemRescue and verify integrity of the medium (checksum)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 checksum
      
      LABEL sysresccd_nomodeset
      TEXT HELP
      Boot using basic display drivers to avoid display issues
      ENDTEXT
      MENU LABEL Boot SystemRescue using basic display drivers (nomodeset)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 nomodeset
      
      LABEL sysresccd_findroot
      TEXT HELP
      Boot from a Linux operating system installed on the disk
      ENDTEXT
      MENU LABEL Boot a Linux operating system installed on the disk (findroot)
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 findroot
      
      LABEL sysresccd_break
      TEXT HELP
      Stop during the boot process before mounting the root filesystem
      ENDTEXT
      MENU LABEL Stop during the boot process before mounting the root filesystem
      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701 break
      
      INCLUDE boot/syslinux/sysresccd_tail.cfg
      
      

      Did you know which settings I need in FOG?

      Maybe?:

      LINUX boot/x86_64/vmlinuz
      INITRD boot/intel_ucode.img,boot/amd_ucode.img,boot/x86_64/sysresccd.img
      APPEND archisobasedir=sysresccd archisolabel=RESCUE701
      

      Thank you!

      posted in General
      S
      seppim
    • RE: Booting Rescue ISO

      @sebastian-roth I see now, that the 5.5.2 ist very out dating.

      Current is 7.01

      Did you know which file and arguments I need for this?
      cp /mnt/loop/isolinux/{rescue64,initram.igz} /tftpboot/os/RescueCd/5.2.2/

      Both are in the 7.02 iso not available. Content of the isolinux:
      -r–r–r-- 1 root root 2048 Dez 20 13:10 boot.cat
      -rw-r–r-- 1 root root 432 Dez 20 13:10 isohdpfx.bin
      -rw-r–r-- 1 root root 38912 Dez 20 13:10 isolinux.bin
      -rw-r–r-- 1 root root 137 Dez 20 13:10 isolinux.cfg
      -rw-r–r-- 1 root root 119668 Dez 20 13:10 ldlinux.c32

      Thank you!

      posted in General
      S
      seppim
    • RE: Booting Rescue ISO

      @sebastian-roth wow, great. Thank you!

      posted in General
      S
      seppim
    • Booting Rescue ISO

      Hello,

      I’m new with FOG server and ask myself if I can boot a kind of own Rescue ISO file?

      So far as I understood FOG is for cloning images … but can I boot without changes also a live Rescue ISO?

      Thank you!

      posted in General
      S
      seppim
    • RE: 2 tasks for the same host not possible?

      @sebastian-roth great, thank you!

      posted in FOG Problems
      S
      seppim
    • RE: 2 tasks for the same host not possible?

      @tom-elliott hmmm … yes I have … you mean I just need to start the PXE task? I did not recognize that the host made automatic a reboot 🙂 Maybe I need wait longer?

      posted in FOG Problems
      S
      seppim
    • RE: 2 tasks for the same host not possible?

      @tom-elliott Hello Tom,

      unfortunately I need first the snapin and then the pxe.

      Many PC´s are running and I don’t want to go to each and power down.

      I thought I could force a restart and when he boot he do the other task

      posted in FOG Problems
      S
      seppim
    • 2 tasks for the same host not possible?

      Hello,

      I want to restart a group of PC´s for a new deployment or other.

      Here my Problem:
      I add a snapin to restart as a script. When I add this to the host, he restart in 1min … its working.

      But I want before set a task for the PXE boot … but when I add later the snapin task, he delete the previous boot task.

      Is it not possible to add more tasks to one host?

      Thank you!

      posted in FOG Problems
      S
      seppim
    • RE: AntiVirus

      @george1421 Oh, thanks for the info. Is there a way to use an AntiVirus to check the HDD?

      posted in FOG Problems
      S
      seppim
    • AntiVirus

      Hello,

      when I install FOG Server … should the ClamAV Antivirus working out of the box?

      He failed mounting path IP:/opt/fog/clamav

      but folder clamav did not exists.

      The Error is Permission denied … but guess it is not installed?
      Thank you!

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth oh, ok 🙂 Thank you!

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @george1421 Hello!

      ok, thank you. I have with this case now other questions. I don´t open a new post and asking here:

      1. I deploy a group via multicast (12 PC´s). Unfortunately one PC (PC07) has an another HDD and this was to small. So all other 11 PC´s waiting for this PC07 to start the deploy. But PC07 never start and I need to cancel all.
        1.1 Is it possible, to cancel just one or more PC while the other are waiting? When I check PC07 and click cancel task … he stop the multicast and all PC´s are canceled
      2. When I want to deploy a group … and some of the PC´s I want to exclude this one time … is this possible? He deploy always all PC´s and when I cancel some in the task, he cancel all (same as point 1)
      3. Update the Windows product key: I deploy a image, where the product key from the master is set. sysprep I don´t used, because after the PC are nor started. When I manual set the new product key in Windows and click activate, it is working. Can I set this also with FOG? I can add the product key in the host settings … but when and how I can write this to the client?
      4. While a multicast deploy to the 11 PCs, one was stopping (because of hardware problem) … but then all other 10 also stopping, because one of the PC was “lost” while write sda3 … can I manual delete this one problem PC, so that the other continue the multicast deployment?

      Thank you!

      All in all did the FOG server a great job and at least all 12 PC´s was deployed … but next time I want this faster, when I can handle the problems 🙂

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @george1421 Hello!

      Sure, no problem … from which PC you need to know the RAM?
      Master VM: 1024MB
      FOG server in Hyper-V: 2834MB

      I try to capture again.

      edit:
      yes, error:
      b7d1f054-63c5-46fb-a4e2-cb4ff53c29f3-grafik.png

      edit 2:
      I set the Compression back to 18 … then he start capturing

      edit 3:
      until compression 20 its working here … 21 and 22 throw error

      edit 4:
      no, after some time, he reboots … maybe running out of memory … but now error while startup the capturing

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth ok, deploy is now running.

      To set the timeout from 10 to 300 helps. The VM is waiting while the physical PC resizing /dev/sda2.

      PC: 250GB HDD
      VM: 10GB HDD

      Both booting after deploy! Great

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth Hello,

      capture is now running … sorry, guess it was my fault?

      I thought to use the latest kernel … but the list in the kernel module is not sorted by the newest. So I install 4.19.143 … I see this now and install now 5.6.18

      I also set the compression back … its now capturing!

      Sorry for the second issue … I try to capture and deploy on the physical and virtual PC and check if with multicast the problem stil exists (physical is resizing and virtual continue deploy)

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth Hi Sebastian,

      ok, this is a little weird … I try to capture again the Ubuntu Server 20 from my Virtual Box. HDD size 10GB.

      Not possible … seems not enough storage.
      But there are 50GB free:
      Fog server:
      708aa361-f7b9-463e-b21a-be0c37537f95-grafik.png

      Capture error:
      17e33be7-ae5b-49a3-a23e-fc77b8f885b3-grafik.png

      I´m not able to continue in debug mode … when I press Enter: nothing happens

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth Thank you … here are the contents:

      d1.partitions

      label: gpt
      label-id: 01BDEC12-F9A1-4F00-BFC2-2B10AFF0D320
      device: /dev/sda
      unit: sectors
      first-lba: 34
      last-lba: 3907029134
      sector-size: 512
      
      /dev/sda1 : start=        2048, size=        2048, type=21686148-6449-6E6F-744E-656564454649, uuid=9B59A7D0-D660-42E9-9098-CF8A334905E2
      /dev/sda2 : start=        4096, size=  3888156672, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=84C5FC93-D8A6-4B0A-B7CD-62C86A9A4232
      /dev/sda3 : start=  3888160768, size=    18868224, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=B2ED86A4-3D80-402F-8C38-3A5EA00C33A0
      

      d1.minimum.partitions

      label: gpt
      label-id: 01BDEC12-F9A1-4F00-BFC2-2B10AFF0D320
      device: /dev/sda
      unit: sectors
      first-lba: 34
      last-lba: 3907029134
      sector-size: 512
      
      /dev/sda1 : start=        2048, size=        2048, type=21686148-6449-6E6F-744E-656564454649, uuid=9B59A7D0-D660-42E9-9098-CF8A334905E2
      /dev/sda2 : start=        4096, size=      852852, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=84C5FC93-D8A6-4B0A-B7CD-62C86A9A4232
      /dev/sda3 : start=  3888160768, size=    18868224, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=B2ED86A4-3D80-402F-8C38-3A5EA00C33A0
      
      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth I did now the debug deploy and he show me: size to small.

      So I set from 10GB to 14GB (Master has 10GB) and did a debug deploy again:
      43723b3a-91f3-473f-890a-59d5168bc539-grafik.png
      1da48633-d69c-45ae-8062-814fa17acfec-grafik.png

      Then I delete the HDD in the VM and create a new with 25GB … same error.

      posted in FOG Problems
      S
      seppim
    • RE: Deploy with Multicast on different machines

      @sebastian-roth

      Both has 10GB HDD … I already deploy once to a VM … so this is weird.

      I think between this I made on the FOG Server a apt upgrade.

      lsblk:

      NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
      loop0                       7:0    0   55M  1 loop /snap/core18/1880
      loop1                       7:1    0 55.4M  1 loop /snap/core18/1932
      loop2                       7:2    0 67.8M  1 loop /snap/lxd/18150
      loop3                       7:3    0 71.3M  1 loop /snap/lxd/16099
      loop4                       7:4    0 31.1M  1 loop /snap/snapd/10492
      loop5                       7:5    0 29.9M  1 loop /snap/snapd/8542
      sda                         8:0    0   10G  0 disk
      ├─sda1                      8:1    0    1M  0 part
      ├─sda2                      8:2    0    1G  0 part /boot
      └─sda3                      8:3    0    9G  0 part
        └─ubuntu--vg-ubuntu--lv 253:0    0    9G  0 lvm  /
      sr0                        11:0    1 1024M  0 rom
      
      

      fdisk -l

      Disk /dev/loop0: 54.98 MiB, 57626624 bytes, 112552 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
      
      
      Disk /dev/loop1: 55.37 MiB, 58052608 bytes, 113384 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
      
      
      Disk /dev/loop2: 67.77 MiB, 71041024 bytes, 138752 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
      
      
      Disk /dev/loop3: 71.28 MiB, 74735616 bytes, 145968 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
      
      
      Disk /dev/loop4: 31.6 MiB, 32571392 bytes, 63616 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
      
      
      Disk /dev/loop5: 29.9 MiB, 31334400 bytes, 61200 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
      
      
      
      
      Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
      Disk model: VBOX HARDDISK
      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: 01BDEC12-F9A1-4F00-BFC2-2B10AFF0D320
      
      Device       Start      End  Sectors Size Type
      /dev/sda1     2048     4095     2048   1M BIOS boot
      /dev/sda2     4096  2101247  2097152   1G Linux filesystem
      /dev/sda3  2101248 20969471 18868224   9G Linux filesystem
      
      
      Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 8.102 GiB, 9659482112 bytes, 18866176 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
      
      

      mount:

      sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
      udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=458144k,nr_inodes=114536,mode=755)
      devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=100416k,mode=755)
      /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime)
      securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
      tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
      tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
      tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
      cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
      cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
      pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
      none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
      cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
      cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
      cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
      cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
      cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
      cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
      cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
      cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
      cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
      cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
      cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
      systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15888)
      hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
      mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
      debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
      tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
      fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
      configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
      /dev/sda2 on /boot type ext4 (rw,relatime)
      /var/lib/snapd/snaps/core18_1880.snap on /snap/core18/1880 type squashfs (ro,nodev,relatime,x-gdu.hide)
      /var/lib/snapd/snaps/core18_1932.snap on /snap/core18/1932 type squashfs (ro,nodev,relatime,x-gdu.hide)
      /var/lib/snapd/snaps/lxd_18150.snap on /snap/lxd/18150 type squashfs (ro,nodev,relatime,x-gdu.hide)
      /var/lib/snapd/snaps/lxd_16099.snap on /snap/lxd/16099 type squashfs (ro,nodev,relatime,x-gdu.hide)
      /var/lib/snapd/snaps/snapd_10492.snap on /snap/snapd/10492 type squashfs (ro,nodev,relatime,x-gdu.hide)
      /var/lib/snapd/snaps/snapd_8542.snap on /snap/snapd/8542 type squashfs (ro,nodev,relatime,x-gdu.hide)
      tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=100416k,mode=755)
      nsfs on /run/snapd/ns/lxd.mnt type nsfs (rw)
      tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=100412k,mode=700,uid=1000,gid=1000)
      

      lvscan:

        ACTIVE            '/dev/ubuntu-vg/ubuntu-lv' [<9.00 GiB] inherit
      
      posted in FOG Problems
      S
      seppim
    • 1 / 1