Can't Upload Image - Hangs or 'Attempting to Check-In'
-
Hi all,
I currently have a problem where I can’t upload an image from a Hyper-V VM. When trying to do so, it hangs on ‘Resizing Filesystem’ for over an hour, and then comes back saying it could not mount /dev/sda2. I’ve run chkdsk /f multiple times and restarted multiple times, but still run into this error. It was working before, so I’m wondering if the VHD has gone wrong? Would cloning everything to a new VHD make it work?
I just updated FOG to cover that base (currently running version 1.3.0-RC-8 (SVN revision: 5949), and now I’m getting ‘attempting to check-in… failed’. I’ve attached screenshots of all the errors.
Any help with this would be appreciated as this is happening with our most used image and the upload attempt has actually wiped the image from the FOG server (so this is the only copy…).
-
Is it a fixed size VHD?
-
@Quazz Yes - with 40GB free on it.
-
@RobTitian16 Have you ever been able to upload from this VM?
If not, it’s likely a configuration issue or Hyper-V issue.
-
@Quazz Yes, quite a few times. This issue only just started happening within the past few days.
I’ll try creating a new VM with a copy of the VHD it’s using to see if I can upload it then. -
This looks like an issue with the VM’s virtual HDD. I would double check all of those settings.
-
@RobTitian16 Why would it be able to check in and fail the next time when attempting to check in?? Please check your apache error logs on this (see my signature on where to find the logs).
About NTFS resize speed in Hyper-V you definitely want to read this posts. AFAIK this is still not solved as we are still waiting for the kernel devs to answer/fix this.
Your resizing taking an hour and failing might be another issue though. Somehow to me this sounds like the VHD is screwed. Maybe create a new one - same partition table and formatting but only put in a couple of files for testing - and see if you still get the same errors. I doubt it.
-
@Sebastian-Roth I created a new virtual machine with a copy of the VHD that was faulty and now it’s back to ‘resizing file system’ for over an hour and a half.
I’m currently running a chkdsk /b on the original version of the VHD in the hopes that will fix it. I’ll try the upload again afterwards, otherwise it looks like I’ll have to rebuild the image. -
@RobTitian16 What’s the kernel version you’re running?
-
@Tom-Elliott Ubuntu 14.04
-
@Tom-Elliott After trying to upload this on a new VHD, I get the following error:
-
@RobTitian16 Did you run a chkdsk before trying this? If not, try this.
-
@Quazz Unfortunately I can’t run chkdsk /f after the upload attempt - it seems to really screw up the VHD to the extent that it is no longer bootable. I’m going to try from a real hard drive and see if that makes any difference.
The last message I received with a brand new VM and VHD was:
-
@RobTitian16 I can’t find the thread where it’s said, but,
Someone recently discovered that a certain type of virtual disk cannot be used for capturing images from - because of how it dynamically expands/shrinks the disk based on used space - it totally messes up partclone and fog capturing.
Maybe one of the @Developers @Moderators @Testers remember this thread?
-
@Wayne-Workman Hmm, that’s interesting… although I’m certain my hard disks aren’t set to dyanmically expand/shrink.
I worked around this by using a physical hard drive. -
@Wayne-Workman Not sure, dynmically sized hard drives can cause all kinds of issues though, one of them being that you only get the space used when your image is deployed and you’re unable to expand it in Windows.
