Posts made by Rama

@danilopinotti
I’m getting this same error, can you please expound on this “WINS” fix? Thanks.

Appears to be working, will let you know once the image is uploaded if it still boots

Thanks for the replies. I am using “Version: 1.2.0”. I’ll give the fixparts a try.
The original image was windows 10, I wiped the disk and installed 7, then sysprep’d and tried to “upload” the image to fog at this point.
It’s highly likely that it is GPT, I forgot that could cause issues.
I’ll let you know how I get on.

Rama

I’m trying to upload a new windows 7 Ent. 64 to an HP Elitebook 850 G3 and I’m getting this error (Image type, single-resizeable):

An error has been detected!
No resizable partitions found.

I tried setting the image to non-resizeable single disk but it just gets stuck on “found drive /dev/sda” and never progresses.

From scouring other fog posts this could be related to TRIM function on the ssd?

I’m getting tired of the bleeding edge… every 3 years on the new leases I run up against some issue, its getting old.

Thanks,
Rama

@george1421
and it works! Thanks very much , 4.1.2 did the trick

@george1421
sorry to dig up the zombie thread! I thought some context might be helpful
Looking at the fog web UI it says version 1.2.0, I’m not sure if thats the “stable” release or not, I’ll see if I can find out. In any case I’m about to test the 4.1.2 and I’ll post here with results.

I am having the same error with a new model HP Elitebook 840 G3. Is it possible that the NIC is simply too new and the driver isn’t in the kernel yet?
I’ve tried the latest kernels (4.6.2 and 4.6.4) and they do not resolve the issue.
The network hardware details are:
Intel I219-V
HardwareID: PCI\Ven_8086&DEV_1570&subsys_8079103C

Some other sites are recommending a “3.16 backport kernel” as having the driver needed?

Thanks.
Rama

what is the usual cause of corruption in the images? over the last 6-8 months we have had a few go bad, I would just recreate them if it was a one off, but this seemed to be a bunch so I wanted to make sure it was corruption before reinstalling.
We are running identical hardware (both with the same redundancy/mirroring) at another school and have had zero issues.

hmm… the ‘images’ folder on the fog server is a local folder, its not a symlink or mapped to another network location if thats what you meant? the VM is running a .VDI with all the images on it, so as far as virtualbox/fog is concerned it is on a local disk?

so far there are 3 images that I know of that are corrupted/not deploying. all of them are recent ones… before the disk resize happened.

any system, same image. One very strange workaround I found for a laptop was to re-run host registration, then the image decided to deploy?!?! but didn’t work on any of the desktops

Hi, I have multiple images that used to be fine, but are now failing to deploy. I recently upgraded the bzImage kernel to get around some graphics issues with newer laptops, but apart from that nothing else has changed (yes I have tried deploying with old kernels, either specifying them in ‘host kernel’ slot in host management page, or renaming bzImage with older file version, neither work).

The exact error (was only able to capture with video shot on phone, as was too quick for the eye to read when it failed!):

performing cleanup stage 1… done
changing hostname… ntfs_mst_post_read_fixup: magic 0x71d40e27 size: 1024 usa_ofs: 16406 usa_count: 41949: Invalid argument
Record 0 has no FILE magic (0x71d40e27 )
Failed to load $MFT: Input/output error
Failed to mount /dev/sda2: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or its a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on windows then reboot.
…
…
unmount: can’t unmount /ntfs: Invalid argument
Done.

EDIT: sorry I should mention I’m running fog 0.32 on a linux(CentOS) VM in Virtualbox.

P.S. It seems like possible file corruption? which may have happened when we added some space on the images drive (a resizeable LVM partition).
Is there any way to mount the sys.img.000 partition and run an fdisk on it or similar? or is there any other way to check for file system errors?
thanks.