• 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: The future of partclone and therefore FOG as it is

      @george1421 Well, we did find a resize bug in the inits, particularily on fast disks.

      Might be time to revive this idea soon and test it out again.

      posted in General
      Q
      Quazz
    • RE: Debian 10 libcurl3 install problem, solved?

      @JGwinner FOG 1.5.7 is out now with Debian 10 installation support if you want to give it a try.

      posted in Linux Problems
      Q
      Quazz
    • RE: Fog image size too big (500 GB/takes around 2hours to capture and deploy)

      There’s something strange going on here, you 😄 drive is 900GB yet partclone only reports 500GB?

      It also says /dev/sda1, though on windows 7 we’d expect /dev/sda1 to be a partition called “System Reserved”

      Can you post a screenshot of disk management here?

      posted in FOG Problems
      Q
      Quazz
    • RE: Image sharing between sites

      @KennethJ Perhaps the API? https://news.fogproject.org/simplified-api-documentation/

      posted in FOG Problems
      Q
      Quazz
    • RE: Full C:\ After Imaging Inconsistent

      Issue is likely similar to if not the same as

      https://forums.fogproject.org/topic/13440/fog-1-5-6-auto-resize-is-unpredictable

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Eric-Johnson Very interesting, here’s what sfdisk man page has to say about it.

      sfdisk uses BLKRRPART (reread partition table) ioctl to make sure
             that the device is not used by system or another tools (see also
             --no-reread).  It's possible that this feature or another sfdisk
             activity races with udevd.  The recommended way how to avoid possible
             collisions is to use exclusive flock for the whole-disk device to
             serialize device access.  The exclusive lock will cause udevd to skip
             the event handling on the device.  For example:
      
                    flock /dev/sdc sfdisk /dev/sdc
      
             Note, this semantic is not currently supported by udevd for MD and DM
             devices.
      

      So perhaps adding flock $disk before sfdisk $disk < $file will resolve it

      Making the line read as flock $disk sfdisk $disk < $file

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Sebastian-Roth From what I gather, it’s an issue that isn’t happening under every circumstance (personally haven’t ran into it, having deployed to hundreds of devices over the course of each new init release), but does happen reliably under certain conditions.

      It seems odd that a momentary delay in the script or otherwise a sync of the “disk” (as in the ramdisk) would prevent this issue from appearing again.

      From what I can tell, people did start reporting such issues after a certain version, perhaps a buildroot update (Just looked and Buildroot version 2019.02 has bugfixes up to 2019.02.4 now! changes list: https://git.busybox.net/buildroot/plain/CHANGES?id=2019.02.4) ? People tend to wait a while before updating, so we may have to look a bit further back.

      posted in Bug Reports
      Q
      Quazz
    • RE: Windows 10 temp file clean up - Error(5) shrinkPartition - Capture fail

      @duanekaeb On Windows 10 when you run “defrag” on an SSD it will run “trim” on it instead, so yes, it is.

      You may want to schedule a chkdsk as well.

      posted in Windows Problems
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Eric-Johnson I mostly wanted to see it before and after your cat and ls commands and such, but I don’t think it matters, since 2000+ should be more than enough for just about anything anyway.

      I was thinking that perhaps certain hardware wouldn’t generate enough entropy in time and that that would cause issues.

      @Sebastian-Roth @Tom-Elliott Do you reckon it would be good idea to try and store the output in a variable as opposed to a file and use it as such?

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Eric-Johnson Interesting. Could you add

      cat /proc/sys/kernel/random/entropy_avail
      

      before and after your output commands?

      Just a wild hunch

      If my hunch is correct, then I suspect you could replace your output commands with any other output commands and it would work. Alternatively, you could smash the keyboard a couple of times.

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      I created a PR to fix some stuff and to hopefully handle errors better/more reliably.

      I don’t think it will fix this problem necessarily, but it should should hopefully throw errors when we expect it to.

      https://github.com/FOGProject/fos/pull/26

      You can download the inits of it here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/PR-26/2/artifacts

      if you’re interested in testing it out.

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @george1421 There were some changes to GPT related stuff, not a lot, but some

      https://github.com/FOGProject/fos/commits/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib

      I also think I remember a case where an existing image only started showing odd issues after updating FOG, so I’m currently leaning towards FOS, especially since I have experienced no problems on the latest Windows 10 versions at all.

      So I’m guessing there’s something funky going on under certain conditions, but not sure what. Given the ambiguity it might not even have anything to do with GPT, but since those were the only relevant changes to the files currently being examined it seems the most likely path all the same.

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Cheetah2003 OS-built recovery partitions have the partition flags that keeps them fixed size.

      The reason for multi partition resize is in case you have your normal partition layout (fixed size 1-3 + Windows partition) and an additional data partition.

      eg

      /dev/sda 1 200mb
      /dev/sda2 800mb
      /dev/sda3 200mb
      /dev/sda4 30GB
      /dev/sda5 200GB

      You can’t automagically know which of the last 2 partitions to resize and which to ignore. Windows needs room to breathe, but if you deploy this to a 2TB drive then having a 1.8TB windows partition and 200GB data partition feels silly.

      I agree that the current method isn’t good enough, of course, but it’s not without its logic.

      Back to the topic of trying to figure this (this being why sometimes partitions don’t resize) out, as far as I can tell, these resize issues only occur on GPT based layouts.

      I’ll be looking over partition-funcs.sh in that sort of a direction.

      posted in Bug Reports
      Q
      Quazz
    • RE: Error trying to restore GPT partition tables. Exit returned code 4

      @Matthieu-Jacquart What’s on the first partition? It’s currently not marked as fixed size, is this to be expected?

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Sebastian-Roth Corrected the cli as per the info given, same results however.

      I am using gawk because I’m running the tests on my Centos machine and if I don’t explicitily call gawk it will run awk (which for some reason gawk isn’t symlinking too on this system) which misses out on a variety of the requirements used in the script (and lint)

      Forcing a skip in the for loop at line 563 delivers the output makes it look more normal, but then the partition table doesn’t make sense since the starts aren’t properly recalculated.

      My gawk version seems to be an older version than the one Buildroot has been running for a while, so I’ll see if a newer version delivers better output.

      Gawk version was the issue indeed. (was 4.0.2, now 4.2.1)

      New output:

      # Partition table is consistent.
      label: gpt
      label-id: 6D7D4E9F-F276-4554-945E-D42EF1DB667D
      device: /dev/sda
      unit: sectors
      first-lba: 34
      last-lba: 1871362046
      
      /dev/sda1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=0E09A256-6313-43EA-9C45-1BDB234A17A3, name="Basic data partition", attrs="RequiredPartition GUID:63"
      /dev/sda2 : start=     1085440, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E004F3EB-3497-45AC-8BC2-40BF62ECF868, name="EFI system partition", attrs="GUID:63"
      /dev/sda3 : start=     1288192, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=B4553686-67E2-4177-BC7D-AC092860D2CF, name="Microsoft reserved partition", attrs="GUID:63"
      /dev/sda4 : start=     1320960, size=   188101120, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=0005FBFB-A630-456B-9938-D501F6F70B00, name="Basic data partition"
      /dev/sda5 : start=   189422080, size=  1681939456, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=5F76FA4B-76D2-43B0-8ECB-F3EB8596E490, name="Basic data partition"
      

      By the way, @Cheetah2003 looking over the code, I think what it tries to do is assign the new size as a the same percentage as it took on the previous image if the partition is resizable. At least that’s what the intention is supposed to be.

      The output here looks valid and more or less what we expect the script in its current iteration to do; but I could be missing something of course.

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Sebastian-Roth Out of curiosity I tried that out and got some strange results. (resizable gets early “start positions”) I then ran

      gawk /usr/share/fog/lib/procsfdisk.awk --lint -v SECTOR_SIZE=512 -v CHUNK_SIZE=512 -v MIN_START=2048 -v action=filldisk -v target="/dev/sda" -v diskSize=187136208 -v fixedList="1:2" d1.minimum.partitions d1.partitions
      

      (gawk has a --lint option apparentally)

      this threw a slew of warnings, haven’t had the oppertunity to go through them (I suspect most of them to be irrelevant), but figured I’d mention this option, could help in figuring this out.

      EDIT: Aside two (minor) issues (such as line 545 (unquoted gpt label check)), couldn’t find anything through the lint option personally. (although I do wonder why non-fixed partitions seem to not be passed their original size. EDIT2: figured out this bit, corrected it, but still strange output, will paste below)

      # Partition table is consistent.
      label: gpt
      label-id: 6D7D4E9F-F276-4554-945E-D42EF1DB667D
      device: /dev/sda
      unit: sectors
      first-lba: 34
      last-lba: 1871362046
      
      /dev/sda1 : start=  1870042624, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=0E09A256-6313-43EA-9C45-1BDB234A17A3, name="Basic data partition", attrs="RequiredPartition GUID:63"
      /dev/sda2 : start=  1871126016, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E004F3EB-3497-45AC-8BC2-40BF62ECF868, name="EFI system partition", attrs="GUID:63"
      /dev/sda3 : start=  1871328768, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=B4553686-67E2-4177-BC7D-AC092860D2CF, name="Microsoft reserved partition", attrs="GUID:63"
      /dev/sda4 : start=        2048, size=   188101120, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=0005FBFB-A630-456B-9938-D501F6F70B00, name="Basic data partition"
      /dev/sda5 : start=   188103168, size=  1681939456, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=5F76FA4B-76D2-43B0-8ECB-F3EB8596E490, name="Basic data partition"
      

      Problem appears to steam from the for loop at line 562

      posted in Bug Reports
      Q
      Quazz
    • RE: Error on image upload

      @Sebastian-Roth Ahhh, that makes sense, good find!

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Cheetah2003 So did your recovery partition have no label at all or what was it exactly? (should clarify that label is basically the user editable “name” of the partition such as “System Reserved”)

      If it didn’t have a label, then I’m kind of confused about how it wouldn’t get resized since it most certainly should have.

      There’s actually something very strange in this case, which is that your partitions and min.partitions file is the same. (maybe you accidentally pasted the wrong one?)

      posted in Bug Reports
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      I’m guessing the partition label is something like “Recovery” which is why the old inits picked it up.

      The problem with the label system was that it was language dependant, which in turn cause loads of issues on windows images in languages other than a few that happened to match.

      There was some discussion about which direction to go forward in and ideally we’d do things in a more clever way, but for the time being we landed on using partition flags (such as boot, hidden, reserved) to determine whether or not they should be attempted to resized.

      I’m not well versed in the deploy time resize logic however. I’m guessing there were scenarios were exceeding the starting point of the following resizable partition was desirable. (eg a Windows partition + a data partition. You wouldn’t want your windows partition to be tiny after deploy per se)

      It being inconsistent (or at least seemingly so) seems of a greater concern. Is this occurring on different hardware? (particularily disk size)

      posted in Bug Reports
      Q
      Quazz
    • RE: Error on image upload

      @Zourous Did anything change with the newer init? Different line number or slightly different error?

      posted in FOG Problems
      Q
      Quazz
    • 1
    • 2
    • 14
    • 15
    • 16
    • 17
    • 18
    • 98
    • 99
    • 16 / 99