Imaging not starting
-
@Killklli Is this in the web interface or when a client boots up? Sorry but I just can’t imagine what you mean. Maybe a screenshot or photo would help.
-
@Uncle-Frank I’ll try to get an image but here is the exact process of what happens.
- I set the task for the computer to download the image and it WOL’s the computer
- The computer loads up to PXE and loads ipxe
- The computer boots into the usual imaging options (Before it gets to the blue Imaging screen)
- All of the sub options say done almost instantly and the client says the imaging is complete and it is restarting.
- When I go back to the web interface the task is no longer on the task list as if the process was successful.
EDIT
The image was hard to get because it happens within a few seconds.
-
Sounds a bit like FOG does not recognize the disk in this machine. Please run a debug job (Host->Basic Tasks->Debug) for this particular host and the following two commands:
shell$ gdisk -l ... shell$ cat /proc/partitions ...What do you see there?
-
I’ve seen this issue before.
this was due to my image being non-resizable and trying to restore it to a HDD smaller than the source. There might be other things that might cause this, but @Uncle-Frank is on the right path. It’s HDD related for sure.
Pop the hood on two of the systems, compare the drives and report back.
-
@Uncle-Frank For some reason gdisk -l does not like me. @Wayne-Workman The two hard drives I have are a 250gb ssd and a 1tb HDD all of the other machines have the same drives. I tried rotating through the sata cables to see if order mattered but it did not work.
-
@Killklli What’s the image type? resizeable? Non-Resizeable? Did the image come from the 250GB or the 1TB ?
-
And what about ‘cat /proc/partitions’?? Maybe try ‘fdisk -l’. Just thought I point you to gdisk in case you have GPT on your disk…
-
@Wayne-Workman Its a Multiple Partition Image - All Disks (Not Re sizable) It was made on the 250 @Uncle-Frank I’ll check in the morning.
-
@Uncle-Frank
-
FOG uses its own too to enumerate disks. I am pretty sure we won’t see any surprises here but could you please boot into debug mode again and run
fogpartinfo --list-devices? -
@Uncle-Frank
-
Well, there we go I’d say. FOG does not expect this output (“unrecognized disk label”) and is propably not able to parse this. I am away for the weekend and won’t be able to have a closer look at this till Monday.
-
Have you tried zeroing the disk entirely with DBAN? (Darik’s Boot and Nuke - just use the quick method)
Is it possible the disk is failing?
-
@sudburr I’ve tried DBAN on both. I’d be surprised if both started failing at the exact same time.
-
Is that a 512e drive?
-
@Killklli As I am still kind of new in the Dev-Team I don’t know all details of all the tools yet. Looking into the code of
fogpartinfoI just saw that it tries to read a partition table from a disk. This fails because your disks don’t have a partition table yet (as we see in the output offdisk). Quick solution would be to boot up into debug mode and create one partition on both drives e.g. usingfdisk.@Developers Is there a reason why
fogpartinfoexpects a valid partition table when enumerating disks only? I don’t know enough about libparted. Maybe it’s just the way it is?! -
@Uncle-Frank After doing some heavy messing around with the images I was deploying it seems that for some reason the size of the image was an issue. Even though every computer has the same hard drive and have all been wiped, lowering the image size by 50 more GB (instead of leaving the 10gb padding I had before) fixed it. I used 50GB as a brute test to see it it worked and its strange that it did. Considering the 1tb drive should have taken over no matter what. So I put the 1tb drive in another computer and it imaged fine in there. It seems to just be a strange image size issue.
-
Thanks for reporting this. Would be interesting to see if you can nail it down exactly just to see if this could be an issue on other systems too.
Does that mean that my assumption about
fogpartinfo(it fails when there is no partition table) is wrong?? -
@Uncle-Frank That seems to be the case. The drives themselves had DBAN run on them so it might just assume pre existing partitions. Not default info.
-
is there a reason you’re not using the re-sizeable image type?
