Added new drive for more /images space, now captures fail with "failed to read back partitions"

  • Server
    • FOG Version: 1.3.5
    • OS: Ubuntu 14.04
    • Service Version:
    • OS:

    Args passed on the client error /dev/sda which was the original mount point for /images but I added a new drive to make some more room, /dev/sdb and copied the images there. I think I just need to tell fog the location changed, but don’t know how. Can anyone be so kind as to enlighten me, please?

  • @lesliebright We all do dumb stuff, but only the men among us admit it.

  • @Wayne-Workman Well, now I’m embarrassed. The installation completes perfectly well if you actually give the installer the correct information. Thank you.

  • @lesliebright From one of these clients that is having this issue, open up a web browser and try to go here: http://x.x.x.x/fog/management/other/ssl/srvpublic.crt but replace the x.x.x.x with your fog server’s IP address. Then next try with the hostname of your fog server. If those two things work, are you putting in the correct information into the FOG Client installer or are you just clicking through it?

  • @george1421 Re-ran installer from dev-branch and behold, RC11 is out. Fixed some issues, but not all. I can download the client installers through the links, but they still fail at the ca cert install :/

  • Moderator

    @lesliebright Lets have you rerun the FOG 1.3.5RC10 installer again (if you are not on RC10, you should upgrade first). FWIW: 1.3.5(stable) hasn’t been released yet.

    But the installer may fix what is sideways in your current FOG setup.

  • Thank you for your response. I decided to increase the original drive’s size and extend the partition. I did away with the second drive altogether. I now have enough storage space. The only issue I know that I have now is that the client downloads don’t work. The downloads page is there, but clicking on the msi or the smart installer never downloads anything. I found the files on the fog server and manually copied them over to try to run the installer, but both failed, complaining that they were unable to install the CA certificate.

  • Moderator

    This is on the FOG server right?

    If this is the case you have a broken concept of how linux works.

    physical drives are attached to a root path at different locations. Typically /dev/sda1 (first partition on the first drive) is connected to the root path (this is not 100% accurate, but for this discussion it is). I’m going to guess that you used the default layout for your ubuntu installation where the complete root path is connected to /dev/sda1. The issue with this is as you collect (upload) fog images your root partition runs out of space. This issue can be fixed one of two ways.

    1. The quickest is of LVM is used to manage your disks is to just add an additional physical disk to the FOG server and then add it to your LVM volume group. LVM will manage and use this new disk (i.e. /dev/sdb). Nothing else has to be done.

    2. The second option is to add the additional disk to your FOG server and then mount (attach) that new disk to a temporary mount point (like /mnt), move the contents of /images/* to /mnt, then umount /mnt and remount /dev/sdb1 to /images directory. (coming from the windows realm its a bit hard to understand but that is the way it is done. Actually Windows 2008 and newer can do the same thing, but no one uses it). I did write a tutorial on how to go about this method:

    Now back to your OP. I’m going to bet what is going on is that you maybe moved the location of /images on the FOG server files. The issue is that the /images directory is shared via NFS, and moving that data path could cause the share to fail. The best approach here is to attach /dev/sdb1 to the current /images directory/mount point, ensure the fstab is updated and reboot the FOG server to make sure everything restarts correctly. When the FOG server comes back up, log into the linux console and key in showmount -e that will show you the nfs shares that are shared on your fog server.

Log in to reply