Cant get fog to image disk
-
not a disk issue…tried wiping disk with dban first, as well as a different disk. still gets to the point where it should start the image process(checks disks, then cleans up, then Task completed and exits the pxe boot). Totally baffled, as these are identical to the rest. will try the bios update and try again…
-
not a bios issue… is there a way to delete these from the fog database and then rebuild the database?
-
[quote=“brett lutkehus, post: 3207, member: 1029”]not a bios issue… is there a way to delete these from the fog database and then rebuild the database?[/quote]
You can individually delete the computer hosts by going to the web server -> host management -> list all hosts, find the hostname you gave it and click on it. Then go to delete host. Then go through the whole process of registration again.
-
tried that too. no change. I am going to install from custom wim image and repackage for for and try to upload new reference image…
-
You might look in the /tftboot/pxelinux.cfg folder to see if there are any files there for those MAC addresses. Just delete the files.
-
no files there…
-
I’m seeing this too occasionally - seems to occur on (what should be) new hdd’s that have just been replaced by the pc manufacturer under extended warranty. I’ve not had a chance to get to the bottom of these yet, just placed them on one side for now, but in my case it’s definitely not BIOS related because I can drop another hdd caddy into the same machine and it will image fine.
-
I’ve had a look at this today - in my case it seems to be caused by the hard disk being brand new and having no partition table.
Quite why this should be a problem for FOG is a mystery to me but I have found that if I put the hdd (which is in an easily removable caddy as the pc is a CF19 Toughbook) into a machine then boot the machine from a USB CD-ROM drive with a linux live boot disk in it, I can then run GParted from the live cd and get an error message saying [FONT=Arial]“No partition table found on device /dev/sda”[/FONT]
[FONT=Arial]If I then Use Device -> Create Partition Table to put a basic MS-DOS partition table onto the new hdd I can then take that caddy, put it back into the machine that was showing the problem with FOG deployment and everything is OK.[/FONT]
Hope this helps, YMMV of course !
Edit - I forgot to say that it wasn’t necessary to format the hdd at all, just creating the partition table did the trick for me.
Cheers
Robin -
[quote=“Robin Commander, post: 3278, member: 64”]I’ve had a look at this today - in my case it seems to be caused by the hard disk being brand new and having no partition table.
[/quote]I remember this being an issue in older verisons of FOG (around .26) but I thought they had resolved that. Interesting. Regardless, good information to know it’s still around.
-
Indeed… I’m using FOG 0.31 on my production system currently.