Posts made by Trevor

I can’t remember, but it was way too long. I discovered the problem. I attempted to resize the partition via windows since the drives are huge and we don’t need the extra space. Windows complained that it could only reduce the partition 150GB because of unmovable files. So that made me google resizing partition unmovable files. The fix was as follows, to allow me to shrink the partition:

[FONT=Trebuchet MS][COLOR=#000000]For some reason Windows can’t figure out how to move some files around on disk. When attempting to shrink a volume, it will only allow you to shrink it to where the last immovable file is located. These are some things I found necessary to temporarily get rid of those immovable files so that an NTFS volume could be shrunk[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]1- Disable System Restore (Right click on Computer => Properties => System Protection => System Restore)
2- Disable Virtual Memory (Right click on Comptuer => Properties => Advanced System Settings => Performance (Settings) => Advanced Tab => Virtual Memory (Change) => No Paging File => Set.
3- Run Disk Cleanup to get rid of Thumbnails, Temporary Internet Files, and a bunch of other files that it makes no sense why they are immovable.
4- Restart the computer to have #1 and #2 take effect[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]Then I resized the partition to a manageable 80GB, to ensure I was past the original 155GB mark that was showing in the “data copied” field.[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]Then re-enabled system restore, and virtual memory.[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]This fixed my issue.[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]I would recommend this process for anyone experiencing imaging that slows down to a crawl. Mine would start at 3GIB/Min and then gradually get slower and slower. It was taking 3 hours to image only 26GB of data. My actual image file sizes were small, but my assumption is that the partition had files located deep into the partition, which FOG had to account for space. This is only a guess with my limited knowledge of file systems/partitions.[/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000] [/COLOR][/FONT]
[FONT=Trebuchet MS][COLOR=#000000]I am happy again w/ imaging a machines it 8 mins. YAH!! LOVE FOG![/COLOR][/FONT]

Does anyone have a guess on why the “file copied” size differs from the actual partitions in the screenshots I posted? To me it makes no sense. On a machine I installed Windows with the OEM clean install disc, the image “file copied” size matches the partition size, etc.

This machine I was forced to use the factory installed Windows because they don’t offer a clean install disc for this machine in x64.

I’ve read that FOG is suppose to account for the 100MB system partition. I’ve not had success in the past with Single Partition, but I just tried again anyway, and it stuck on “Resizing partition”. See attachment.

[url=“/_imported_xf_attachments/0/212_IMG_20121130_081421.jpg?:”]IMG_20121130_081421.jpg[/url]

Extra info. I used multi partition, single disk for Windows 7 images due to the extra 100mb system parttion. Worked well on the last one.

Screenies attached. Thx

[url=“/_imported_xf_attachments/0/204_IMG_20121128_092451.jpg?:”]IMG_20121128_092451.jpg[/url][url=“/_imported_xf_attachments/0/205_screen.png?:”]screen.png[/url][url=“/_imported_xf_attachments/0/208_IMG_20121128_104605.jpg?:”]IMG_20121128_104605.jpg[/url]

I have a Win7 image I’m trying to deploy. It’s take 1.5 hr to deploy to a single machine on a gigabit connection.

The only thing different I can see is I can’t figure why the file size on the server, doesn’t match the “Data copied:” part of the restore partition screen. I have attached screenshots from the image folder, and the actual deploying screen.

Size on server: d1p1.img = 9.1MB d1p2.img 16.9GB
Data copied on restore screen: 154.65 GiB (~166.05GB)

This doesn’t make sense to me at all. How can a 16GB file become 166GB of data to be copied? On past images, the data copied is the same as the size on server.

Any help or better understanding would be extremely appreciated. Thank you!

If anyone cares, Gigabit was a bad CAT6 cable.

I tested the kernel version that the other HP models similar used, and it now works perfectly! I’m a FOG lover!!

Fully working on [FONT=sans-serif][COLOR=#000000]2.6.35.3 PS as well. Quick![/COLOR][/FONT]

[quote=“chad-bisd, post: 4217, member: 18”]I have updated the [URL=‘http://www.fogproject.org/wiki/’]wiki[/URL] with your kernel information for this device.[/quote]
Actually, it didn’t work for uploading. The kernel that works is 2.6.28.7 KS and doesn’t appear to have Gigabit for the NIC. I’m stuck at 100Mb.

Had to re-create server due to hardware failure. I was incorrect for the working kernel version.

Working Kernel for HP Pro 3400 Series MT is [B]2.6.28.7 PS[/B], confirmed today.

Posting to help anyone who might be running into issues in the future.

I actually ended up getting it to work. I did the following:

1. Manually downloaded the 3.2.4 kernel again, since the link in Kernel Updater is broken.
2. Changed the BIOS setting for the HD back to AHCI.
3. Everything appears to be working with that kernel/BIOS setting.

Greetings FOG experts,
We have HP Pro 3400 MT desktops that I can’t get to work properly in FOG. I’ve tried numerous Kernels including 3.2.4, 3.3.3, 2.28, etc. When doing the test compatibility part, it Fails for Network. Hoping to find the person who reported it as “works well”.

When performing a quick register, it takes forever to load, and reports Unknown Bios Unsupported BIOS. Before that it reports UVESAFB errors.

Also, I set the HDD settings from AHCI to IDE in BIOS in case that was an issue.

Any help would be greatly appreciated!