• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Resize failure?

Scheduled Pinned Locked Moved
General Problems
3
4
1.3k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    geardog
    last edited by geardog Jun 14, 2019, 8:46 AM Jun 14, 2019, 2:44 PM

    Running FOG 1.5.6

    Error(5): Could not map attribute 0x80 in inode 24291: Input/output error

    This is a follow up to
    https://forums.fogproject.org/topic/13334/mismatched-drive-sizes-in-win10-after-incomplete-capture-with-1-5-5

    After correcting the FS size, I ran Windows DISM clean and chkdsk /f which completed succesfully; they gave no errors. I then captured a raw image of the box which completed succesfully.

    Attempting to capture a resized image of this computer gave me this error

    f47dd505-ed4d-49bc-ada4-9c605c579ba0-image.png

    I ran chkdsk /f on the box, which completed clean before and after the imaging attempt.

    Any thoughts on cause or resolution to the error?

    Checking file system on 😄
    The type of the file system is NTFS.
    Volume label is HP.

    A disk check has been scheduled.
    Windows will now check the disk.

    Stage 1: Examining basic file system structure …
    576000 file records processed.
    File verification completed.
    12848 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage …
    26147 reparse records processed.
    657814 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    26147 reparse records processed.

    Stage 3: Examining security descriptors …
    Cleaning up 5 unused index entries from index $SII of file 0x9.
    Cleaning up 5 unused index entries from index $SDH of file 0x9.
    Cleaning up 5 unused security descriptors.
    Security descriptor verification completed.
    40908 data files processed.
    CHKDSK is verifying Usn Journal…
    36582096 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    223223172 KB total disk space.
    66502968 KB in 158976 files.
    128652 KB in 40909 indexes.
    0 KB in bad sectors.
    698964 KB in use by the system.
    65536 KB occupied by the log file.
    155892588 KB available on disk.

      4096 bytes in each allocation unit.
    

    55805793 total allocation units on disk.
    38973147 allocation units available on disk.

    Internal Info:
    00 ca 08 00 d8 0c 03 00 63 aa 05 00 00 00 00 00 …c…
    76 01 00 00 ad 64 00 00 00 00 00 00 00 00 00 00 v…d…

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth Jun 24, 2019, 12:39 AM Jun 24, 2019, 6:39 AM

      @geardog Do you usually shuwdown the Windows machine before capturing properly? See here: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      G 1 Reply Last reply Jun 26, 2019, 1:19 PM Reply Quote 0
      • G
        geardog @Sebastian Roth
        last edited by Jun 26, 2019, 1:19 PM

        @Sebastian-Roth

        I’ve typically just restarted, but Fast start was enabled too.

        A cold boot with fast-start disabled allowed a good capture.

        Thanks so much.

        G 1 Reply Last reply Jun 26, 2019, 5:11 PM Reply Quote 0
        • G
          george1421 Moderator @geardog
          last edited by Jun 26, 2019, 5:11 PM

          @geardog said in Resize failure?:

          A cold boot with fast-start disabled allowed a good capture.

          Just for another option:

          1. Let sysprep power off the computer after its run
          2. Run the following command from a command prompt shutdown -s -t 0

          Both of those commands will ensure that the system is properly powered off and ready for image capture.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          1 / 1
          • First post
            4/4
            Last post

          162

          Online

          12.1k

          Users

          17.3k

          Topics

          155.3k

          Posts
          Copyright © 2012-2024 FOG Project