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

W7 Image: Disk read Error after imaging

Scheduled Pinned Locked Moved Solved
FOG Problems
7
32
11.0k
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
    roger-jsf
    last edited by Jun 7, 2017, 10:45 AM

    Server
    • FOG Version: Running Version 1.4.0
    • OS: Ubuntu 14.04
    Client
    • Service Version: -
    • OS: Windows 7 Professional x64
    Description

    Hi everyone,

    I am currently having an issue deploying a certain type of image. It only happens whenever i try to use
    Single Disk - Resizable. I tried with non resizable methods and it works nicely but it’s not what I am looking for. I’ve also been looking for a solution for a couple of days but all post messages end without a conclusive result 😞 .

    I get the “Disk read error” message after imaging and the computer won’t boot ( DELL Optiplex 3020 ) and the OS i try to deploy is a Windows 7 Professional x64 - non OEM.

    These are the things I’ve already tried:

    • Repair Windows using installation CD / DVD ( to no avail ).
    • Use other imaging non resizable methods. ( It works but I would want to optimize deployment time ).

    If you need additional info feel free to ask.

    Thanks!

    G 1 Reply Last reply Jun 13, 2017, 4:25 PM Reply Quote 0
    • G
      george1421 Moderator
      last edited by Jun 7, 2017, 11:29 AM

      There was a bug in FOG 1.3.5 that under certain conditions the disk would not expand correctly. That issue was fixed in 1.4.0RC1 (pre release version of 1.4.0).

      If we need to get the developers involved, the first thing that will be said would be to update to the latest version and try again (1.4.2). While I don’t think this will address your issue, you might want to take that step and see.

      Just for clarity the target disk is the same size or larger than your reference image data size (if I asked that correctly)?

      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!

      R 1 Reply Last reply Jun 8, 2017, 7:55 AM Reply Quote 0
      • R
        roger-jsf @george1421
        last edited by Jun 8, 2017, 7:55 AM

        @george1421 I just updated to 1.4.2, created a new image, deployed it and still have the same problem.
        In reference to your question, the target disk is the same size as the reference disk ( in fact,both are the same make and model ).

        1 Reply Last reply Reply Quote 0
        • J
          Joseph Hales Testers
          last edited by Jun 8, 2017, 5:51 PM

          This may be off base but are the drive settings in BIOS the same on both machines I have had similar issues when ahci is enabled on one but not the other.

          RTFM

          G R 2 Replies Last reply Jun 8, 2017, 6:01 PM Reply Quote 0
          • S
            sudburr
            last edited by Jun 8, 2017, 6:00 PM

            Where exactly does this `Disk Read Error’ occur?

            What did you create your image on?

            If you created the image on a physical machine, did you zero the HDD first?

            Have you zeroed the destination machine’s HDD?

            Have you pushed the image onto any other hardware?

            [ Standing in between extinction in the cold and explosive radiating growth ]

            1 Reply Last reply Reply Quote 0
            • G
              george1421 Moderator @Joseph Hales
              last edited by Jun 8, 2017, 6:01 PM

              @Joseph-Hales said in W7 Image: Disk read Error after imaging:

              have had similar issues when ahci is enabled

              You may be on to something here. I remember that someone had an issue with a dell, it was in uefi mode and the drive configuration was “raid-on” In that setup it would have issues imaging. I can’t remember the exact details (I read way too many threads) but moving the firmware setting from raid-on to achi resolved that specific issue.

              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
              • R
                roger-jsf @Joseph Hales
                last edited by Jun 13, 2017, 10:03 AM

                @Joseph-Hales Both BIOS Configurations are identical and both drives are on AHCI mode.

                1 Reply Last reply Reply Quote 0
                • J
                  Joseph Hales Testers
                  last edited by Jun 13, 2017, 12:32 PM

                  Then I think you need to try what @sudburr suggested and wipe the drive fully before imaging.

                  RTFM

                  1 Reply Last reply Reply Quote 0
                  • G
                    gfontenot
                    last edited by Jun 13, 2017, 3:51 PM

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • G
                      gfontenot @roger-jsf
                      last edited by Jun 13, 2017, 4:25 PM

                      @roger-jsf

                      We were having a read error also, changed to the 2nd image type and it worked but created a large file. So, we then changed it back to 1st image type and selected Partclone GZip as the Image Manager, everything worked fine for us after doing this.

                      1 Reply Last reply Reply Quote 0
                      • R
                        roger-jsf
                        last edited by roger-jsf Jun 15, 2017, 2:56 AM Jun 15, 2017, 8:56 AM

                        Got a little more info:

                        Partitions are swapped. The 100 MB partition for system usage is being read as C:.

                        And the C:\ is now the D\ drive.

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sebastian Roth Moderator
                          last edited by Jun 15, 2017, 9:48 AM

                          @roger-jsf Can you please post a screenshot of the disk managment (partition layout) of your reference system. As well, please post the content of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions (all text files!) for this image on your FOG server (find those in /images/<IMAGENAME>/…).

                          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

                          R 1 Reply Last reply Jun 19, 2017, 9:22 AM Reply Quote 0
                          • R
                            roger-jsf @Sebastian Roth
                            last edited by Jun 19, 2017, 9:22 AM

                            @Sebastian-Roth

                            Here you go!

                            0_1497863976666_Partition Layout.png

                            CONTENT OF PARTITION FILES:

                            -------d1.partitions----------

                            label: dos
                            label-id: 0x55366f1b
                            device: /dev/sda
                            unit: sectors
                            
                            /dev/sda1 : start=          63, size=       80262, type=de
                            /dev/sda2 : start=       81920, size=      204800, type=7, bootable
                            /dev/sda3 : start=      286720, size=   976484352, type=7
                            

                            -------d1.minimum.partitions----------

                            label: dos
                            label-id: 0x55366f1b
                            device: /dev/sda
                            unit: sectors
                            
                            /dev/sda1 : start=          63, size=       80262, type=de
                            /dev/sda2 : start=       81920, size=      204800, type=7, bootable
                            /dev/sda3 : start=      286720, size=    57298684, type=7
                            

                            -------d1.fixed_size_partitions--------

                            :1:2


                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by Sebastian Roth Jun 19, 2017, 8:27 AM Jun 19, 2017, 2:25 PM

                              @roger-jsf Thanks for posting the picture and listings. To me this looks pretty good. Nothing out of the ordinary as far as I can see. We were fighting with type=de partitions about a year ago but FOG should handle those properly since then!

                              Can you please boot up this client that you deployed to with a debug deploy task again (normal deploy in FOG web GUI but check the debug checkbox in the view just before scheduling the task). Let the client boot and it will ask you to hit ENTER twice and drop you to a command shell. Run sfdisk -d /dev/sda there, take a picture and post it here.

                              By the way: Which setting for “Operating System” is set for this image in the FOG web GUI? Is it “Windows 7 - (5)”?

                              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
                              • R
                                roger-jsf
                                last edited by roger-jsf Jun 19, 2017, 9:10 AM Jun 19, 2017, 3:05 PM

                                @Sebastian-Roth Yes, “Windows 7 - (5)” is selected. Thanks!

                                I don’t know why but I can’t upload the image, so I have posted here: https://s2.postimg.org/djnk4qzvt/fog.jpg

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sebastian Roth Moderator
                                  last edited by Sebastian Roth Jun 19, 2017, 9:22 AM Jun 19, 2017, 3:21 PM

                                  @roger-jsf Ok, now I see why things go wrong. The start of the partitions are being moved. See the different numbers in the picture you posted.

                                  Re-reading your initial post I just saw that you are using FOG 1.4.0. Sorry but I didn’t notice this earlier. Could you please upgrade to the very latest version. Tom has worked on this stuff and we need to see if the issue is still persistent in the current code. So please upgrade and re-deploy that same image to one of your clients.

                                  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

                                  R 1 Reply Last reply Jun 20, 2017, 7:36 AM Reply Quote 0
                                  • R
                                    roger-jsf @Sebastian Roth
                                    last edited by Jun 20, 2017, 7:36 AM

                                    @Sebastian-Roth Following Goeorge’s advice I updated to 1.4.2, created a new image , redeployed the image and it didn’t work. 😞

                                    G 1 Reply Last reply Jun 20, 2017, 10:02 AM Reply Quote 0
                                    • G
                                      george1421 Moderator @roger-jsf
                                      last edited by Jun 20, 2017, 10:02 AM

                                      @roger-jsf Forgive me if I already asked this. What hard drive is in the 3020? Is it a nvme or sata disk?

                                      The reason I ask, for nvme you need to have 2 fixes for Win7 installed in the reference image or Win7 will not see the nvme disk.

                                      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!

                                      R 1 Reply Last reply Jun 20, 2017, 10:08 AM Reply Quote 0
                                      • R
                                        roger-jsf @george1421
                                        last edited by Jun 20, 2017, 10:08 AM

                                        @george1421 It’s a sata disk.

                                        G 1 Reply Last reply Jun 20, 2017, 10:10 AM Reply Quote 0
                                        • G
                                          george1421 Moderator @roger-jsf
                                          last edited by george1421 Jun 20, 2017, 4:10 AM Jun 20, 2017, 10:10 AM

                                          @roger-jsf Is this a new install of fog, meaning you haven’t used fog before for imaging? This is your first system or do you have history imaging with FOG?

                                          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!

                                          R 1 Reply Last reply Jun 20, 2017, 10:20 AM Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          1 / 2
                                          • First post
                                            10/32
                                            Last post

                                          159

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project