DeployStudio - unable to mount repository

[FN-GM]

Hi,

 

I have setup DeployStudio by following this: ADaMac Tutorial - DeployStudio 101 - YouTube

 

I can netboot by pressing N on startup fine. When i click create master i get the error message "unable to mount repository".

 

Does anyone know why this happens please?

 

Thanks

[HodgeHi]

AFP share not being found?

Permissions not correct?

 

There could be a few reasons. More information would be needed to better help resolve the issue.

 

Can the share be mounted on the deploystudio server using the name and password given for the deploystudio user?

[FN-GM]

AFP share not being found?

Permissions not correct?

 

There could be a few reasons. More information would be needed to better help resolve the issue.

 

Can the share be mounted on the deploystudio server using the name and password given for the deploystudio user?

 

the admin account used to mount it has full control, i assume it can be mounted as it needed this during the wizzard.

 

All i did was what is the the video, apart from setting up the AFP and NetBoot service as this isnt shown.

 

Thanks

[pooley]

Open server admin, click on server then go to "share points" look for your "share" there and make sure that deploystudio admin has full access.

[FN-GM]

Is there a special account made for it? I specified the normal admin account during the install.

 

Thanks

[HodgeHi]

The AFP share settings are found in the nbi file (used to netboot the clients). Make sure that all the settings in this file are correct.

 

Also check the log on the screen during process. It may give more information as to the reason the repository couldn't be mounted. I think you can also do this from the deploystudio admin GUI.

[FN-GM]

Checked the permissions and the admin account has full read a write.

 

The AFP share settings are found in the nbi file (used to netboot the clients). Make sure that all the settings in this file are correct.

 

What would i be looking for please?

 

I re-ran the wizzard and it still does it.

 

It says unreachable host connection refused in the background of the netboot.

 

Thanks

[Greenbeast]

i had major problems with this too, make sure the server address is the fqdn and any dashes are underscores

[stevehp]

Make sure that the drive or directory used to host the image files has account used in the Deploy Studio wizard listed in the ACL section it can be set to Read-Only. Posix permissions are a little tricky as it can be different. I have root (R+W) admin (R+W) and others (No Access).

 

wazmac || OSX 10.6 Server Setup Notes has a client imaging guide which goes through the steps to setup Deploy Studio. It might worth a read through to see if anything was missed.

[jlucas]

Do you have a proxy set on your Deploy Studio server?

I remember that causing havoc with our set-up when we first did it.

[FN-GM]

i had major problems with this too, make sure the server address is the fqdn and any dashes are underscores

 

Yep done that, also tried with IP

 

Make sure that the drive or directory used to host the image files has account used in the Deploy Studio wizard listed in the ACL section it can be set to Read-Only. Posix permissions are a little tricky as it can be different. I have root (R+W) admin (R+W) and others (No Access).

 

wazmac || OSX 10.6 Server Setup Notes has a client imaging guide which goes through the steps to setup Deploy Studio. It might worth a read through to see if anything was missed.

 

Will have a look, thanks.

 

Do you have a proxy set on your Deploy Studio server?

I remember that causing havoc with our set-up when we first did it.

 

We do have a proxy server but i have not specificed it yet.

 

Thanks

[HodgeHi]

You need to put the deploy studio server in the proxy exceptions list.

 

You will know if this is working as it should since when running through the deploy studio assistant on the server if it can mount the share the it is fine.

 

When booting a client from the network the settings for the deploy studio server are in the .nbi file that is used to boot the client. A .nbi file has to be made for the clients using the deploy studio reboot file creator. It is found when running the deploy studio setup assistant.

 

The way I do it is install deploy studio on the client run the assistant, create the .nbi file and save it locally or to an external drive and then copy it into the nebootSP0 folder on the server. This is then used by the NetBoot server to boot the clients over the network.

 

During the creation of the .nbi file it will ask for the information to find your deploy studio server and the share and also the username to access the share where the images are found, if I remember right.

 

This is the bit you may need to re-create.

[FN-GM]

The proxy settings are covered.

 

The problem with creating an nbi file is that the machines only have windows on.

 

Thanks

[HodgeHi]

 

The problem with creating an nbi file is that the machines only have windows on.

 

 

This may well be your problem. I tried to image a MacBook with just windows on and couldn't get it to start. I think it needs something to be there on the hdd from os x to start the process.

 

If this isn't your newest hardware what you could try is creating a .nbi file using the latest apple kit you have. By using the latest apple kit (and also using the same version of deploy studio that is on the server) you can create a .nbi file that will boot any of the previous generation macs. This is perhaps one of the best things about macs when it comes to net booting.

 

If this doesn't work then maybe time to break out carbon copy cloner?

[tommej]

This is ressurecting an old thread but it's the 2nd hit on google for this issue!

 

I solved this by unticking share folder and re-ticking it on my repository share. This is after an upgrade to el capitan and updating deploy studio to the latest version.

 

The share seemed to be working from other macs but I could not set it using deploy studio assistant.

 

After I did the above it worked fine. Stupid Macs.