The Recovery Server could not be contacted in Internet Recovery

What version of macOS are you accessing when in Recovery Mode?

Try booting into Internet Recovery Mode using Command + Option + R to see if you can boot into the online installer for macOS 10.13 High Sierra as that should be the easiest OS to install. Unfortunately some Macs will only boot to the online installer for the OS which originally shipped from the factory. If that is the case, then you may need to set the system date & time to Jan. 2, 2017 @ 11:33am using this command using the Terminal app found on the Utilities menu on the menu bar:

date  -u  0102113317

If there are no errors with the command, then quit the Terminal app and try the "Reinstall macOS" option. If you still get the same error, then try adjusting the date to an earlier year.

Do you have access to another Mac from 2008 to 2018? If so, then you can create & use a bootable macOS USB installer instead.

catalin44 wrote:

Hello,

I have the same problem in my iMac mid 2010, change the date but the same error with the recovery

I try to make the UBS boot with El Capitan from a mac pro but is not finishing the install.

With that USB I install the OS on an other laptop but not on this iMac

It would also help to know why you are reinstalling macOS. The installation failure may be caused by the same thing requiring you to try reinstalling macOS. For a computer that old I would first suspect a failing hard drive, but other hardware issues could be at play here as well including whether any external devices are connected to this Mac. I'm also assuming that there has been no recent hardware changes to this Mac.

You can try running the Apple Diagnostics to see if any hardware issues are detected. Unfortunately the diagnostics do not detect most hardware issues. It is possible to check the health of the internal drive(s) by creating & using a bootable Linux USB stick using the instructions found here making sure to post the complete health report for the drive(s):

Creating & Using a Knoppix Linux USB Stick to Check a Drive's Health Information - Apple Community

catalin44 wrote:

I have on installer log

"installer payload initialization failed no program found"

"predicate update product fetch failed with error"

Unfortunately I don't know what this may indicate. Since you said this USB installer worked on another Mac, then it would indicate that this Mac where it failed has some sort of hardware issue preventing the installation.

FYI, it is hard to find the exact line in the installer logs which is actually relevant to the failure since there may be multiple error entries which are not even fatal and those error entries may only apply to a specific model Mac. I know since I have reviewed installer logs from failed installation attempts....it is really tricky to figure out which entry is the one which contains the critical clue. I usually start at the end of the log and go back to where the installer is cleaning things up. Then I note that spot and continue working backwards until I find a spot where it appears the installation actually failed. Usually somewhere between those two points is the critical information, but it may still not make any sense to us.

Is that an actual third party Samsung SSD or an original Apple OEM SSD which happens to be made by Samsung? There is a huge difference between these two options. Plus is this Samsung SSD a 2.5" model or a blade style SSD using a third party SSD adapter? Not all SSDs are compatible with all computers when the SSD is installed internally. Plus some internal Samsung SSD models are known to have their own compatibility issues with various Macs. Just because an SSD is showing good health does not mean the SSD is actually healthy since most SSD failures I have encountered tend to be due to faulty controllers within the SSD itself....the SSD's controller does not usually have any health metrics reported by the SSD.

If you have a spare external USB hard drive or SSD which can be erased, then you can try installing macOS onto the external drive to see if it makes any difference. While not a foolproof test, this is the next best test you can do beside removing the internal third party Samsung SSD (not a good option due to the difficulty to access the internal drive). If macOS installs to the external drive without issue, then you have your answer that something with the internal SSD is not working correctly (may just be a compatibility issue).

Hello,

I have the same problem in my iMac mid 2010, change the date but the same error with the recovery

I try to make the UBS boot with El Capitan from a mac pro but is not finishing the install.

With that USB I install the OS on an other laptop but not on this iMac

It came with an Samsung SSD, and working fine. The last install was a printer in wifi and after 1 week I can power on, boot loop.

I test the ssd on rack and is working fine with 99% life.

Change the ssd, and the same problem.

Its the Samsung SSD that was in it but the unit was second hand, its a 2.5" with an adapter and was working fine for 2 months.

I'am testin the idea from you with external ssd and in the Disk Utility I see the bouth ssd the internal one and the external one but in the Start up "boot" see only the macOS stick

I have on installer log

"installer payload initialization failed no program found"

"predicate update product fetch failed with error"