Expand Fog Storage Space
-
The answer is it depends. The simplest way to know the direction is to post the output of this command:
lsblk. That will tell us if you have lvm setup or just physical partitions. -
-
@vanopy OK so you have the easiest path. Your system is setup to use LVM (logical volume manager). So in short you just need to add your new disk to the volume group and extend your file system to use all of the disks in the volume group.
I searched and I don’t have a tutorial on expanding a LVM disk, mainly because its not a FOG issue but a Linux distro issue. There are many helpful guides out there that covers the process in detail.
I did a quick google-fu search and found this document. If you want the full details then read this: https://www.tecmint.com/add-new-disks-using-lvm-to-linux/
IMO this next document is a bit easier to follow and straight step by step. If you have a physical FOG server then skip over the bits about adding a new virtual disk. The workflow is the same between physical and virtual. https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/
-
@george1421 Great, I’ll have a look, thanks for your help!
-
@george1421 So I’ve followed all the steps in this article, and it seems that I’ve expanded the file system to use all of the disks in the volume group, but unfortunately I’m unable to capture the new image I’ve made. In the fog dashboard I can now see that I have plenty of storage space.
However, I keep getting the following error message while I’m capturing the image around 53%:
Any idea what might be causing this?
Thanks.
-
@vanopy what is the output of
lsblkas done on your fog server again? How does it compare to the first one? How aboutdf -h? -
-
@vanopy OK by your second image I see that you are 15% used space on your /images disk. So server disk space isn’t the problem here.
Your fog error message almost gives me the idea that you have a bad hard drive on the target computer. Because its have a page read issue.
So 2 things here.
- Try a similar upload on a second computer of a similar model as this one that failed.
- Set up a capture again to this failed computer, but this time before you schedule the task tick the check box for debug. Then pxe boot the target computer. After a few screens of data you will need to press enter to clear, you will be dropped to a linux command prompt. At this point you are using the FOS linux console. The next steps will be to single step through the deployment process. You will need to hit enter to go to each step. In the error screen you posted, that is the result of partclone failing, but not the reason why (the buffer i/o error is a clue). When partclone is imaging and runs into an error it will printout the error on the screen. We need to capture that error. If we can’t capture the error we can at least look in the log files on the target computer. So for now key in
fogand press enter to start the image deployment. The deployment program will stop at each step waiting for your input. These pauses will give you a chance to review any error messages.
-
@george1421 So I’m in debug mode right now, and this is the error I’m seeing:
-
@vanopy I’m still thinking its a disk error. You may need to boot it back into Windows and run some disk repair utility to see if 1. you can detect the error in the OS and 2. repair the error. The fog suggestion that disk space on the server is the issue is incorrect.
