Imaging not starting
-
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?
-
@Junkhacker I had multiple hard drives I was trying to image at once and once this issue started popping up I actually did switch to re sizable but it was still having that issue strangely.
