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

Cannot Mount /Dev/SDA3 - Sysprep & Imaging Issue

Scheduled Pinned Locked Moved Unsolved
FOG Problems
3
5
1.4k
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.
  • R
    RobTitian16
    last edited by Feb 6, 2017, 11:53 AM

    Server
    • FOG Version: 1.3.4 Revision 6064
    • OS: Ubuntu 14.04
    Client
    • Service Version:
    • OS: Windows 10 64-Bit
    Description

    Hi all,

    I’m currently trying to upload a sysprepped image to the FOG server, but everytime I do, I receive the following error:
    0_1486381765454_1.jpg

    The thing is, I’ve already run chkdsk /f before running sysprep - twice and rebooted the system twice each time. Then, I can’t load the OS at all - the system stays at a blank screen, as if it can’t read the hard drive correctly. But when simply running sysprep and not doing anything with FOG at all, the system will work (this is after re-imaging it with a non-sysprepped version of the image).

    Has anyone come across this before?
    Any help would be appreciated.

    1 Reply Last reply Reply Quote 0
    • J
      Jaymes Driver Developer
      last edited by Feb 6, 2017, 1:02 PM

      Is this by chance a new drive? Or did it have data on it prior to imaging?

      I’ve been away a minute, so please excuse this message if this is no longer an issue.

      In the past we have had issues pushing an image to a “blank” hard drive. We would resolve this issue by writing a partition to the volume then imaging.

      WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

      R 1 Reply Last reply Feb 6, 2017, 1:14 PM Reply Quote 0
      • R
        RobTitian16 @Jaymes Driver
        last edited by Feb 6, 2017, 1:14 PM

        @Jaymes-Driver No, I had data on it prior to imaging (it’s a laptop ordered from Dell so it had a preinstalled Windows 10 Pro 64-Bit OS).

        I’ll try it once more with sysprep, etc. and see how it goes.

        G J 2 Replies Last reply Feb 6, 2017, 1:27 PM Reply Quote 0
        • G
          george1421 Moderator @RobTitian16
          last edited by Feb 6, 2017, 1:27 PM

          @RobTitian16 What is the hardware model you have?

          Is there anything special about the disk (NVMe) or sata?

          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
          • J
            Jaymes Driver Developer @RobTitian16
            last edited by Feb 6, 2017, 1:57 PM

            @RobTitian16 Thank you for your reply.

            Did you build your Windows 10 image from scratch or are you using a modified version of the pre-installed os?

            You could try wiping the drive of all partitions, adding a blank one and imaging again. We have had trouble with partitions on the disk that were put there as a factory recovery point. (I know Dell, HP, etc are known for having a recovery partition).

            WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

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

            157

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project