You could try to repair whatever is wrong using the rescue system. Is there any more info available about the error?

Edit: If it's an error/technical problem in netcups server environment and not something you did wrong setting up the server, you could also call the emergency support.

See https://www.netcup.eu/kontakt/telefonsupport.php

Zitat von Engerous

No sorry i dont have any other info i tried to use rescue system but for that i have to set the first boot device to "network"and when i do it it says me the same error : An error has occured

If you cannot access neither the Rescue System nor your own installation due to an error as shown above and the above is reproducible, call the Emergency Support.

Ok, so, if it is urgent, I would call the emergency support in this case. The rescue system should always work, even if you completely misconfigured the server. So it's likely a technical problem of netcup.

I'm really glad Netcup has this emergency support! I wish a certain Provider not to confuse with Jagdpanzer 38 had it too

Some users reported their driver changed from SCSI to VIRTIO or vice versa at reboot, which could cause a boot failure. Have you checked this issue in your SCP?

The SCP reports an issue which means something on Netcups side is broken. If it was the wrong driver the KVM instance would start, thought the console would show an error

Hmm maybe create a snapshot, export it, rent the same server again, import the snapshot and start the new server. Wait for the support to fix the issue. You could cancel the new server within the first weeks. Sounds horrible but could help.