Jump to content

Recommended Posts

Posted

Hello, I'm getting this error from fog clients when trying to push the images;

"can't have partition outside the disk" ( then PC halts )

The PC's are Dell Optiplex 740's, but the Optiplex 740 which I pulled the image from has a larger hard drive than the others. ( one large partition )

I thought that fog auto-sized the target drive's partition when pushing the image, so the target drive could be smaller than the originating drive's partition.

Have I missed something ?

And does the fog server have a utility to check the target drive first ?

Posted
I just started using fog a few months back and I have the same problem with a few machines and particularly with any hard drive that has been wiped clean. The way I fix it is to boot with a Gparted live disk and then go to Device > Create Partition Table. That usually fixes it for the hard drives that were completely wiped. I do have one machine I can't seem to resolve the issue with though and I'd love a more definitive and automated way of doing it than having to boot a live disk every time I get a new hard drive in the office.
Posted

Well I decided to buy new hard drives which were identical to the ones which we fogged successfully.

Luckily the pricing was low ( on Dell's site ) for the 250 gig Seagate SATA drives.

But thanks for the tip about using Gparted, I may use that next time I run into this problem.

Posted

personally it sounds like you had some hidden data left on the drive, this happens from time to time.

 

Always make sure you run dban and or any other zero write application to the drive (like the vendors own apps which are free as well)

 

Seen this happen as well, just make sure that you wipe em first =)

Posted

Get to a command line and type fdisk -l

Note the number of cylinders reported and see if there is a partition that ends on this cylinder +1. There probably is.

Using fdisk again, delete the partition(s), then create a new partition, ensuring that end of the partition = the cylinder count report by fdisk -l.

This method works where gparted doesn't seem to. I do not know why gparted fails, or why this works, or why there should be cylinders outside the number of cylinders the disk has. It's all crazy.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...