I would like add a new hdd ...
-
Hmm, it’s working on my end.
Is there anything in the apache error logs? (FOG Configuration -> Log viewer -> Drop down apache error log)
-
@Quazz no log available.
The message printing is “unable to open a file”
In the configuration of a new node.
The “password management” is the same of fog user ? -
@afaure Yes, but to be precise, it is the FOG linux account. Not the Web login.
If you don’t know/remember this, the password should be in /opt/fog/.fogsettings
-
@afaure I’m in an add day meeting today so very little time, but just wanted to add. Make sure the file permissions on /images2 match the same as /images.
-
@Quazz it’s ok. The good password are used…
-
@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…
-
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. -
@afaure said in I would like a add a new hdd ...:
@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 ?
Thank you.
-
@Tom-Elliott thank you.
I can update the version of my fog the next week.I can update with the git method ?
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunkThank you.
-
@afaure said in I would like a add a new hdd ...:
I can update with the git method ?
Yes.
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.
-
@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.
-
Hi @george1421
Ok i waiting your tutorial
Thanks !!
-
@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.
-
@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 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.
-
What you are seeing has been confirmed and I can duplicate it over and over. I have issued a bug check with the developers.
-
@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)The
fsidvalue should have been incremented to not duplicate thefsidfor two shares on the same server. So for the /images2 share thefsidshould be3and /images2/devfsidshould be4. 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) -
Thanks @george1421 i have try this.
I have an error at the end
Where are you ftp_login
Thanks for the next reply
-
@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.
-
@Tom-Elliott thanks.
The same user/password is used on the configuration node.
I have inspect the box with management password.
I have copy/paste the password
