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

could not map attribute 0x80 in inode FOG 1.5.9

Scheduled Pinned Locked Moved
FOG Problems
3
6
737
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.
  • I
    IronAngel777
    last edited by Jul 21, 2021, 4:31 PM

    I have finally been able to install FOG images with UEFI boot, however, now I receive an could not map attribute 0x80 in inode FOG error when trying to capture an image off the same computer.

    PXL_20210721_155405534.jpg

    I have run chkdsk /f/r/x, I have turned off quick boot. Yet I get this error.

    I would revert back to legacy, but now a new Lenovo laptop E14, has no legacy boot option. This is occurring only on Lenovo laptops as that’s what I’m currently updating and imaging.
    I’m trying to capture Windows 10 images

    Thanks

    I 1 Reply Last reply Jul 21, 2021, 7:11 PM Reply Quote 0
    • I
      IronAngel777 @IronAngel777
      last edited by Jul 21, 2021, 7:11 PM

      Well, I did the exact same update and capture to the next new Lenovo, out of the box, and it captured fine. Perhaps, CHkDSK does not completely repair NVME drives.

      Anyway…

      1 Reply Last reply Reply Quote 0
      • N
        Noseman
        last edited by Jun 10, 2023, 9:19 AM

        I have exactly the same problem in FOG 1.5.0.

        10 Lenovo machines with 256GB Crucial MX500 SSDs, all same setup, all same settings.
        8 capture fine, 2 get this error.

        • no dirty bit
        • chkdsk shows no errors
        • no smart errors or other errors shown in crucial storage executive

        buggy SSD? The machines are working fine.

        Any suggestions how to fix this error?

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Jun 11, 2023, 6:13 AM

          @Noseman said in could not map attribute 0x80 in inode FOG 1.5.9:

          I have exactly the same problem in FOG 1.5.0.

          I hope you mean 1.5.10!?

          Now on your issue, made sure fast boot is disabled??

          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

          N 1 Reply Last reply Jun 11, 2023, 9:38 AM Reply Quote 0
          • N
            Noseman @Sebastian Roth
            last edited by Jun 11, 2023, 9:38 AM

            @Sebastian-Roth said in could not map attribute 0x80 in inode FOG 1.5.9:

            @Noseman said in could not map attribute 0x80 in inode FOG 1.5.9:

            I have exactly the same problem in FOG 1.5.0.

            I hope you mean 1.5.10!?

            Now on your issue, made sure fast boot is disabled??

            Hi @Sebastian-Roth ,

            thank you for answering.

            You mentioned right, it is 1.5.10. 😎

            I said, no dirty bit set, so this means also no fast boot to me,

            After my post I was fiddling around:

            • Testing RAM, not with included memtest over pxe, because it does not work, I tried the memtest86 (6.x) included in the proxmox iso, uefi booted via ventoy. - RAM OKAY
            • Taking an image with Trueimage, no errors - works
            • Changing to a new SSD, and deploying the Trueimage image onto. - works
            • After that capturing the machine via fog. - works without errors
            • Deploying the captured image in the old (not captureable) SSD - works
            • Capturing this again, from the (not captureable) SSD works now flawlessly.
            • Tested this on both machines several times, works absolutely fine.
            • On the other machine I tried deploying the image from trueimage directly onto the “not captureable” ssd, which saves some time and works also with capturing from fog afterwards.

            I would call this a workaround, and it did the trick, but WTF was the problem?

            Happy ☀ sunday!

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Jun 18, 2023, 6:47 AM

              @Noseman The tools used within FOS (FOG OS doing all the hard work when capturing and deploying) are no official Microsoft certified software products but from open source community. They work in 99% of cases but I can imagine there can be special states of the filesystem or certain edge cases those tools simply cannot handle (yet).

              Great you found a workaround!

              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

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

              147

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project