PXE image looping
-
@ManofValor Ouch! I really think you should look into how fdisk and partitioning in general works before using this tool. From what I can see you’ve totally screwed the partition scheme on your FOG server and you will run into big trouble sooner or later. You might not see any issue yet as your disk was in use when you changed the partitions. But rebooting the machine will finally kill it I am pretty sure. So if you still have access try backing up things over the network or onto an external disk before it is too late!
Then you probably need to start from scratch. Install CentOS and probably best make sure you add a good size partition for
/imagesright then. So you don’t have to move things around later on. Then install FOG trunk again. -
@Sebastian-Roth said:
Then you probably need to start from scratch. Install CentOS and probably best make sure you add a good size partition for
/imagesright then. So you don’t have to move things around later on. Then install FOG trunk again.FWIW: Unless you specifically go into the hard drive layout during centos install Centos 7 will divide the hard drive between the root partition and the /home partition. Not really helpful for an application server configuration. If you are setting up fog on a VM create the initial FOG disk in the 16 to 20GB size, then after centos is installed add a new vmdk file that is 50-100GB and mount this new disk to the /opt directory before you install fog. Then during fog install tell fog to install its images in /opt/fog/images. This will keep all of the big files on the /opt disk without the risk of filling up the root partition on linux.
-
@george1421 said:
Unless you specifically go into the hard drive layout during centos install
That’s the only way I ever do it
I actually give /images it’s very own partition, and I seriously reduce the size of all other partitions.
-
@george1421 I knew I was going to screw it up. I want to make the images file as big as possible since this is strictly for image backup. So after install I could make it like 350G in size, right?
-
@ManofValor If you do as I suggest just create a 20GB vmdk for the OS. The OS only really needs about 5GB, but leave room for updates and such. Once that is done go back in and create a new vmdk file for your storage. Make it what ever size you need today. By putting the images in their own vmdk file you can dynamically grow that disk as you need to as time goes by.
Once you have that second vmdk file (will probably be listed as /dev/sdb) you will need to partition it with fdisk and then format it as ext4. Once you have that disk you need to attach it over/to the /opt directory so it mounts every time (using /etc/fstab file).
Once you have that new vmdk attached, then you can install fog and tell it to put its images in /opt/fog/images
This will be a great learning experience for you. Google is your friend.
-
@george1421 Solid advice, absolutely, and would work fine too.
I would prefer though to mount the 2nd hdd to /images because /opt/fog/images is a deviation from the expected. And because /images would be the expected location for all of our documentation, all of our forums posts, and any future advice we give out, and any tech with previous fog experience coming into an environment to take care of FOG would expect the images to be in that location, and the installer uses this location as default.
But again, nothing mechanically or logically wrong with moving it to /opt/fog/images, it’d be perfectly functional and equally as expandable in the future.
-
@Wayne-Workman What partitioning scheme do you recommend? I’ve been trying to look up the difference between the four options I have (standard, btrfs, LVM, and LVM Thin Provisioning). I was thinking standard for the OS and LVM thin for the images?
This is question for all.
-
@ManofValor LVM is easier to resize later. However, all can be resized, just the older the scheme the more difficult it is. You might want to hold off till @george1421 chimes in.
-
@ManofValor LVM is the way to go. But you still want to move your FOG storage off your root LVM, or if you fill it up you will have the same issue as if you had everything on the same partition. *nix does not like it when you fill up the root partition. When you do this, you will never have a happy ending. But if your images are on a different LVM or disk that is attached to your root partition then you can fill up that disk, but it won’t whack the root volume. Its kind of complicated how it is setup.
If you want to think about it in MS windows terms. The root disk/partition is like the
drive and we will connect a new disk to the folder C:\opt. When you change into the C:\opt folder behind the magic curtain windows will seamlessly transition to that other drive. -
@george1421 So for the install just do the 20 GB and then do the other one later after the install? I’m not trying to set this up as a VM, isn’t that what a vmdk is for? This is a physical server.
-
@ManofValor Sorry I shouldn’t think the whole world is virtualized.
On your server do you have a single disk, array, or what?
-
@george1421 Single. We are mostly virtualized, but not for this yet.
-
Using the install GUI, do I do it like this:
Manually partition OS with LVM at 20GB mounted on /boot using ext4
Manually partition storage, for images, with LVM at 450GB mounted on /opt/fog/images using ext4
Something along those lines?
-
@george1421 said:
Sorry I shouldn’t think the whole world is virtualized.
I was just going with the flow lol.
-
This post is deleted! -
@ManofValor It’s not a fog question. It’s a Linux question. If CentOS 7 supports it (or any other distro of Linux), then fog can use it.
-
-
@ManofValor Looks good, the only suggestion I’d make is making the /boot partition 1GB. Who knows how long you’ll use this server?
Once I helped with a Ubuntu server that was literally out of space on it’s boot partition… We only got by because I found some older kernels to delete!
-
@ManofValor I know its probably too late, but I would have done the /opt mount point instead of /opt/fog/images. That way all of the opt stuff would go into that 400GiB drive. What you won’t get is /opt/fog/snapins that will still go onto the root partition. Sorry I was late, stuck in a teleconf call for 2 hours.
-
@george1421 said:
I know its probably too late, but I would have done the /opt mount point instead of /opt/fog/images.
It’s not too late. I’d say go back and do it right.
