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

Imaging issue with writing BCD after FOG update (1.2.0)

Scheduled Pinned Locked Moved
FOG Problems
2
5
1.1k
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.
  • W
    WelbyAdmin
    last edited by May 25, 2016, 7:27 PM

    Error is:

    Backup and replacing BCD mv: cannot stat '/bcdstore/Boot/BCD': No such file or directory
    

    I have completely ruled out the hard drive in the machine I’m trying to image, it’s fine. I did this by booting to a Hiren’s boot CD and cleaning and re-initializing the HDD.

    I read about a similar error here: https://forums.fogproject.org/topic/3409/imaging-issues-after-updating-from-0-32-to-1-1-2

    …but I’m on 1.2.0, which is the latest version of FOG. Any ideas on how to fix this?? Thanks.

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by May 25, 2016, 9:22 PM

      We need to know what OS and version your FOG server is running on.

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 1
      • W
        WelbyAdmin
        last edited by May 25, 2016, 9:29 PM

        @Wayne-Workman Certainly, thank you Wayne.
        OS hosting FOG is Ubuntu 14.04 (w GUI and Mate).
        I just now updated FOG to SVN 7853.

        I think the problem is actually with the image I’m trying to deploy, but I did nothing to it.

        W 1 Reply Last reply May 25, 2016, 9:34 PM Reply Quote 0
        • W
          Wayne Workman @WelbyAdmin
          last edited by May 25, 2016, 9:34 PM

          @WelbyAdmin I agree, I think it’s the image. it worked fine in 0.32? If so, you could build a 0.32 server quickly and just copy over the image, make the definition for it appropriately, and then restore to a computer - then upload that to the new server.

          That might work.

          Another option is to rebuild the image.

          Pay attention to this thread, others may chime in with better advice.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          W 1 Reply Last reply May 25, 2016, 10:01 PM Reply Quote 1
          • W
            WelbyAdmin @Wayne Workman
            last edited by May 25, 2016, 10:01 PM

            @Wayne-Workman Thank you, I just finished imaging a machine with an older image, so it 100% was the image. No worries though, I’ll just build a new one. Thank you!

            1 Reply Last reply Reply Quote 2
            • 1 / 1
            1 / 1
            • First post
              2/5
              Last post

            154

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project