Thank you for your feedback,
I do all the tests at the end of the week and I’ll give you a feedback at that time. I won’t have the equipment available until

Hey

I found out where my error came from, here are the settings:

Follow the tutorial of @george1421
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/16

On the Fog Web server

0_1493113426231_Capture d’écran 2017-04-25 à 11.37.44.png

On Nas Synology, here is the NFS configuration on all the files /volume1/images /volume1/tftpboot /volume1/snapins so that all posts find sharing Thanks @hfredh

0_1493113614033_Capture d’écran 2017-04-25 à 10.39.05.png

Thanks to all
One can pass the subject in solved

I keep you informed if I can deploy with this method normally there should be no problem

@+

A VM or physical server (or AWS instance) is the correct answer.

FOG wraps itself so tightly into the OS, it really should be an appliance. But since we are all volunteers and FOG is totally open source and nobody who works on fog actually has any money or time to do anything else besides what we’ve been doing - we just have a really elaborate installation script that we work hard to support.

Hey @Tom-Elliott

I confirm that now everything works correctly. The error message was on one of the 2 partitions on the hard drive was too full. I will refine the settings and make you a return on the minimum size of available space to deploy.

I confirm that I capture and deploy on the same machine and therefore even hard drive. So no space problem available.

We can pass the inviter in resolve
As soon as I have the information on minimum available space I will add them in this topic

@+

@Tom-Elliott j’ai fait la mise à jour de FOG 1.3.0RC et cela fonctionne correctement avec cette machine c’est top
Merci de ton aide

@Tom-Elliott I made the update of FOG 1.3.0RC and it works correctly with this machine it is top
Thanks for your help

@Quazz

You are the best @Quazz it’s good everything is working properly now
And thank you for taking the time to Have Reply

@melvinpaz Ok, this is a Mac client you are having problems with. Please tell us exactly which Mac you have (serial number!). The modifications you made are correct as far as I see.

I am wondering why it is saying “Could not open net1”. Are there two network cards in this client. Possibly wireless? Although I am pretty sure iPXE does not provide any wireless drivers. We need more information on the hardware (exact Mac model / serial number) to be able to help you.

Bonjour
Oui c’est bien FOG 1.2.0 et c’est bien la modification initrd=$imagefile qui à fait fonctionné sur MAC

#########
Hy
Yes it’s good FOG 1.2.0 and it is changing initrd=$imagefile who in fact worked on MAC

Bonjour @Sebastian-Roth

Mon problème était bien la version du kernel mais pour mettre à jour le kernel il fallait que je rentre le proxy donc oui tu avais raison.

Maintenant j’ai un nouveau problème voici le message d’erreur

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

############
Hello @Sebastian-Roth

My problem was indeed the version of the kernel but to update the kernel I had returned the proxy so yes you were right.

Now I have a new problem here is the error message

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)