@dungeon: Thanks for confirming that this is a 2TB disk.
dungeon wrote:iam from holland
Thanks, I can see that from your profile - unfortunately some detail about your issue is not clear / ambiguous due to language issues...
dungeon wrote:Yes i now the password
Unfortunately this answer is not detailed enough.

I hope you mean that:
a) you have set a password on that USB Freecom XS 2TB disk, and
b) you know what the password is, and
c) you are entering that correct password into the correct application, before trying to access the drive.
Am I correct?
Were you able to use this password security OK before your problem started, or did your problem start as soon as you enabled this password security?
In order for us to properly understand your situation, please explain exactly how you set that password (which program did you run? do you mean that you set a BIOS password, or do you mean something else?). There are different types of application which could use a password, and it is not clear which type you are using. As mr_spokk highlighted, the point is to make sure that your problem is
not caused by you losing (or not correctly entering) the password.
Due to the specific type of error message which I translated in my earlier posting, and assuming that you are correctly unlocking whatever security you have enabled by using the correct password, I still think that trying to clone the disk is probably the DIY "next action" - but that is
only if you already have skills and experience which mean you are comfortable doing this type of work, and that you want to take the risks of DIY. If this sounds too difficult, or you do not have the necessary skills/experience, then if the data has value to you, now is the time to decide to use a DR company. Some of the members here could give recommendations, if you ask.
If you are able to clone
any of the disk without errors (i.e. if you can read
any of the source "problem" disk), then the drive must be unlocked from whatever security you have enabled. Of course you could do further checks with a hex editor to try reading from the drive, but if you are able to read from the drive, then IMHO it is better to spend that time trying to clone it and that will also tell you if any of the disk is readable, if you are accepting the risks of DIY.
There is more (better) diagnosis you can do if you had a direct SATA connection to the disk, but that would mean voiding the warranty by opening the USB enclosure (and it also assumes that the internal disk has a SATA, and not a direct USB, interface).
Edited to add: You have not yet answered this question which I asked earlier:
You say the disk is only 3 days old - so either it was already faulty, or some event has damaged it within those 3 days. Has anything unusual happened during those 3 days?