• 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 disk contains an unclean file system (0, 0)

      @willian Fast Strange, there should be more options in the top left corner for power mangement, something like “Actions to take when closing lid”, thats where fastboot option is located.

      posted in FOG Problems
      Q
      Quazz
    • RE: windows 10 updates

      Sounds like you’re looking for something like http://download.wsusoffline.net/

      Of course we can’t really provide support for 3rd party software.

      posted in Windows Problems
      Q
      Quazz
    • RE: Error when trying to capture an image?

      @george1421 Worth noting that on 1.5.6 the linux user account was changed from fog to fogproject

      posted in FOG Problems
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Deployed successfully with your init on my end, W10 Pro UEFI.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Of course, just trying to figure out if there’s any differences in the inits themselves that might cause a disrepancy.

      I’ll let you know if it deploys correctly on my test system tomorrow.

      Do you have a funky partition layout perhaps? I’m assuming fairly vanilla, but you never know.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Did you remove the partclone patch file?

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Deploying now, will report tomorrow.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      Finally got around to testing a bit.

      I compiled partclone 0.3.12, removed --ignore-crc and deployed a 0.2.89 UEFI windows 10 image.

      Verified I was running the correct partclone version (since it mentions it while writing the data) and monitored for any trouble

      Everything completed successfully and the pc booted normally.

      edit: I should additionally mention I haven’t touched ramdisk size or anything.

      posted in General
      Q
      Quazz
    • RE: Error trying to restore GPT partition deploying an Image to Smaller Disk

      It looks like it failed to correctly record which partitions should be fixed.

      FOG 1.5.6 should be better about that.

      To fix it for this image specifically change d1.fixed_size_partitions from :2 to :1:2:3

      That being said

      I don’t believe that is your main issue here since the partition sizes don’t imply they are resizable anyway, but I’m not 100% sure if the system will or will not try to resize them under these conditions.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG unable to capture/deploy resizeable images correctly.

      @dambron The script grabs the init from this url https://fogproject.org/inits/init.xz

      Put it in /var/www/fog/service/ipxe

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG unable to capture/deploy resizeable images correctly.

      There was a bug in the inits that would cause issues with recording the wrong info about “fixed size partitions”. I believe 1.5.6 (just released!) contains the fix though. You’ll have to recapture the images though.

      It was fixed in this PR, no? (the PR isn’t labelled that well, but basically the code hadn’t been updated in that file, but now we just read the info instead of running the same tests twice) https://github.com/FOGProject/fos/pull/24

      The other user hasn’t reported back yet, but give 1.5.6 a go and let us know!

      posted in FOG Problems
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @Junkhacker The following commit changed UUID stuff https://github.com/FOGProject/fos/commit/f49b0f7d5b0c90866a6dcdbbd5d59e529857242e

      On MBR, the label-id is in the form of what appears to be an error code (0xrandomnumbersandletters) hence the output that you saw.

      I don’t know for sure why it would fail, but something in that direction possibly.

      edit: Ok, so, in d1.partitions it’s saved as 0xlabelid whereis sgdisk expects it as labelid

      The original method used blkid -po udev which does not put 0x in front.

      Shouldn’t be too hard to fix

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @Sebastian-Roth I believe I do have dpkg installed, I think I did that to try and make it work with dpkg instead of having to select rpm or dpkg depending on distro flavor, but dpkg has no knowledge of rpm installed packages and is therefore not usable for that purpose.

      Definitely needs to be updated, yes.

      I’ll double check the config files for building, but I synced the FOG branch before I started so I’m unsure why that would fail.

      Hmmm, looks like my sync may not have worked as I notice some differences, strange. Will have to reset and try again.

      edit: New build in progress, will test thursday (tomorrow is holiday)

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @Sebastian-Roth Btw I think that it’s not so much a “new image format”, but rather the checksum mechanism as per Junkhacker https://github.com/Thomas-Tsai/partclone/issues/121 (and https://forums.fogproject.org/topic/12750/file-format-and-compression-option-request/7) ,but I could be wrong of course.

      I’ll be testing 3.12 (in the testing branch)

      edit: Implemented Junkhacker’s suggestions. (well, only the checksum bits, since we want it to work before doing extra stuff)

      Currently building, will test tomorrow.

      edit 2: Seems like build errors complaining about legacy options, will see if I can fix that before I go home.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Best thing is probably to just pull the latest FOS from git and build that with an updated partclone.

      @Sebastian-Roth I’ll see if I have some time this week.

      posted in General
      Q
      Quazz
    • RE: "Could not open inode XXXXXX through the library..." Windows 10 Sysprep Capture

      @kafluke You may have to defragment the drive and/or run chkdsk on it if you’ve deleted a significant amount of data.

      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

      @HG12 Hey, it’s been a while, is this issue resolved? There are updated inits available (I think) that might have resolved this issue.

      posted in Bug Reports
      Q
      Quazz
    • RE: [CentOS 7 + FOG1.5.5] Password MariaDB FOG + Password WEB

      @Guillaume-IT You need to edit two files

      /opt/fog/.fogsettings (edit snmysqlpass)
      

      and

      /var/www/fog/lib/fog/config.class.php (edit define (‘DATABASE_PASSWORD’, “MdpROOTsql”);)
      
      posted in FOG Problems
      Q
      Quazz
    • RE: [CentOS 7 + FOG1.5.5] Password MariaDB FOG + Password WEB

      You can change the password on the Web UI for any account, including fog from the users menu on the Web UI.

      As for the MySQL password, it says what to do

      Configuring the new FOG mysql root password
      Edit the file /opt/fog/.fogsettings and enter the password on line 21:
      nano /opt/fog/.fogsettings
      snmysqlpass = ‘MdpROOTsql’
      
      Edit the file /var/www/fog/lib/fog/config.class.php and enter the password on line 50:
      nano /var/www/fog/lib/fog/config.class.php
      define (‘DATABASE_PASSWORD’, “MdpROOTsql”);
      
      posted in FOG Problems
      Q
      Quazz
    • RE: Single Partition Imaging

      @sonic136 I’m assuming what you want is to image the windows partition (plus partitions needed to boot the system) without the ‘data’ partition.

      For Image Type just select Single Disk - Resizable.

      For Partition you’ll have to select the partitions you want (check disk management). While it is certainly possible to capture a single partition (such as C:), keep in mind that this won’t create a bootable image.

      posted in General Problems
      Q
      Quazz
    • 1 / 1