Tom kindly fixed it for me, I’m very grateful. I want to document it properly in case anyone else has the problem, which I’ll do tomorrow, its 23:45 here and after a week of trying to get it to work I need some beauty sleep!!

Thank you all for your help, it’s much appreciated, sleep well.

Yours

Julian

Hi Wayne,

I have a VMware troubleshooting course to finish off updating, but afterwards I should have some time and more importantly kit free in early May. I could have a go then if that’s ok.

Julian

The problem was that the master node check box wasn’t selected. As it was a new storage node, it needed selecting.

Thank you all for your help. It’s much appreciated.

Julian

I ran out of disk space on the data disk today, but couldn’t work out why. I then researched it a bit and found that Linux reserves 5% of the disk in case you start to run out, for the system files. Great idea for system disks, but pointless if you have data disks for say images.
This command removes the reservation from the disk, and gives you back the 5%

sudo tune2fs -m 0 /dev/sdb1

I hope this is useful

I fixed it, it was the grapjics card. I swapped it over and now it’s working perfectly.

I spend, not hours, but days on this, eventually I swapped every component with one that worked.

Thanks for all your help, what a weird one!

Could you change this to solved please

Thanks

Thanking you , have a jolly good evening.

Thank you Wayne, that’s really helpful.

Julian

Thanks Sebastian, that’s great. How do I backup the database? and restore it?

Thanks

Julian

Hi Sebasrtian

It’s not really a fog issue, it the expansion of the raid array that requires it wiping. I have a mega raid 9341-8i hardware raid array. I’ve just run out of space,

I’ll be installing Ubuntu 20.

Thanks

Julian

Hi All,

I use Fog in my training rooms to re image the student servers. The images are updated once every 6 months if that, but it deploys them on a Friday night.

I’ve decided to wipe and re install Fog from my old version 1.5.0 to the new 1.5.9. I need to add a new drive to the array which requires a rebuild of the array.
I have about 20 images I’m going to copy to both an internal disk and USB disk. It’ll take a week I think. Then copy back and recreate the images pointing to the restored files
Then I’m going to reinstall the OS and Fog. That’s the plan.

I thought I’d ask about any gotchas before I hit them.

I have a dedicated box which is running Fog I borrowed from a lab, 32GB 4 Core SSD array, which will be fine, but the OS is updating to ubuntu 20. Nothing else will change. I have 2 types of images, Windows and VMware, and I’ve put the details below.

Is there anything I should be aware of?

Thanks

Julian

Er sorry for creating so much trouble.

Thanks Sebastian. I’m not good with databases though. Will these commands wipe the image side of the database? I’m not bothered. I can happily recreate the images, as the files will still be there.
Thanks
Julian

I had another look at it in the light of day. I redeployed the images to the rest of the servers and what a mess. Servers were deploying on the wrong physical boxes. It’s VMware and the UUID of the hard disks need to match or it gets awfully upset.

So the images seem to have their references to the image locations wrong. I then changed an images location and saved it, then changed it back again and saved it, nope that didn’t work. I then created a new image, moved the original image elsewhere, and pointed the new image to the correct file location, and it works.

So the database seems stuffed. The fog server is crutial, I’ve put it on a fast box with a SSD raid array and don’t want this again, so I’m going to image down the servers, rebuild the fog server and image it up.

I’m going to screen shot the image details. I’ll use unbuntu 18 and the latest fog. I’ll take the details of the images Is there anything I need to be aware of before I do this?
Thanks

Thanks I didn’t realise that. Much appreciated.

It would be nice if I could be emailed to let me know that an image, or group of images had successfully deployed or finished deploying.
There are services that allow you to subscribe to a number of SMS notifications, all you need to do is send them a set of parameters, so I could get a text telling me they’d finished deploying.

Just a thought

I rebuilt my training room last week and imaged it up. Fog version: 1.5.0. There are 11 machines. on 4 of them everything’s ok, but one doesn’t have an image but works, details below, and the remaining ones give me the following error. A screen shot is here.

https://www.dropbox.com/s/06wf9g22cxaslrs/IMG_3596.JPG?dl=0

There are 11 images in my room. Servers 0-11. Server 9 doesn’t exist. If I look in the /images directory I see Server0-8 and 10-11. BUT not server 1, but there is an image in the /images/dev directory with the same MAC as server1, so this is the temporary one that is copied over. If that didn’t happen then it probably ran out of disk space, but I deleted all the server images from /images before I started the upload. I’ve checked the images directory, and there’s space here’s the details https://www.dropbox.com/s/d0jnxw7b7q0dn92/IMG_3598.JPG?dl=0

I think the database is corrupted.

Fog has worked brilliantly for me, and I’ve become totally dependent on it. I have to get this working this week or I’m in a real mess.

can anyone help me? Pleeese

Julian

Thanks Sebastian,

The fog server ia a quad core 3.4GHZ with 32GB ram and uses a 4 TB sata drive to store these images on. It’s normal images are stored on a SSD array, its just because these aren’t used that often that they’re stored on a sata.

The clients are all 32GB 4/6 Cores @3.4 GHZ, single SSD disk with a dedicated 1 GB network.

The machines are usually used for just their PC’s image in the training room.

Any suggestions?

Thanks