If I get a chance I’ll try to add the AR8161 driver to the kernel and rebuild it. I won’t get a chance to look at it again for an hour or so though.
astrouga
If I get a chance I’ll try to add the AR8161 driver to the kernel and rebuild it. I won’t get a chance to look at it again for an hour or so though.
astrouga
Ah, well that one doesn’t appear to be supported in 3.4. It looks like 3.5 has some Atheros support. Try this:
[URL=‘http://www.filedropper.com/bzimage35072512’][U][COLOR=#0066cc]http://www.filedropper.com/bzimage35072512[/COLOR][/U][/URL]
astrouga
Did you try any of the other options mentioned in the first link? Also, I accidentally put the kernel option in as “reboot=BIOS”, which did not work. I’ve since learned that many (if not all) kernel options are case sensitive. So make sure you enter:
[CODE]reboot=bios[/CODE]
astrouga
I had some Dell Optiplex 960s that were doing this. This setting solve the problem. Thanks.
astrouga
quote=“Gorosoki, post: 4981, member: 1248”]I deployed an image with the bzimage34 kernel and it finished after about 4 hours. The Windows 7 image didn’t deploy right. Window repair tried to fix it, but it couldn’t. Any suggestions?[/quote]
How do you have the rest of your image definition set up? Try setting the image type to “Multiple partiton - single disk(not resizable)”, even if it is only 1 partition.
Is this a clean install of Win 7 or an OEM install? I’d take one of the spares and install windows 7 from scratch (removing the 100 MB partition). No apps or patches. Just try to upload and deploy. If it works, you can be sure that FOG is working with your hardware and you can focus on your partition/filesystem.
Sounds like this is unlikely to help, but here is a 3.4.5 kernel. I used it the other day and it works fine on my systems:
[SIZE=2][COLOR=#0060e0][url]http://www.filedropper.com/bzimage34_1[/url][/COLOR][/SIZE]
astrouga
[quote=“Whateverdude, post: 5021, member: 1614”]where can i get a copy off .33 beta[/quote]
You can download the latest trunk here:
[U][SIZE=3][COLOR=#0060e0][COLOR=#0060e0][url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/[/url][/COLOR][/COLOR][/SIZE][/U]
[SIZE=3]Don’t upgrade your production system obviously. There are quite a few features that do not work yet.[/SIZE]
[SIZE=3]Read through the “Bugs in FOG 0.33” thread and post successes and failures.[/SIZE]
[SIZE=3]astrouga[/SIZE]
Have you tried the ones I created recently? I don’t have a Dell all-in-one to test on.
3.4 kernel using fog core:
[U][SIZE=3][COLOR=#0060e0][COLOR=#0060e0][url]http://www.filedropper.com/bzimage34[/url][/COLOR][/COLOR][/SIZE][/U]
[SIZE=3]3.4.5 kernel using fog core:[/SIZE]
[SIZE=3][url]http://www.filedropper.com/bzimage34_1[/url][/SIZE]
[SIZE=3]Click on the “Download This File” image link after the “URL:” and “Embed:” text boxes.[/SIZE]
[SIZE=3]Let us know if it worked for you.[/SIZE]
[SIZE=3]astrouga[/SIZE]
For the A11 systems, have you cleaned up as much free space as possible, defrag’d and run chkdsk on the disk before you imaged? It is a good first step. Also, open up Disk Management on the machine and and shrink the volume down a lot, then try to image it.
Report back.
astrouga
Try manually deleting the entry from the mysql db, if the host is there. From a terminal:
[CODE]mysql -u root -p
use fog;
select * from hosts; //this will list all the hosts
[/CODE]
if you know the hostname:
[CODE]select * from hosts where hostName=“blah”;[/CODE]
if you find it, delete it with:
[CODE]delete from hosts where hostName=“blah”;[/CODE]
You can list and delete with similar commands for the mac addresses you tried to register. Just change the “where” portion of the above statements like:
where hostMAC=“00:00:00:00:00:00” substituting in your mac values.
Let us know if that worked.
astrouga
OK, seems the fastest was to disable this when you start imaging from the “full host registration and inventory” boot menu option is to edit /var/www/fog/services/auto.register.php and comment out the line that starts with
[CODE]$other .= (" chkdsk=" . ($core->getGlobalSetting(“FOG_DISABLE_CHKDSK”) == “1” ? ‘0’ : ‘1’));[/CODE]
so, it becomes
[CODE]//$other .= (" chkdsk=" . ($core->getGlobalSetting(“FOG_DISABLE_CHKDSK”) == “1” ? ‘0’ : ‘1’));[/CODE]
that stops the chkdsk option being added for just this boot menu option.
astrouga
I just tested the “full host registration and inventory” and selected the option to image the system. Seems “chkdsk=1” is passed the append initrd line of the pxe configuration file for the host in this case. If I select the “quick image” option there is no “chkdsk” option in the pxe configuration file.
astrouga
Just curious, is this a new server? What os and version is it? Have you been able to image anything else or is it just the Debian machine?
astrouga
Doh! Well who knows then. I’ll see if that happens for me as well.
I would think this should be possible. Look at how the “quick image” menu option works. All it is doing is creating a file in /tftpboot/pxelinux.cfg with instructions. If you start a “quick image” job on a machine, just take a look at that folder on the server and you will see the file. It will be named with the mac address of the client.
It might be a simple as changing the “type” portion of the command from “down” to “up”. But, I’d open up the init file and take a look at the code. I would be nice to have both a “quick image pull” and a “quick image push” option. You’d want to password protect that image pull option though!
Keep us posted if you make progress on this. I’m kinda interested in this now, so perhaps I’ll take a look too.
astrouga
This should be fine. Just make sure that your image partition size is small enough to fit on both. In other words, if one drive is 40GB and the other is 80 GB, you won’t be able to dump the 80GB partition image to the 40GB drive. You’d need to resize the partition first.
A fool-proof method for a one image for all scenario is to include the drivers for all your systems in the image and tell sysprep where the inf files are.
astrouga
Have you using a custom kernel for that system?
astrouga
Cyrus:
Any luck? As Steve Ropiak mentioned, the partitions are good first place to look. How is the disk partitioned? How have you defined your image?
I haven’t had any issues imaging Lenovo laptops.
astrouga
I’m sure someone can help you troubleshoot. You’ll need to provide a lot more information first. Can you provide details about your server configuration, your system and what is happening when you attempt to image it?
astrouga
Sorry, I got swamped then forgot. I just created this one using the 3.4.5 kernel. I haven’t tested it, so I can’t guarantee it will work. I’ll try to take a look later to make sure I didn’t miss anything. Let me know if it works at all.
[url]http://www.filedropper.com/bzimage34_1[/url]
astrouga