Looking for Hard Drives ... Then Freeze
-
It created a folder named after the mac address of the machine in my /images/dev folder , but there’s nothing in there and there’s no HDD activity on either machine
-
Hangouts?
-
So I found the solution to this issue. I had installed Windows 7 on a machine that formerly was a Ubuntu Box. I tried to use Clonezilla - which identified the issue. I won’t pretend I knew what was going on so here is what they said about it:
[FONT=Bitstream Vera Sans][COLOR=#000000]You might have installed an OS with GPT partition table, and later overwrite the disk by installing another OS with MBR partition table. The MBR partition table editor, e.g. fdisk, sfdisk, or cdisk does not know GPT, so it overwrite part of the GPT partition table, but did not clean the rest completely. Therefore that’s why you got such a message.[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]If you are sure your running OS is using MBR partition table, not GPT one, you can run[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]sudo sgdisk -z /dev/sdx[/COLOR][/FONT]The box I was trying to image was formerly an Ubuntu box, which I installed Windows 7 on. I did delete the partitions, but apparently that didn’t matter.
[FONT=Bitstream Vera Sans][COLOR=#000000]This worked. Just thought I’d include this for posterity. Thankfully now that this is out of the way hopefully I can put the FOG server I’ve (and the excellent guys who support FOG) invested so much time into to good use.[/COLOR][/FONT]
-
[quote=“John Finley, post: 26117, member: 23810”]So I found the solution to this issue. I had installed Windows 7 on a machine that formerly was a Ubuntu Box. I tried to use Clonezilla - which identified the issue. I won’t pretend I knew what was going on so here is what they said about it:
[FONT=Bitstream Vera Sans][COLOR=#000000]You might have installed an OS with GPT partition table, and later overwrite the disk by installing another OS with MBR partition table. The MBR partition table editor, e.g. fdisk, sfdisk, or cdisk does not know GPT, so it overwrite part of the GPT partition table, but did not clean the rest completely. Therefore that’s why you got such a message.[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]If you are sure your running OS is using MBR partition table, not GPT one, you can run[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]sudo sgdisk -z /dev/sdx[/COLOR][/FONT]The box I was trying to image was formerly an Ubuntu box, which I installed Windows 7 on. I did delete the partitions, but apparently that didn’t matter.
[FONT=Bitstream Vera Sans][COLOR=#000000]This worked. Just thought I’d include this for posterity. Thankfully now that this is out of the way hopefully I can put the FOG server I’ve (and the excellent guys who support FOG) invested so much time into to good use.[/COLOR][/FONT][/quote]
Thanks for the documentation on this!
-
That MAKES much BETTERERERERERERER sense now. Thanks John for reporting back.
-
[quote=“John Finley, post: 26117, member: 23810”]So I found the solution to this issue. I had installed Windows 7 on a machine that formerly was a Ubuntu Box. I tried to use Clonezilla - which identified the issue. I won’t pretend I knew what was going on so here is what they said about it:
[FONT=Bitstream Vera Sans][COLOR=#000000]You might have installed an OS with GPT partition table, and later overwrite the disk by installing another OS with MBR partition table. The MBR partition table editor, e.g. fdisk, sfdisk, or cdisk does not know GPT, so it overwrite part of the GPT partition table, but did not clean the rest completely. Therefore that’s why you got such a message.[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]If you are sure your running OS is using MBR partition table, not GPT one, you can run[/COLOR][/FONT]
[FONT=Bitstream Vera Sans][COLOR=#000000]sudo sgdisk -z /dev/sdx[/COLOR][/FONT]The box I was trying to image was formerly an Ubuntu box, which I installed Windows 7 on. I did delete the partitions, but apparently that didn’t matter.
[FONT=Bitstream Vera Sans][COLOR=#000000]This worked. Just thought I’d include this for posterity. Thankfully now that this is out of the way hopefully I can put the FOG server I’ve (and the excellent guys who support FOG) invested so much time into to good use.[/COLOR][/FONT][/quote]
This may sound like a dumb question, but where do you run that command? On the fog server?
-
No such thing as a dumb question.
You run it on the client you are trying to image.
-
[quote=“BPSTravis, post: 26364, member: 22444”]No such thing as a dumb question.
You run it on the client you are trying to image.[/quote]
I am having this same issue.
I went into the fog compatibility menu and I get a parted prompt, with a message that says Warning /dev/sda contains GPT signatures…etc…but I am getting invalid tokens when I try to type anything in. This does make sense reading through the post. But this drive was OEM from Dell, why would it have this issue?
-
OEM’s formatting is usually not imaging friendly. That’s why we recommend wiping the formatting on the drive.
In order to type into the input you need to use a Debug task…
Debug mode will load the boot image and load a prompt so you can run any commands you wish. When you are done, you must remember to remove the PXE file, by clicking on “Active Tasks” and clicking on the “Kill Task” button.
-
i did sgdisk -z /dev/sda
output: invalid partition
partition destroyed
