Error capturing image after increasing drive size
We recently ran out of space on our Fog server. Since the server is a Hyper-V VM, I simply increased the drive space. After a very long process of getting the partition resized to use the new unallocated space (way harder than I feel it should have been), I had double the drive space and was ready to capture more images. When I first got the disk space expanded, Linux and Fog both did not see it, they were still reporting the old size. After running the command “lvextend -l +100%FREE”, Linux and Fog both started reporting with the new size. However, when uploading an image I am getting Exit Code 1, which asks if the server has plenty of disk space.
I am not very proficient in Linux, so I am at a loss as to what I could do or even look for.
Wayne Workman last edited by Wayne Workman
So if I ever encounter an error, should I go to the Wiki first and not the forums?
All of the standard troubleshooting we recommend for standard problems is usually documented in the wiki as best as we can.
This list has all of our troubleshooting articles:
But there are of course nuggets spread all over the wiki.
Good to know. So if I ever encounter an error, should I go to the Wiki first and not the forums? I found only one other post that referenced my same error, so I thought that it was a very small rare thing. Didn’t even think to check the wiki.
It uploaded properly this time, still with the drive being checked. Not sure how it was flagged as dirty that first time around.
Thanks again, and sorry for the pointless thread.
Sorry, the images were out of order. I thought that may be it, but I always sysprep so I know that it was shutdown correctly. I also set the disks to be checked, but have never received and error for doing it before. I’m going to sysprep and try to upload it once again.
Wayne Workman last edited by
@zpoling This wiki article is literally written for that exact error (picture in the wiki even exactly matches):
The error comes after the partclone error? It seems to be telling you exactly what’s wrong. The drive wasn’t shutdown properly.