I would like add a new hdd ...
afaure last edited by Tom Elliott
I have installed a new hard drive in the fog machine.
I have create a new storage group and a new store node.
But, the capture doens’t work and the image of my laptop is captured in the folder /images
In the image configuration for this PC, i have been choosen the new storage group.
I have screenshots all the detail i think…
Can you help me ?
Thanks for reply !
@george1421 ahah thanks really
I will be back soon (tomorrow) for a new thread :D
I used FOG since 3 years and this solution is beautiful !
@george1421 thank you so much
Have a good night
@afaure Really nice. I needed to write that tutorial for a while now. With your motivation its now done and works!!
afaure last edited by afaure
@george1421 i have been used the same username/password for the node by default.
I have create a new image/association with PC and NOW it’s WORKS
A big thank you dude ! It’s DONE !
Thanks everyone !
@afaure In your case (as Tom posted) your ftp managmeent password is wrong.
In step 6 of the tutorial, ensure the management user name and password are set correctly. You can find out the answers there if you review the /opt/fog/.fogsettings file.
The same user/password is used on the configuration node.
I have inspect the box with management password.
I have copy/paste the password
@afaure On the second storage node that’s connected to the same server, you need the same management username and password as the original server has.
Thanks @george1421 i have try this.
I have an error at the end
Where are you ftp_login :’(
Thanks for the next reply
@george1421 The developers got back with me and there was a flaw in what I did with the instructions. By simply copy and pasting the nfs exported filesystem I introduced the error.
In the exportfs file the following was the incorrect instructions.
- Append the following lines to the end of the exports file
/images2 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images2/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
fsidvalue should have been incremented to not duplicate the
fsidfor two shares on the same server. So for the /images2 share the
4. The correct line should be this:
/images2 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=3) /images2/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=4)
What you are seeing has been confirmed and I can duplicate it over and over. I have issued a bug check with the developers.
@afaure Well, lets hold the thanks for a little while. I just LOOKED at the proof of concept server again AND the capture image IS going to /images and not /images2!!!
On the negative side my tutorial does not work as intended. On the plus time I can duplicate your results exactly. Which is VERY strange since I saw (and posted in the tutorial) that partclone was saying it was copying to /images2/dev. I’m going to duplicate the test since the environment is still setup from last week to confirm. If I can confirm for sure that things are not working right I’ll ask the developers to take a second look at the FOG code since things don’t “appear” to be doing what we are telling them.
@george1421 Thanks for the tuto.
For information, I just updated the FOG !
I can select my new storage but i have a problem of permission !!
I reading your documentation and post the result later !!
Big thanks @george1421
@afaure Sorry. I finished it last week, but forgot to post a link here. https://forums.fogproject.org/topic/10450/adding-additional-image-storage-space-to-fog-server
It did install correctly and work as expected. The first post talks about setting up the operating system and the second post shows what FOG settngs are needed.
Ok i waiting your tutorial
@afaure I think I have what you want working in my test lab. I will work on proving it works tonight and then create a tutorial on how to do this in your environment. There were no secrets uncovered, it just worked once all of the bits were put in place.
I can update with the git method ?
I’m also going to try to make time to put a test system together to test this concept so it can be documented if it works, or not. It should. I feel just something is not set correctly in your setup.
@Tom-Elliott thank you.
I can update the version of my fog the next week.
I can update with the git method ?
@Quazz it’s ok. The good password are used…
@Quazz, can you post a screenshot to the configuration node and image management of 1 PC please ?
Maybe I’m seeing the obvious where others are missing it. Can you update to at least the latest stable and see if the problems you’re seeing with adjusting groups and what not are fixed? It appears you’re running a version of 1.3.5-RC from what I can tell.
All the more reason we want “version” information when opening information about a problem…
RABBLE RABBLE RABBLE.
@george1421 thank you. It’s ok now.
But, i can’t change the storage group of the image…
The storage group “default” are keep all the time…