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

Image Store Corrupt Unable to locate MBR.

Scheduled Pinned Locked Moved Solved
FOG Problems
3
24
3.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.
  • J
    JimmyJ0516 @george1421
    last edited by Jun 18, 2020, 1:57 PM

    @george1421 thanks for the steps. So I did as you said and I indeed got an error https://imgur.com/A6QGyJk I took a picture of it.

    G 1 Reply Last reply Jun 18, 2020, 2:35 PM Reply Quote 0
    • G
      george1421 Moderator @JimmyJ0516
      last edited by Jun 18, 2020, 2:35 PM

      @JimmyJ0516 Ok you didn’t answer me, what version of FOG are you using?

      From that error if you hit Crtl-C it should drop you back to the linux command. From the linux command prompt on the target computer lets see the output from these commands.

      // sidebar: On the target computer if you give root a password using the passwd command. Give it something simple like hello and then get the IP address of the target computer with ip addr show that will give you enough info so you can connect to the target computer using a windows program like putty. Just connect to it using the IP address you just discovered. Login as root with the password of hello. This will allow you to copy and paste text much easier then having to seen a screen shot. You can continue with the screen shots if you want but the putty route is faster //

      lsblk
      fdisk -l /dev/sda

      Also we need to start identifying this hardware you are using? Have you imaged this type of computer before and this specific computer is the only one that is failing? Or is it a class of computers that are failing? Its possible that you have a bad hard drive in the source computer.

      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!

      J 2 Replies Last reply Jun 18, 2020, 2:38 PM Reply Quote 0
      • J
        JimmyJ0516 @george1421
        last edited by Jun 18, 2020, 2:38 PM

        @george1421 Sorry, I did not see that. I am running 1.5.8. I am going to run those commands now

        1 Reply Last reply Reply Quote 0
        • J
          JimmyJ0516 @george1421
          last edited by Jun 18, 2020, 2:49 PM

          @george1421 I posted the results below. Also, this is not the first time using the computer I have captured the image before and never had issues. I also took another computer model and capture the image of that and also had the same issue the d1.mbr file is missing. I have also post the results of the differences.

          [Thu Jun 18 root@fogclient ~]# lsblk
          NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
          sda      8:0    0 465.8G  0 disk 
          |-sda1   8:1    0   579M  0 part 
          `-sda2   8:2    0 465.2G  0 part 
          [Thu Jun 18 root@fogclient ~]# fdisk -l /dev/sda
          Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
          Disk model: ST500DM002-1SB10
          Units: sectors of 1 * 512 = 512 bytes
          Sector size (logical/physical): 512 bytes / 4096 bytes
          I/O size (minimum/optimal): 4096 bytes / 4096 bytes
          Disklabel type: dos
          Disk identifier: 0x0105e8f5
          
          Device     Boot   Start       End   Sectors   Size Id Type
          /dev/sda1  *       2048   1187839   1185792   579M  7 HPFS/NTFS/exFAT
          /dev/sda2       1187840 976771071 975583232 465.2G  7 HPFS/NTFS/exFAT
          [Thu Jun 18 root@fogclient ~]# 
          

          This is from the server itself

          /images/OPT7040-2019:
          total 18393216
          drwxrwxrwx  2 fogproject root        4096 Nov 18  2019 .
          drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
          -rwxrwxrwx  1 fogproject root     1048576 Jul  1  2019 d1.mbr
          -rwxrwxrwx  1 fogproject root   392718467 Jul  1  2019 d1p1.img
          -rwxrwxrwx  1 fogproject root 18440862240 Jul  1  2019 d1p2.img
          -rwxrwxrwx  1 fogproject root         190 Jul  1  2019 d1.partitions
          -rwxrwxrwx  1 fogproject root          15 Jul  1  2019 d1.size
          
          /images/OPT7040-2020:
          total 19968056
          drwxrwxrwx  2 root       root        4096 Jun 17 12:20 .
          drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
          -rwxrwxrwx  1 root       root   424917799 Jun 17 12:14 d1p1.img
          -rwxrwxrwx  1 root       root 20022329625 Jun 17 12:20 d1p2.img
          -rwxrwxrwx  1 root       root         190 Jun 17 12:13 d1.partitions
          -rwxrwxrwx  1 root       root          15 Jun 17 12:13 d1.size
          
          /images/OPT3040-2019:
          total 16517136
          drwxrwxrwx  2 fogproject root        4096 Jun 28  2019 .
          drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
          -rwxrwxrwx  1 fogproject root     1048576 Jun 28  2019 d1.mbr
          -rwxrwxrwx  1 fogproject root   382515569 Jun 28  2019 d1p1.img
          -rwxrwxrwx  1 fogproject root    13559174 Jun 28  2019 d1p2.img
          -rwxrwxrwx  1 fogproject root    11096900 Jun 28  2019 d1p3.img
          -rwxrwxrwx  1 fogproject root 16505295550 Jun 28  2019 d1p4.img
          -rwxrwxrwx  1 fogproject root         861 Jun 28  2019 d1.partitions
          -rwxrwxrwx  1 fogproject root          15 Jun 28  2019 d1.size
          
          /images/OPT-3040-IMG:
          total 11964976
          drwxrwxrwx  2 root       root        4096 Jun 18 09:38 .
          drwxrwxrwx 26 fogproject root        4096 Jun 18 09:38 ..
          -rwxrwxrwx  1 root       root   424782473 Jun 18 09:33 d1p1.img
          -rwxrwxrwx  1 root       root 11827327909 Jun 18 09:38 d1p2.img
          -rwxrwxrwx  1 root       root         190 Jun 18 09:32 d1.partitions
          -rwxrwxrwx  1 root       root          15 Jun 18 09:32 d1.size
          
          
          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Jun 18, 2020, 2:50 PM

            Possibly those regexp errors are fixed in the latest already… see fix here: https://github.com/FOGProject/fos/commit/80e240dee4c463c6ec62640edbe48d343098de6e (I would think this was after 1.5.8 released… not exactly sure though)

            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

            J 1 Reply Last reply Jun 18, 2020, 2:53 PM Reply Quote 0
            • J
              JimmyJ0516 @Sebastian Roth
              last edited by JimmyJ0516 Jun 18, 2020, 8:55 AM Jun 18, 2020, 2:53 PM

              @Sebastian-Roth Do you think and again I’m just throwing it out there. What if I downgrade to 1.5.7. All of the images I created were on 1.5.7. Now that I am capturing images for the first time on 1.5.8 I am having these issues. If I do downgrade do I just re-run the installer for 1.5.7? As well as you mentioned all of the images before the news created the owner is fogproject and the new ones have root as the owner.

              G 1 Reply Last reply Jun 18, 2020, 3:34 PM Reply Quote 0
              • G
                george1421 Moderator @JimmyJ0516
                last edited by Jun 18, 2020, 3:34 PM

                @JimmyJ0516 Instead of going backwards, lets take you to 1.5.9RC2. That RC version will probably become the next 1.5.9 GA release. There hasn’t been any bug reports against that RC release so far.

                If you used the git method to install FOG change to that directory (typ /root/fogproject) and issue the following commands.

                git checkout dev-branch
                git pull
                cd bin
                ./installfog.sh
                

                Now when 1.5.9 comes out you will want to switch back to the master branch to get 1.5.9.

                git checkout master
                git pull
                ... and so 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!

                J 1 Reply Last reply Jun 18, 2020, 3:45 PM Reply Quote 1
                • J
                  JimmyJ0516 @george1421
                  last edited by Jun 18, 2020, 3:45 PM

                  @george1421 I have been using the TAR/GZ archive way of downloading the updates and all of the updates are stored in /opt is that a problem?

                  G 1 Reply Last reply Jun 18, 2020, 3:46 PM Reply Quote 0
                  • G
                    george1421 Moderator @JimmyJ0516
                    last edited by Jun 18, 2020, 3:46 PM

                    @JimmyJ0516 With the tarball releases you can only install GA releases of FOG. The git method allows for a bit more flexibility.

                    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!

                    J 1 Reply Last reply Jun 18, 2020, 3:47 PM Reply Quote 0
                    • J
                      JimmyJ0516 @george1421
                      last edited by Jun 18, 2020, 3:47 PM

                      @george1421 Understood so I am moving into my /opt directory where all of the versions of Fog are stored and then I proceed to run the command you gave me correct?

                      G 1 Reply Last reply Jun 18, 2020, 3:50 PM Reply Quote 0
                      • G
                        george1421 Moderator @JimmyJ0516
                        last edited by Jun 18, 2020, 3:50 PM

                        @JimmyJ0516 To use the git method you can run this command from the /opt directory (my preference) or from /root

                        cd to that directory and then issue the following commands.

                        git clone https://github.com/FOGProject/fogproject.git
                        cd fogproject
                        

                        Then issue the commands from the previous post to switch to the dev branch and reinstall FOG.

                        Note if git is not installed then you will need to use your linux distro’s tools to install git.

                        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!

                        J 3 Replies Last reply Jun 18, 2020, 4:10 PM Reply Quote 0
                        • J
                          JimmyJ0516 @george1421
                          last edited by Jun 18, 2020, 4:10 PM

                          @george1421 I have successfully updated and I am now on 1.5.9-RC2.9. I will try and capture a image now and see where this takes me.

                          1 Reply Last reply Reply Quote 0
                          • J
                            JimmyJ0516 @george1421
                            last edited by JimmyJ0516 Jun 18, 2020, 10:34 AM Jun 18, 2020, 4:27 PM

                            @george1421 Actually this did fix the issue. It has now captured the d1.mbr file. I am now going to deploy the image to make sure it works 100%. Thank you

                            1 Reply Last reply Reply Quote 1
                            • J
                              JimmyJ0516 @george1421
                              last edited by Jun 18, 2020, 4:53 PM

                              @george1421 Alrighty Thank you so much for helping. Everything is now working fine with no issues at all. Last question lol how do I make this issue solved or does someone take care of that lol?

                              G 1 Reply Last reply Jun 18, 2020, 4:56 PM Reply Quote 0
                              • G
                                george1421 Moderator @JimmyJ0516
                                last edited by Jun 18, 2020, 4:56 PM

                                @JimmyJ0516 I took care of it for you. Basically under topic tools change the state as ask as question, then go back into topic tools and mark as solved.

                                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!

                                J 1 Reply Last reply Jun 18, 2020, 5:08 PM Reply Quote 0
                                • J
                                  JimmyJ0516 @george1421
                                  last edited by Jun 18, 2020, 5:08 PM

                                  @george1421 Thanks again

                                  1 Reply Last reply Reply Quote 0
                                  • 1
                                  • 2
                                  • 1 / 2
                                  1 / 2
                                  • First post
                                    18/24
                                    Last post

                                  338

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project