• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Quazz
    3. Posts
    Q
    • Profile
    • Following 3
    • Followers 2
    • Topics 27
    • Posts 1,977
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: FOG resizes all partitions even System Reserved!

      @imt_fog If you boot the machine in question in debug mode, you should be able to run parted -l manually and check the flags.

      I don’t think this is caused by such, however, but interested in seeing the results.

      Worth noting that partitions that go through the checks but fail to resize get marked as fixed size as well (to prevent issues during deploy)

      posted in FOG Problems
      Q
      Quazz
    • RE: No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2

      @Sebastian-Roth https://github.com/FOGProject/fos/pull/24

      @HG12 Hopefully new inits will be available then!

      posted in Bug Reports
      Q
      Quazz
    • RE: No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2

      @Sebastian-Roth No, I mean in general, since the logic to extract fixed partitions and handle single partitions is already done in bin/fog.upload which is where the is_fixed variable is based on anyway.

      posted in Bug Reports
      Q
      Quazz
    • RE: No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2

      @HG12 There were some changes to how to detect which partitions to resize and which not.

      It’s supposed to not mark a single partition disk as fixed size, but it appears that’s not really working as expected, but looking over the code I’m unsure as to why.

      edit: Ah, think I may have found the problem.

      @Sebastian-Roth

      https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L462

      Why don’t we just test for if [[ $is_fixed -eq 1 ]] like on line https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L439

      This would simplify the code and put the logic on the initial fixed size file creation which makes more sense, imo.

      posted in Bug Reports
      Q
      Quazz
    • RE: No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2

      Try the latest init files. You need to manually download those from our server. https://fogproject.org/inits/init_32.xz and https://fogproject.org/inits/init.xz

      posted in Bug Reports
      Q
      Quazz
    • RE: Erasing current MBR/GPT tables.... taking about 5-10 minutes

      @Foglalt It’s slated for 1.5.6 I believe, but you can manually download them for the time being.

      It’s just the init files you need I think.

      posted in FOG Problems
      Q
      Quazz
    • RE: FoG with UEFI or Secure Boot?

      @jcabuco You can UEFI boot with secure boot disabled.

      Secure boot and bitlocker are unrelated. They can be enabled irrespective of the other.

      posted in FOG Problems
      Q
      Quazz
    • RE: Error during capture

      @Sebastian-Roth Looks good! Don’t think we thoroughly tested Linux at the time, not surprised it needed to be improved.

      posted in FOG Problems
      Q
      Quazz
    • RE: Dev branch fails install

      Change 0-1 to 0-9 over at https://github.com/FOGProject/fogproject/commit/71844d48ea00581f28ce56c28a8a63fc6166c38b

      You can do working branch as well of course.

      posted in FOG Problems
      Q
      Quazz
    • RE: Error "rcu_sched self detected stall on CPU" on legacy BIOS Capture job

      @george1421 The problem is for new kernels we need to update the kernel headers. Programs built against that (such as the programs in the init files) require the minimum supported kernel of those headers to run.

      In practice, it will often work anyway, but sometimes the changes make it impossible, nothing that can really be done about that from our side afaik.

      posted in FOG Problems
      Q
      Quazz
    • RE: Fog 1.5.5.3 - password install issues

      Yes, there’s a small mistake in the regex for the new password check. The whole password thing is getting a bit of a tune up.

      More details here: https://github.com/FOGProject/fogproject/commit/244b239641d8ff602e97441d1d6658e71e9593b0#commitcomment-32148121

      posted in FOG Problems
      Q
      Quazz
    • RE: DHCP release after FOG menu exit

      I think adding dhclient -r to /images/postdownloadscripts/fog.postdownload might work.

      posted in FOG Problems
      Q
      Quazz
    • RE: [SOLVED] Partition resizing problem

      @arnaudrigole I am glad you found a solution that worked for you, though I’m still interested in trying to at least guess at why the other partition scheme gave problems.

      Was there a difference in disk size in the SATA vs nVME SSDs?

      Perhaps the nVME SSD is smaller and the OEM partitition at the end of the disk was out of range, though we’d expect a different error for that.

      posted in FOG Problems
      Q
      Quazz
    • RE: Multicast issues - start session without reaching client count

      How is the multicast task started on the client? Scheduled per host through the Web GUI?

      posted in FOG Problems
      Q
      Quazz
    • RE: problem ACPI error

      @greezy said in problem ACPI error:

      ACPI Exception: AE_NOT_FOUND

      What’s between brackets after AE_NOT_FOUND? (screenshot would be helpful)

      Also… does it capture/deploy properly regardless of these errors?

      FOG version would be nice to know too.

      posted in FOG Problems
      Q
      Quazz
    • RE: Fog imaging and M.2 drives

      @dirtrunner21 I’d be interested to see if the speed improves any on the latest kernels. I do think it’s some kind of kernel/firmware issue (that being said, the kernel configs seem to already have all recommende options enabled/disabled as needed), although this one in particular isn’t nearly as bad as some others (some reaching only 8mb/s under certain conditions)

      Worth checking out an update to FOG 1.5.5 (which will automatically pull latest kernel and binary)

      posted in FOG Problems
      Q
      Quazz
    • RE: Can't deploy after migrating

      Is this quick deploy? Or from the WebUI interface?

      It looks like FOS can’t detect the MAC address for some reason, but since you got this far, it must obviously have one or DHCP would have failed much earlier in the process.

      posted in FOG Problems
      Q
      Quazz
    • RE: Fog imaging and M.2 drives

      I recall certain SSDs getting inexplicably low speeds.

      Here’s the discussion about it on the partclone github page:

      https://github.com/Thomas-Tsai/partclone/issues/112

      Currently not solved and obviously a pretty big problem if you’re experiencing this.

      Only info I’ve found myself is about 32 bit kernels on systems with 4GB+ RAM causing this issue.

      Some older topics suggest the DMA is sometimes disabled on SSDs for some reason.

      posted in FOG Problems
      Q
      Quazz
    • RE: Can't deploy latest win10x64uefi with 1.5.5

      @kAs1m Does this happen on non-VM as well?

      What kind of VM software do you use?

      Exit types are tricky at best in UEFI, throw in VM as well and it gets even more crazy.

      posted in Windows Problems
      Q
      Quazz
    • RE: Apache2 error-Won't download-We're DOWN :(

      @Dee You can delete old tar files safely.

      You have to enter the bin directory after extraction (before ./installfog.sh)

      So:

      cd Downloads
      tar -xzf fog_1.5.5.tar.gz 
      cd fog_1.5.5/bin
      ./installfog.sh
      

      the v parameter for tar stands for ‘Verbose’ and is always optional. (prints more info to screen)

      FOG creates backups in /home for every upgrade (both web files and DB backup), so you could clear out those files (or to be safe move them off your server to a storage system somewhere)

      Double check your /images/dev folder for stray unfinished capture sessions (the folders will be named to the MAC address of the device in question)

      posted in FOG Problems
      Q
      Quazz
    • 1
    • 2
    • 18
    • 19
    • 20
    • 21
    • 22
    • 98
    • 99
    • 20 / 99