• 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
10.9k
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.
  • G
    george1421 Moderator @roger-jsf
    last edited by george1421 Jun 20, 2017, 4:24 AM Jun 20, 2017, 10:23 AM

    @roger-jsf OK, I just wanted to know if this was a new problem (as compared to a previous version of fog).

    So if you use clonezilla to copy the same master reference image it works correctly? Or did you use a new reference image for FOG too?

    I’m trying to rule out the reference image being at fault here. There are some drivers that must be embedded into reference image before capture.

    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, 11:16 AM Reply Quote 1
    • R
      roger-jsf @Sebastian Roth
      last edited by Jun 20, 2017, 10:49 AM

      @Sebastian-Roth

      Machine used as fog Server: Ubuntu DESKTOP 14.04 LTS.

      Link to d1.mbr:

      http://s000.tinyupload.com/?file_id=05105010012586326507

      Ls-la of image:

      0_1497955495096_LS AL image.png

      1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator
        last edited by Quazz Jun 20, 2017, 5:07 AM Jun 20, 2017, 11:06 AM

        Can I ask how you figured out the disk letters were swapped? Please note that in WinPE enviroments (bootable USB, recovery mode, etc) the drive letters aren’t necessarily representative of what it would be if the system itself booted!

        Just want to see if we can exclude a possible issue or not.

        R 1 Reply Last reply Jun 20, 2017, 11:11 AM Reply Quote 1
        • R
          roger-jsf @Quazz
          last edited by Jun 20, 2017, 11:11 AM

          @Quazz You can exclude this option! I noticed the drive letter issue in WinPE environments and didn’t remember to delete the comment, my bad!

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

            @george1421

            I don’t understand exactly what are you asking me, so please forgive me. 😛

            Are you asking me to replicate the image captured by FOG using clonezilla or if it works capturing and cloning the same machine with clonezilla ?

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

              @roger-jsf Ok here is what I’m thinking.

              I’m trying to apply logic to this because the issue can be anywhere. At this point we don’t know if the image is at fault or FOG why this target computer doesn’t boot.

              If you told me, this is the same reference image that we clone using clonezilla then I would know the image itself is good, then we would focus on FOG as being the bad guy here and try to understand why.

              At this point we have to question everything. Was the master image created incorrectly for this hardware? Is the OS missing boot time drivers (like disk controller drivers)? Was this reference image sysprep’d? Was the image taken from another working 3020 and its failing to deploy to another 3020? How are you injecting the drivers for the 3020. Is FOG messing up expanding the disk after being compressed? Is there a hardware issue with the disk in the target computer?

              As you can see right now I have more questions than answers?

              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
              • S
                Sebastian Roth Moderator
                last edited by Sebastian Roth Jun 20, 2017, 6:33 AM Jun 20, 2017, 12:32 PM

                @george1421 @roger-jsf Hopefully I can give some more answers… I think I was able to replicate the problem and I guess it’s within our magic-calculate-partition-resize-awk-script. I might figure this out in the next hours. Please give me a bit more time.

                As well I am still trying to figure out why this issue is not more common but only seems to come up with this particular partition layout.

                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 1
                • S
                  Sebastian Roth Moderator
                  last edited by Jun 20, 2017, 1:54 PM

                  @roger-jsf Found and fixed the issue together with @Tom-Elliott! For testing you need to get the very latest initrd files. On your FOG server run those commands:

                  sudo -i
                  cd /var/www/fog/service/ipxe/
                  mv init.xz init.xz.1.4.2
                  mv init_32.xz init_32.xz.1.4.2
                  wget https://fogproject.org/inits/init.xz
                  wget https://fogproject.org/inits/init_32.xz
                  chown fog:www-data init*
                  

                  Then try deploying your image again.

                  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

                  G R 2 Replies Last reply Jun 20, 2017, 2:00 PM Reply Quote 1
                  • G
                    george1421 Moderator @Sebastian Roth
                    last edited by george1421 Jun 20, 2017, 8:01 AM Jun 20, 2017, 2:00 PM

                    @Sebastian-Roth said in W7 Image: Disk read Error after imaging:

                    Found and fixed the issue

                    If this addresses the issue, it may solve 3-4 other threads I’ve been tracking regarding disk resize/deployment failures. Good find!

                    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 1
                    • R
                      roger-jsf @Sebastian Roth
                      last edited by Jun 21, 2017, 9:12 AM

                      @Sebastian-Roth This fixed the issue! Thanks and keep up the good work!

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

                      266

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project