Adding a row in the images table is not hard. But, there is currently there is no way to determine if the image is empty or not. This will be addressed in coming versions.
In the future, please create your own thread for your questions.
Adding a row in the images table is not hard. But, there is currently there is no way to determine if the image is empty or not. This will be addressed in coming versions.
In the future, please create your own thread for your questions.
It looks like a configuration issue. i.e. service looking in the wrong directory, paths are wrong, going to the wrong server?
BryceZ has given good information. You will need to look harder.
[quote=“Bobfrid, post: 559, member: 224”]I think BryceZ is correct with suspecting a HDD problem.
From my experience “Buffer I/O Error’, ‘on device sda1’, ‘DRDY Error’, ‘ata1.00’, ‘logical block error’” is among a number of error messages that occur when a drive can’t be read at a certain point. Since you’re getting the same error using FOG and chkdsk, I would tend to think there’s hardware issue.[/quote]I would agree. Buffer I/O error is telling you that the hard drive has hardware problems.
Toss it and start a new image, do not start go, do not try to save this image.
[quote=“Sebastian M., post: 540, member: 229”]As written it worked good and without problems until we updated the Novell Client, but how could it be, that the simple process of updating a software increases the image size from ~40GB to ~120GB?[/quote]Because the data has been scattered around the disk and FOG needs to read all of the empty data between the real data. Defrag before uploading and this will be fixed (as long as all data can be moved to the front of the disk)
[quote=“Sebastian M., post: 540, member: 229”]I can’t understand why it is so complicated to clone a system with the same infrastructure (DC8100 from HP) and same settings.[/quote]
A good tradesman never blames his tools.
I will be closing this thread as you have created another post here: [url]http://fogproject.org/forum/threads/fog-converts-hdd-in-raw-format.132/[/url]
Your problem looks like a failing hard drive.
Images need to be built on the Hardware set you are creating them images for.
You cannot build images in a VM and then deploy it to a computer.
The no hard drive found error is because the kernel does not have support for that particular VM hard drive controller.
[quote=“The Dealman, post: 560, member: 53”]I don’t see how you can use Single Disk/Single Partition when there are 2 partitions?[/quote]
There is special code to deal with Winblows 7 partition structure. It will work with Single Disk, Single Partition (Re-sizable) as intended.
[quote=“totalimpact, post: 563, member: 217”]The developers know that Windows 7 will always have a 100mb boot partition[/quote]Not always. I remove it on my images personally.
In the future, we are looking at offering a Mutli-Partition (Re-sizable) option that will resize the last partition to the remainder of the disk.
I think you need to do some reading on how FOG works.
[url]http://fogproject.org/wiki/index.php?title=FOGUserGuide[/url]
Hostname should not include your domain. Hostname != FQDN
DHCP reservation is acceptable, i personally prefer static IP’s for most servers.
You should always run sysprep. This is more than likely your problem.
The speeds you mentioned are very slow, I can deploy a 60gb image in under 20minutes at around 4.0gb/min.
No. I haven’t thought about external authentication yet.
It’s something i want to support, but right now ive got other code to convert
There is a field called ‘createdBy’ which holds who the Task was created by. Though it’s not displayed in the 0.32 Web UI anywhere.
In 0.33 you will be able to create a Hook for this; it will be very simple and fast.
I cannot wait until this is up and working.
We need a documented kernel build process
Never uninstall something because it didnt work instantly, make it work.
That being sad, it is very easy and automatic to upgrade to 0.32.
[quote=“rixter, post: 474, member: 168”]Blackout, are you sure this isn’t an initrd issue? I was thinking I had some issue where I changed out my init file and it took care of something similar to this.[/quote]
No Its just my best guess
It could indeed be another issue.
Are you using ‘Single Partition (Re-sizable)’ as your Image Type?
Try this:
[LIST=1]
[]Remove all partitions
[]Make a fresh Windows install
[]Sysprep
[]Upload image as ‘Multi-Partition, Single Disk’
[*]Redeploy
[/LIST]
Does this image work as intended?
Here is another thread, i believe you two are having similar file system issues
[url]http://fogproject.org/forum/threads/deploy-problem-error-loading-operating-system.33/[/url]
It’s a kernel issue with your hardware then. You can always run the 0.29 kernel on 0.32.
Your image should contain most applications by default.
i.e. an Anti-virus suite is a requirement and will (should) not differ between your hosts
It should work. I would suggest upgrading to 0.32 before you put too much work into it.
If the second FOG server is online now, i would copy over the network.
First log into the FOG server with the images. Then copy using ‘scp’ or ‘rsync’.
scp is installed by default, rsync is not. But rsync is much better…
SCP:
[code]scp -r /images/* second_fog_servers_ip:/images/[/code]
Rsync:
[code]rsync -HavP /images/* second_fog_servers_ip:/images/[/code]
Or, to copy them to an external drive.
[code]mount /dev/sdb /mnt/ # change /dev/sdb to suit your external hard drive
cp -rav /images/* /mnt/[/code]