hello, I couldn’t find a solution to unlock my situation, I tried many things on promox and on fog, without succes again. So I decided to start a new install on another post, separated from the proxmox and it’s working fine. I think I’ll keep this solution so, thanks for your help and sorry to leave an unsolved issue, see you later !

@salted_cashews said in Is a direct upgrade possible in this scenario while retaining all previous configurations and images?: To be honest, I’m not 100% sure how our guy knew that was causing a problem. People with even some Linux experience normally check free space as a first-step in troubleshooting. Glad you got it figured out.

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 @+

@Tom-Elliott to further iterate and give some more specific information. Unicast worked because while the order was not “proper” it pulled the partition number from the iterated item. Example /dev/sda1 would look for file d1p1.img. /dev/sda10 would actually look for and use d1p10.img. In multicast this iteration happens but the data is sent by the server. It did not scan for a particular file. So in your case the commands were sent in expected order. udp-sender would send in order d1p1.img, d1p2, d1p10 It sent the commands in that specific order. The partition receiving the file was not matching the file it was receiving. /dev/sda1 would get d1p1.img properly but /dev/sda10 was getting d1p2.img. Hopefully that helps make sense of the problem.