• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Noseman
    N
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 2
    • Best 0
    • Controversial 0
    • Groups 0

    Noseman

    @Noseman

    0
    Reputation
    1
    Profile views
    2
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Noseman Unfollow Follow

    Latest posts made by Noseman

    • RE: could not map attribute 0x80 in inode FOG 1.5.9

      @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!

      posted in FOG Problems
      N
      Noseman
    • RE: could not map attribute 0x80 in inode FOG 1.5.9

      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?

      posted in FOG Problems
      N
      Noseman