Posts made by melvinpaz

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

Hello @Sebastian-Roth

I just tried it and the problem remains the same impossible to launch windows, blinking and still present.

If a person has a lead, I’m a taker. If you need more information, do not hesitate to contact me. So I put it back on sda2
We look forward to hearing from you soon.
Thank you for your help

Hello @Sebastian-Roth

The problem wouldn’t come from the choice of partition at boot time?
I ask the question so you never know

Thank you for your help

Hello @Sebastian-Roth

Here is the screenshot

Thank you for your help.

Hello @Sebastian-Roth

You will find below the requested screenshots.

---

---

Hey @Tom-Elliott, @Sebastian-Roth

This does not work despite the fact that the image is well deployed
I tried the “partclone uncompressed” function and I reach the end of the process but when I restart the Windows computer does not start I have a flashing white bar in the upper left corner of my screen despite the image being well deployed in the hard disk. As if windows doesn’t start.

In the bios we are well in AHCI and Legacy for the boot of windows. I also tried in UEFI impossible to start

All signals are on Done

Thank you for your feedback
You will have a compression mode solution to propose to me to work or do tests to continue using a raspberry or do I have to change my hardware?

Currently I am doing a test without compression. I’ll get back to you as soon as it’s over.

Hey @Sebastian-Roth
Thank you for your feedback
If I use the parameter “partclone uncompressed”, do you think it can work?

Hey @Tom-Elliott my savior
Here is the information in the graphical interface

Here is the information with the command line

I tried with the single disk - resizable option and it doesn’t work either

Hello

My fog server runs on raspberry pi (noob operating system) with a hard disk at boot time of 1TB ssd. I can correctly capture my image from my disk but I can’t deploy it. I tried all the configurations in the bios and couldn’t deploy. Boot AHCI, Start-up UEFI… I can’t find a solution.

Do you have any idea?

The image capture I’m trying to deploy was basically on a 3.5 hard disk and now I’ve put everything on SSDs.

Thank you for your help

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

@+

Hey @Tom-Elliott

I thank you for the update but the problem remains the same. Are there any restrictions on a minimum space in the partition that you want to deploy?

Let me explain :
I captured an image with 20 GB of available space. I get my capture but maybe the 20GB space on this partition is not enough to perform the deployment.

I am currently reformatting the hard drive of the deployment machine and reinstalling the system without putting any contents in the hard drive. I will perform the capture and then the deployment. If it works, it takes a minimum amount of space available in the image in order to realize the deployment.

If you have this information about a percentage or quantity in GB of available space that should be left on the partition to deploy it would be cool to communicate it or share the link of this information because I did not find it.

We do not tell you it may not be enough but still thanks the community for the work done for this really practical tool

@+

Hey @Tom-Elliott @george1421

The problem persists despite the update with the revision RC 1.4.0 RC9

I captured the image again and tried to deploy it without success

Do you have another idea?

@+

Hey @Tom-Elliott et @george1421

The problem persists despite the update with the revision RC 1.4.0 RC8

I captured the image again and tried to deploy it without success

Do you have another idea?

@+

@george1421 That she is how git to retrieve the version 1.4.0 RCx ?

Hey @Tom-Elliott

I allow you to restart because I have the same error message with a more recent revision on a MAC.

Do you have an idea ?

@+

Hey @Tom-Elliott

I therefore realize a fog server with a physical machine under Ubuntu

thank you for the answer
@+

Incident résolu
Incident Resolved

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

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

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

@+

Hey @george1421

I did exactly what you asked me and I manage to mount the share on the machine without any problem.

Fog

ubuntu@ubuntu-P5QL-PRO:/$ sudo umount /mnt 
ubuntu@ubuntu-P5QL-PRO:/$ sudo mount -t nfs 10.9.153.249:/volume1/images /mnt
ubuntu@ubuntu-P5QL-PRO:/$ ls -al /mnt/
total 4
drwxrwxrwx  1 root root    36 avril 24 14:23 .
drwxr-xr-x 26 root root  4096 avril 25 10:00 ..
drwxrwxrwx  1 1054 users   18 avril 24 14:24 dev
----------  1 root root     0 avril 24 14:23 .mntcheck

By Contre by launching debug mode this is what I get on the station in debug mode

I followed your advice @hfredh and I fall on the same error message. I tried with the 2 configurations in ip direct and with ips under networks

Thank you for your help and suggestions

@+

Hey @george1421

10.9.153.249=NasSynology
10.9.153.248=Fog

When I followed your tutorial I had a problem with this line

mount -t nfs <syno_nas_ip>:/volume1/snapins /mnt
mkdir /mnt/ssl
cp -R /opt/fog/ssl/* /mnt/ssl
umount /mnt

I did not find the /opt/fog/ssl directory in the computer with the Fog server so I copied the /opt/fog/snapins/ssl/

Here is the error message I get

More information.

Fog

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/fstab 
10.9.153.249:volume1/images /images nfs default 0 0
10.9.153.249:volume1/images/dev /images nfs default 0 0

ubuntu@ubuntu-P5QL-PRO:/$ ls -al
drwxrwxrwx   4 fog  root  4096 avril 20 16:17 images

NasSynology

ubuntu@UFRIngemedia:/volume1$ ls -al
drwxrwxrwx+  1 root  root    36 Apr 24 14:23 images
drwxrwxrwx+  1 root  root    18 Apr 24 14:24 snapins
drwxrwxrwx+  1 root  root   808 Apr 24 14:26 tftpboot

The configuration is the same for tftpboot and snapins files

---

I then tried the following tutorial with @chris-dees et @george1421 https://forums.fogproject.org/topic/9422/setup-synology-diskstation-as-main-storage-for-fog-sever/12 and I come across the same type of error message

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

Thank you for your help
@+

---

Hey @george1421

10.9.153.249=NasSynology
10.9.153.248=Fog

Quand j’ai suivie votre tutoriel j’ai eu un soucis à cette ligne

mount -t nfs <syno_nas_ip>:/volume1/snapins /mnt
mkdir /mnt/ssl
cp -R /opt/fog/ssl/* /mnt/ssl
umount /mnt

Je ne trouvé pas le répertoire /opt/fog/ssl dans l’ordinateur avec le serveur Fog j’ai donc copié le repertoire /opt/fog/snapins/ssl/

Voici maintenant le message d’erreur que j’obtiens

En complément d’information.

Fog

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/fstab 
10.9.153.249:volume1/images /images nfs default 0 0
10.9.153.249:volume1/images/dev /images nfs default 0 0

ubuntu@ubuntu-P5QL-PRO:/$ ls -al
drwxrwxrwx   4 fog  root  4096 avril 20 16:17 images

NasSynology

ubuntu@UFRIngemedia:/volume1$ ls -al
drwxrwxrwx+  1 root  root    36 Apr 24 14:23 images
drwxrwxrwx+  1 root  root    18 Apr 24 14:24 snapins
drwxrwxrwx+  1 root  root   808 Apr 24 14:26 tftpboot

La configuration est la même pour les fichier tftpboot et snapins

---

J’ai ensuite essayé le tutoriel suivant avec @chris-dees et @george1421 https://forums.fogproject.org/topic/9422/setup-synology-diskstation-as-main-storage-for-fog-sever/12 et je tombe sur le même type de message d’erreur

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

ubuntu@ubuntu-P5QL-PRO:/$ cat /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

Merci pour votre aide
@+